From: jemarch@gnu.org (Jose E. Marchesi)
To: fche@redhat.com (Frank Ch. Eigler)
Cc: Andrew Burgess <andrew.burgess@embecosm.com>,
cgen@sourceware.org, nickc@redhat.com
Subject: Re: Converting CGEN from CVS to git
Date: Mon, 04 Feb 2019 08:25:00 -0000 [thread overview]
Message-ID: <87h8dk6jut.fsf@gnu.org> (raw)
In-Reply-To: <878sywvnqx.fsf@redhat.com> (Frank Ch. Eigler's message of "Sun, 03 Feb 2019 11:29:58 -0500")
> 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.
What work would be required to achieve that, other than adding the cgen
subdirectory to the binutils repo?
As far as I can see, CGEN is officially still part of binutils, and you
and Doug are listed as the domain maintainers in binutils/MAINTAINERS.
next prev parent reply other threads:[~2019-02-04 8:25 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 [this message]
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
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=87h8dk6jut.fsf@gnu.org \
--to=jemarch@gnu.org \
--cc=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).