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: Wed, 27 Mar 2019 14:32:00 -0000	[thread overview]
Message-ID: <20190327143240.GZ10887@embecosm.com> (raw)
In-Reply-To: <20190306132831.GC10887@embecosm.com>

* Andrew Burgess <andrew.burgess@embecosm.com> [2019-03-06 13:28:31 +0000]:

> * Frank Ch. Eigler <fche@redhat.com> [2019-03-03 17:38:40 -0500]:
> 
> > Hi -
> > 
> > > [...]
> > > Could we not start in a separate repository, then if we find that
> > > there is some problem that would be made easier by having the source
> > > in bintuils-gdb we can do that later?
> > > 
> > > Part of my motivation for patching binutils-gdb to not require CGEN
> > > in-tree was a vision of a future where CGEN would exist as a true
> > > standalone utility that was simply used by binutils (like gcc, flex,
> > > etc).
> > 
> > We've dropped the ball on this thread.  I'd be happy to look over
> > someone else's cvs-git conversion for this (src/cgen + src/cpu?),
> > or try my own.  There are no blockers to having it on sourceware.
> 
> The original thread included links to my attempt at getting this done:
> 
> 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
> 
> And the scripts I used to make the conversion (if you wanted to build
> on them at all) are here:
> 
>   git@github.com:T-J-Teru/cgen-2-git.git
> 
> I would value any feedback you have.
> 
> I hadn't forgotten this thread, February got pretty busy for me, but I
> had scheduled some time this month to try and move this forward.
> 
> I look forward to your feedback.

Hi Frank,

Did you get a chance to look through the conversion?

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)?

Having the repository setup doesn't mean we're committed to a specific
conversion (or even converting at all), but having the repository
setup will probably take a while, so maybe we should get that ball
rolling.  Then once we agree on a specific conversion we can push it.

Thanks for your time,

Andrew

  reply	other threads:[~2019-03-27 14:32 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 [this message]
2019-03-27 20:09           ` Frank Ch. Eigler
2019-04-21 16:23             ` Andrew Burgess
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=20190327143240.GZ10887@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).