public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Burgess <andrew.burgess@embecosm.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: cgen@sourceware.org, nickc@redhat.com
Subject: Re: Converting CGEN from CVS to git
Date: Sun, 21 Apr 2019 16:23:00 -0000	[thread overview]
Message-ID: <20190421162351.GA2737@embecosm.com> (raw)
In-Reply-To: <20190327200946.GA18828@redhat.com>

* Frank Ch. Eigler <fche@redhat.com> [2019-03-27 16:09:46 -0400]:

> Hi, Andrew -
> 
> > > The mail is here, this describes the process I went through and
> > > some of the choices I made.
> > >   https://www.sourceware.org/ml/cgen/2019-q1/msg00000.html
> > > The link to my conversion is here:
> > >   git@github.com:T-J-Teru/cgen.git
> > >   git@github.com:T-J-Teru/cgen-2-git.git
> 
> OK, those look OK.  With respect to email addresses, retaining
> <userid@sourceware.org> as a fallback is fine.

I hadn't originally realised / remembered that userid@sourceware.org
was a valid email address, so I mostly just hunted back through the
mailing lists looking for the last email that each user used.

Do you think it might be better if I just used the sourceware email
for anyone who hasn't been seen in say, the last 3 months?

> 
> > How would you feel if I reached out to the sourceware overseers list
> > to get an empty git repository setup (I guess that's the right place
> > to ask)?
> 
> I set up this for us/you now, and have given you cgen group membership.
> You should be able to commit your work to ssh://sourceware.org/git/cgen.git/
> and take it forward.  Thanks for taking the initiative!

Thanks for doing this.  I know have a little time available again, so
I'm hoping to get this sorted soon.

Once I know how you feel on the email question, I'll do a final
conversion and push it up.

Thanks,
Andrew

  reply	other threads:[~2019-04-21 16:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-31 19:50 Andrew Burgess
2019-02-02  9:35 ` Jose E. Marchesi
2019-02-03 16:30 ` Frank Ch. Eigler
2019-02-04  8:25   ` Jose E. Marchesi
2019-02-04 13:51     ` Frank Ch. Eigler
2019-02-04 16:33   ` Andrew Burgess
2019-03-03 22:38     ` Frank Ch. Eigler
2019-03-06 13:28       ` Andrew Burgess
2019-03-27 14:32         ` Andrew Burgess
2019-03-27 20:09           ` Frank Ch. Eigler
2019-04-21 16:23             ` Andrew Burgess [this message]
2019-04-21 16:42               ` Frank Ch. Eigler
2019-04-21 19:39                 ` Andrew Burgess
2019-04-21 21:32             ` Andrew Burgess
2019-04-22  9:43               ` Jose E. Marchesi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190421162351.GA2737@embecosm.com \
    --to=andrew.burgess@embecosm.com \
    --cc=cgen@sourceware.org \
    --cc=fche@redhat.com \
    --cc=nickc@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).