public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Joel Brobecker'" <brobecker@adacore.com>, <archer@sourceware.org>
Subject: RE: [Archer] Re: [Archer] Archer git account inquiry
Date: Wed, 23 Feb 2011 09:08:00 -0000	[thread overview]
Message-ID: <000f01cbd339$32d6b6c0$98842440$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <20110223033007.GA19610@adacore.com>

  I don't really care about where I put my modifications,
if nobody is against it, archer repository is fine with me.

  Related question: should I change the wiki page
to add my branch? Do I need to logon somewhere for this?

Coming back to the primary reason of my request for git account:
I am mainly interested in an easier way to split 
larges patches into several sub-patches like many of you
are doing.

  So my main question is:
what do you use to create your email series with sub-patches?
-- git alone?
or stgit, guilt or Quilt?

How do you handle ChangeLog entries for instance?
do you really put them into the commits, but then
they would appear formatted as a diff in the patch also
or do you have special scripts for this?

 Thanks in advance,

Pierre
> -----Message d'origine-----
> De : archer@sourceware.org [mailto:archer@sourceware.org] De la part de
> Joel Brobecker
> Envoyé : mercredi 23 février 2011 04:30
> À : Tom Tromey
> Cc : Pierre Muller; archer@sourceware.org
> Objet : Re: [Archer] Re: [Archer] Archer git account inquiry
> 
> > > It would be fine with me as long as writing to gdb.git does not
> mess
> > > with the automatic cvs importer, or somehow interfere with our
> ability
> > > to move to git in the future.
> > >
> > > I don't really know anything about how the cvs->git import works,
> so
> > > maybe this is a needless concern.
> >
> > I will ask Jim.
> 
> Jim confirmed that, as long as we don't write to the "master" branch,
> everything should be fine.  I think it would be fairly straightforward
> to install a hook that prevents updates to that branch except for one
> user.
> 
> So we have 3 alternatives. Pierre publishes his own gdb.git repo (could
> be using some of the git hosting sites???), uses Archer, or uses
> gdb.git.
> 
> --
> Joel

  reply	other threads:[~2011-02-23  9:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-21 13:27 Pierre Muller
2011-02-21 14:22 ` [Archer] " Joel Brobecker
2011-02-21 14:34   ` Tom Tromey
2011-02-22  4:25     ` [Archer] " Joel Brobecker
2011-02-23  3:30       ` Joel Brobecker
2011-02-23  9:08         ` Pierre Muller [this message]
2011-02-23  9:19           ` [Archer] " Joel Brobecker
2011-02-23 20:21           ` Tom Tromey
2011-02-24 11:01           ` Jan Kratochvil
2011-02-24 11:11             ` Pierre Muller
2011-02-24 11:20               ` Pierre Muller
2011-02-24 11:29               ` Jan Kratochvil
2011-02-23 20:23         ` Tom Tromey
2011-02-24  3:22           ` [Archer] " Joel Brobecker
2011-02-21 14:31 ` Tom Tromey
2011-02-24 11:05   ` Pierre Muller

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='000f01cbd339$32d6b6c0$98842440$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.fr \
    --cc=archer@sourceware.org \
    --cc=brobecker@adacore.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).