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: Mon, 04 Feb 2019 16:33:00 -0000	[thread overview]
Message-ID: <20190204163344.GA2829@embecosm.com> (raw)
In-Reply-To: <878sywvnqx.fsf@redhat.com>

* Frank Ch. Eigler <fche@redhat.com> [2019-02-03 11:29:58 -0500]:

> 
> andrew.burgess wrote:
> 
> > I would like to discuss the idea of converting CGEN from CVS to git.
> 
> No objections here, glad to see someone is still interested!  Agreed
> that old branches are disposable, that a straight main branch cvs-to-git
> conversion is sufficient.  Any objections to just doing it?
> 
> It could be nice if someone (tm) were to pursue merging cgen into
> binutils proper, but that is a separate issue.

Yes we _could_ add CGEN to binutils (assuming we could resolve the FSF
copyright assignment), but should we?

I know right now, binutils/gdb are the only real users, but that
doesn't have to always be the case, ideally CGEN could be used for
more than just generating parts of binutils/gdb, and in that case
having the tools jammed into binutils-gdb would be a little odd.

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

Thanks,
Andrew

  parent reply	other threads:[~2019-02-04 16:33 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 [this message]
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
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=20190204163344.GA2829@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).