From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-200266-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 41521 invoked by alias); 24 Sep 2019 22:31:10 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 41342 invoked by uid 89); 24 Sep 2019 22:30:51 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=HX-Languages-Length:1003, price, pay
X-HELO: mail-wm1-f65.google.com
Received: from mail-wm1-f65.google.com (HELO mail-wm1-f65.google.com) (209.85.128.65) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 24 Sep 2019 22:30:31 +0000
Received: by mail-wm1-f65.google.com with SMTP id r19so608161wmh.2        for <gcc@gcc.gnu.org>; Tue, 24 Sep 2019 15:30:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=gmail.com; s=20161025;        h=mime-version:references:in-reply-to:from:date:message-id:subject:to         :cc;        bh=3U/8PprvjRmJGEsE58sXC6tNqGAF1xk1xULPyCyGC8s=;        b=AyU47o+v1whUFFcfqxuOkU1zX1TmZP2tJcrMbY5mIoWLSmRg+ABYq+hzfGT6SjAAe7         BsfWMiG9+g+ZKS8YrRZa8B/r4ZRxb1qLhJslT7dRJrOp3P0DKn//di+9DuBTuy3Qm2KZ         mSVSzTUp6XUVjHFHWzhxWY3v8R9eegUR+Bw25e1AVN/EdAb2d5cF1XXBO6Cvv1fsaN0x         Nqr4f+L0wnibirqn/iWkEjVopmZ581fLYkCGv9Pci50vo9INuhkajrsEX9uMq0g96CLI         Slk742jGuuR5GGo3Fa9AR3bLkEgKMXjjxGmRXvJRz9dGOc8cuAgkt6wf97zYIZiHW/1t         dM/Q==
MIME-Version: 1.0
References: <alpine.DEB.2.21.1909150212460.10798@digraph.polyomino.org.uk> <alpine.DEB.2.21.1909242046110.14213@digraph.polyomino.org.uk> <CAH6eHdQFyBjG8Yfo3kh+ogwt_RZ17rQqK-biA8-0byLmjJKD7A@mail.gmail.com> <alpine.DEB.2.21.1909242212040.14213@digraph.polyomino.org.uk>
In-Reply-To: <alpine.DEB.2.21.1909242212040.14213@digraph.polyomino.org.uk>
From: Jonathan Wakely <jwakely.gcc@gmail.com>
Date: Tue, 24 Sep 2019 22:31:00 -0000
Message-ID: <CAH6eHdSZVVVipMv5Ybxr7F0VqVLm=4YB5SkF7hDn6Y9VpBi35g@mail.gmail.com>
Subject: Re: git conversion of GCC wwwdocs repository
To: Joseph Myers <joseph@codesourcery.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Content-Type: text/plain; charset="UTF-8"
X-IsSubscribed: yes
X-SW-Source: 2019-09/txt/msg00218.txt.bz2

On Tue, 24 Sep 2019 at 23:15, Joseph Myers wrote:
>
> On Tue, 24 Sep 2019, Jonathan Wakely wrote:
>
> > On Tue, 24 Sep 2019 at 21:46, Joseph Myers wrote:
> > >
> > > Would anyone like to make any comments on this conversion from CVS to git?
> >
> > It looks pretty good. I note that the author map just uses the
> > committer's current email address, meaning I have commits using my
> > @redhat.com address nearly a decade before I started working at Red
> > Hat. But that's a small price to pay for moving from CVS to Git in my
> > opinion. And t's arguably correct to have all my commits under one
> > identity rather than several different ones anyway.
>
> If people prefer to use @gcc.gnu.org addresses, that's a small matter of
> adjusting the postprocessing of the author map from the gcc-conversion
> repository to replace the addresses there with username@gcc.gnu.org while
> keeping the names from that author map.

I don't feel strongly about it.