public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>, archer@sourceware.org
Subject: Re: [Archer] Archer git account inquiry
Date: Mon, 21 Feb 2011 14:34:00 -0000	[thread overview]
Message-ID: <m3hbbxtq1z.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20110221142157.GF2617@adacore.com> (Joel Brobecker's message of "Mon, 21 Feb 2011 18:21:57 +0400")

Joel> That being said, this is something I remember us talking about
Joel> at the GCC Summit - opening the git mirror up for development
Joel> branches, rather than using the Archer repository.  I don't think
Joel> anyone had any problems with that idea back then.

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.

Joel> One of the issues (not sure) with using Archer, might be the frequency
Joel> at which the "master" branch is updated in the Archer repo.  With the
Joel> official git mirror, it's updated every 30mins.

We don't update automatically at all.

We used to have this idea of having an archer integration branch, but we
pretty much gave up on it.  We didn't need it.

What I do now is clone from both archer and gdb.git.  I generally make
new feature branches based on gdb/master, but then push them to archer.

We should probably update our wiki instructions to remove the old gunk.
And, I've been thinking of finally taking Jan's advice from 2 years ago
and deleting some of the dead branches.

Tom

  reply	other threads:[~2011-02-21 14:34 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 [this message]
2011-02-22  4:25     ` [Archer] " Joel Brobecker
2011-02-23  3:30       ` Joel Brobecker
2011-02-23  9:08         ` Pierre Muller
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=m3hbbxtq1z.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=archer@sourceware.org \
    --cc=brobecker@adacore.com \
    --cc=pierre.muller@ics-cnrs.unistra.fr \
    /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).