From: jemarch@gnu.org (Jose E. Marchesi)
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: cgen@sourceware.org
Subject: Re: Converting CGEN from CVS to git
Date: Sat, 02 Feb 2019 09:35:00 -0000 [thread overview]
Message-ID: <87r2cqsfc5.fsf@gnu.org> (raw)
In-Reply-To: <20190131195017.GB17699@embecosm.com> (Andrew Burgess's message of "Thu, 31 Jan 2019 19:50:17 +0000")
I would like to discuss the idea of converting CGEN from CVS to git.
Motivation
==========
I have been working with CGEN off and on for the last 8 years, and
though I haven't posted any fixes upstream in that time, I do have a
set of fixes locally that I would like to try an upstream over the
next year.
Obviously, moving from CVS to git isn't a requirement for working on
this project, but hopefully we can all agree that moving out of CVS
makes development easier, and git seems like the obvious choice.
Yay! That would be great, moving the project to git.
I am also using CGEN, for a new target, and have also hacks I will want
to upstream at some point.
The observation that in order to regenerate the CGEN components, the
only part of the cgen CVS module that needed to be copied into the
binutils-gdb was the cgen/ subdirectory was the reasoning behind one
big choice I made, that is:
Only the cgen subdirectory of the current cgen CVS module would be
included in the new git repository. Everything else is unneeded
clutter, and should be discarded.
Makes full sense.
I don't have permissions to create a git repository on sourceware, or
change the admin settings on CVS, nor am I sure who to approach. When
we get that far any advice would be great.
The overseers@sourceware.org may be able to help?
Finally, is there anything else I can or should do to help make this happen?
Thanks for working on this.
next prev parent reply other threads:[~2019-02-02 9:35 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 [this message]
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
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=87r2cqsfc5.fsf@gnu.org \
--to=jemarch@gnu.org \
--cc=andrew.burgess@embecosm.com \
--cc=cgen@sourceware.org \
/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).