GNU bug report logs -
#38862
attribution line parsing
Previous Next
Reported by: Karl Berry <karl <at> freefriends.org>
Date: Thu, 2 Jan 2020 02:44:01 UTC
Severity: normal
Done: Jim Meyering <jim <at> meyering.net>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your bug report
#38862: attribution line parsing
which was filed against the vc-dwim package, has been closed.
The explanation is attached below, along with your original report.
If you require more details, please reply to 38862 <at> debbugs.gnu.org.
--
38862: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=38862
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
[Message part 3 (text/plain, inline)]
On Wed, Jan 1, 2020 at 6:44 PM Karl Berry <karl <at> freefriends.org> wrote:
> Hi Jim - When I had only a single space between date and name in the
> attribution line, as in:
>
> 2020-01-01 Karl Berry <karl <at> freefriends.org>
>
> vcd gave no errors by default. Then I accidentally ran vcd --commit with
> that CL and the only error (warning) was at the end, direct from Perl:
>
> Use of uninitialized value $author in sprintf at /u/karl/gnu/src/vkarl/VC.pm line 210.
> Use of uninitialized value $author in sprintf at /u/karl/gnu/src/vkarl/VC.pm line 210.
>
> I was not left in a good state. There seemed to be no good way to
> recover from this, since the erroneous ChangeLog was already committed,
> so vcd did not think there were any files in the ChangeLog lines.
>
> So I ended up doing rm -rf .git/c/.git and running vcd --init again to
> restart my CL repo, and also
> git fetch && git reset --hard origin && git checkout && git submodule update
> to eradicate all my changes (after saving the actual diff :) in the
> source repo. Thankfully, that apparently erased the memory of the bad CL
> so I could proceed.
>
> Instead of worrying about the exact number of spaces, I wonder about
> parsing attr lines by checking that first word is a YYYY-MM-DD date, the
> last word is <an <at> email.adr>, and considering the words in between to be
> the real name.
>
> Reasonable error msgs would then be easy to give if the first and last
> words don't fit the expected syntax. And if there is no author, it
> could give up at that point. After all, vcd relies on all kinds of
> finicky details about the CL, so seems like it might as well force a
> good attr line too instead of accepting bad ones.
>
> If the idea seems ok, maybe one of us (or a new contributor!) can work
> in that direction eventually. --best, karl.
Hi Karl,
Thanks for reporting and digging into that.
Here's the change that I've just pushed to address it:
[vcd-diagnose-bad-date-line.diff (application/octet-stream, attachment)]
[Message part 5 (message/rfc822, inline)]
Hi Jim - When I had only a single space between date and name in the
attribution line, as in:
2020-01-01 Karl Berry <karl <at> freefriends.org>
vcd gave no errors by default. Then I accidentally ran vcd --commit with
that CL and the only error (warning) was at the end, direct from Perl:
Use of uninitialized value $author in sprintf at /u/karl/gnu/src/vkarl/VC.pm line 210.
Use of uninitialized value $author in sprintf at /u/karl/gnu/src/vkarl/VC.pm line 210.
I was not left in a good state. There seemed to be no good way to
recover from this, since the erroneous ChangeLog was already committed,
so vcd did not think there were any files in the ChangeLog lines.
So I ended up doing rm -rf .git/c/.git and running vcd --init again to
restart my CL repo, and also
git fetch && git reset --hard origin && git checkout && git submodule update
to eradicate all my changes (after saving the actual diff :) in the
source repo. Thankfully, that apparently erased the memory of the bad CL
so I could proceed.
Instead of worrying about the exact number of spaces, I wonder about
parsing attr lines by checking that first word is a YYYY-MM-DD date, the
last word is <an <at> email.adr>, and considering the words in between to be
the real name.
Reasonable error msgs would then be easy to give if the first and last
words don't fit the expected syntax. And if there is no author, it
could give up at that point. After all, vcd relies on all kinds of
finicky details about the CL, so seems like it might as well force a
good attr line too instead of accepting bad ones.
If the idea seems ok, maybe one of us (or a new contributor!) can work
in that direction eventually. --best, karl.
This bug report was last modified 5 years and 144 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.