Re: Test GCC conversion with reposurgeon available

[Segher Boessenkool <segher@kernel.crashing.org>]

On Wed, Dec 25, 2019 at 03:36:38PM +0000, Joseph Myers wrote:
> On Wed, 25 Dec 2019, Andreas Schwab wrote:
> 
> > On Dez 25 2019, Joseph Myers wrote:
> > 
> > > Timezones for any email address can be specified in gcc.map for any 
> > > authors wishing to have an appropriate timezone used for their commits.
> > 
> > But that should not be used for unrelated authors.
> 
> It's not.
> 
> On investigation, I think you are referring to the conversion of r269472.  
> That was committed for you by Jim Wilson and thus has you as author and 
> Jim Wilson as committer and Jim Wilson's timezone entry has been applied.  
> So the argument here is that the author's timezone information should be 
> applied to the author date, and the committer's timezone information 
> should be applied to the committer date.  I expect that should be 
> straightforward (although when coming from SVN, there's also an argument 
> that we only have committer dates so the committer timezone is the 
> relevant one to apply).

Or we could just not make up any time zone at all.  The information
isn't there, what is gained by faking something?

Having people's real names is obviously useful.  Showing the email
address they used when they did the patch (which can be an indication of
affiliation, for example) can also be useful, but less so, and is harder
to get right.  But the timezone some patch was made in (or committed in)?

The goal is not to pretend we never used SVN.  The goal is to have a Git
repo that is as useful as possible for us.  For me, that means the stuff
inherited from the older repos should be just that: exactly what was
there before.  With annoyances like real name fixed, perhaps, and maybe
actual errors fixed (although I never in practice saw *any* error that
made anything even the slightest bit harder to do).

But no lipstick.


Segher