|
From: Daniel J S. <dan...@ie...> - 2017-10-16 20:07:45
|
On 10/16/2017 02:48 PM, Ethan A Merritt wrote:
> On Monday, 16 October, 2017 14:27:09 Daniel J Sebald wrote:
>
> > > your name shows in the associated ChangeLog entry but
> > > has not been propagated to the patchset itself.
> > > Same for the next 5 most ChangeLog entries with your name.
> > > So it does seem that your name in particular is failing to trigger a
> > > match event in the annotation process.
> >
> > There are probably more. For example
> >
> > <sfeam!2015-09-11T19:48:01+00:00Z> 2015-09-11 Akira Kakuto
> > <ka...@fu...>
> >
> > doesn't appear in the log either.
> >
>
> Yeah. I only looked for your name in particular because you
> raised the issue.
>
> But you know what? I don't think it matters that much, at least
> for viewing through the SourceForge interface. However it is that
> you ended up with a commit identifier, once you click on it the
> first thing shown is the ChangeLog entry with authorship
> attribution.
I'm fine with having the detailed ChangeLog entry there as the first
diff. But the main reasons for having the proper authorship in the
changeset is for searching purposes, i.e.
git log | less
In less one can then search for changesets authored by whomever to get
an idea of when something was done, etc. We have the info, something
I'm even wondering if we could even replace the "empty log message" with
some estimate of a message extracted from the corresponding ChangeLog
entry. But, there are only 210 such messages:
git log | grep "empty log message" | wc
210 1050 6300
Maybe those could be replaced by hand (if at all), everyone doing five
or ten summary lines, but it isn't that important.
Dan
|