This is the mail archive of the
mailing list for the GCC project.
Re: Offer of help with move to git
- From: "Eric S. Raymond" <esr at thyrsus dot com>
- To: Segher Boessenkool <segher at kernel dot crashing dot org>
- Cc: Florian Weimer <fw at deneb dot enyo dot de>, gcc at gcc dot gnu dot org
- Date: Sun, 23 Aug 2015 12:54:16 -0400
- Subject: Re: Offer of help with move to git
- Authentication-results: sourceware.org; auth=none
- References: <20150823144340 dot GA7448 at thyrsus dot com> <87fv3am4wj dot fsf at mid dot deneb dot enyo dot de> <20150823154859 dot GA8099 at thyrsus dot com> <87io86kn5n dot fsf at mid dot deneb dot enyo dot de> <20150823162625 dot GA8650 at thyrsus dot com> <20150823163616 dot GC16487 at gate dot crashing dot org>
- Reply-to: esr at thyrsus dot com
Segher Boessenkool <firstname.lastname@example.org>:
> On Sun, Aug 23, 2015 at 12:26:25PM -0400, Eric S. Raymond wrote:
> > One way to do it would be to mine the list archives for not just names
> > but name-date pairs. With a little scripting work that could be processed
> > into a sequence of map files, each one valid for a known span of dates. The
> > only assumption required is that an email address is valid for a person
> > until explicitly superseded by a different address in the archive.
> We also have a MAINTAINERS file (in the toplevel dir of the repo) that
> should hold useful email addresses for everyone, at any point in time.
> Of course sometimes people forget to update it. It also does not hold
> the actual account names, but you can almost always get those from the
> checkin to the MAINTAINERS file itself (or correlate with ChangeLogs,
> etc.) Won't that work better than the ML archives?
Ah, yes, it probably will, for all but contributors who have been gone
since before that practice was established. I hadn't actually looked
at the distribution yet.
Because people tend to re-use their favored Unix usernames, I usually
find that they can be matched up by eyeballing the MAINTAINERS file
without much difficulty.
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>