From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: Jeff King <peff@peff.net>, git <git@vger.kernel.org>
Subject: Re: [RFC] Mirroring svn
Date: Thu, 6 Dec 2007 12:15:47 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0712061214340.27959@racer.site> (raw)
In-Reply-To: <1196923525.10408.103.camel@brick>
Hi,
On Wed, 5 Dec 2007, Harvey Harrison wrote:
> On Thu, 2007-12-06 at 01:43 -0500, Jeff King wrote:
> > On Wed, Dec 05, 2007 at 10:22:33PM -0800, Harvey Harrison wrote:
> >
> > > // fetching someone else's remote branches is not a standard thing to do
> > > // so we'll need to edit our .git/config file
> > > // you should have a section that looks like:
> > > [remote "gcc.gnu.org"]
> > > url = git://git.infradead.org/gcc.git
> > > fetch = +refs/heads/*:refs/remotes/gcc.gnu.org/*
> > > // infradead's mirror puts the gcc svn branches in its own namespace
> > > // refs/remotes/gcc.gnu.org/*
> > > // change our fetch line accordingly
> > > [remote "gcc.gnu.org"]
> > > url = git://git.infradead.org/gcc.git
> > > fetch = +refs/remotes/gcc.gnu.org/*:refs/remotes/gcc.gnu.org/*
> >
> > FWIW, if you are writing a shell recipe for other people to cut and
> > paste, you can say this as:
> >
> > git config remote.gcc.gnu.org.fetch \
> > '+refs/remotes/gcc.gnu.org/*:refs/remotes/gcc.gnu.org/*'
>
> I thought about that, but I like to encourage people to actually look at
> the config file, it's pretty easy to understand.
I agree that people should be encouraged to edit their .git/config. But a
recipe is something easy-to-follow IMHO, so I would write this as a shell
script (with #-comments, not //-comments).
Ciao,
Dscho
next prev parent reply other threads:[~2007-12-06 12:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 6:22 [RFC] Mirroring svn Harvey Harrison
2007-12-06 6:43 ` Jeff King
2007-12-06 6:45 ` Harvey Harrison
2007-12-06 12:15 ` Johannes Schindelin [this message]
2007-12-06 12:18 ` Harvey Harrison
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=Pine.LNX.4.64.0712061214340.27959@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=harvey.harrison@gmail.com \
--cc=peff@peff.net \
/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 NNTP newsgroup(s).