From: Grzegorz Kossakowski <grek@tuffmail.com>
To: Sam Vilain <sam@vilain.net>, git@vger.kernel.org
Subject: Re: How to clone git repository with git-svn meta-data included?
Date: Tue, 09 Dec 2008 21:57:06 +0100 [thread overview]
Message-ID: <493EDBA2.3070404@tuffmail.com> (raw)
In-Reply-To: <1228813734.28186.77.camel@maia.lan>
Sam Vilain pisze:
> It's up to the git-svn user to make sure that they prepare the refs to
> be what git-svn expects. This is something probably requiring more
> documentation and/or git-svn features to be easier.
What I was asking if we should add trunk ref to svn mirror so others cloning it will have
'origin/trunk' reference created automatically during clone process so no extra steps would be needed.
To be honest, I don't understand how Git exactly handles all this refs mapping and rewriting (e.g.
during cloning). Having said that, I cannot foresee all possible implications of choosing particular
method of solving current issues thus asking you.
>> Would it be the best practice?
>
> Well, obscure stuff should never really be best practice. The best practice
> is to have a single git repository that is where the svn -> git migration
> happens. And git-svn could perhaps auto-init based on information in the
> commit log or something. Best practice is to enhance the tool to work the
> way it Should(tm) :)
Cannot follow you here. We want single svn mirror but at the same time we want to our committers to
be able to push back to svn. What has been already proposed satisfies my need apart from the fact
that currently there is small problem with our mirror setup.
--
Best regards,
Grzegorz Kossakowski
next prev parent reply other threads:[~2008-12-09 20:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-06 12:15 How to clone git repository with git-svn meta-data included? Grzegorz Kossakowski
2008-12-07 8:43 ` Jacob Helwig
2008-12-08 0:03 ` Nick Andrew
2008-12-07 16:57 ` Peter Harris
2008-12-07 19:08 ` Grzegorz Kossakowski
2008-12-07 20:30 ` Peter Harris
2008-12-07 22:02 ` Grzegorz Kossakowski
2008-12-07 23:51 ` Peter Harris
2008-12-08 13:10 ` Michael J Gruber
2008-12-08 18:26 ` Grzegorz Kossakowski
2008-12-08 18:40 ` Peter Harris
2008-12-08 18:43 ` Grzegorz Kossakowski
2008-12-09 9:08 ` Sam Vilain
2008-12-09 20:57 ` Grzegorz Kossakowski [this message]
2008-12-09 8:53 ` Michael J Gruber
2008-12-08 16:10 ` Shawn O. Pearce
2008-12-08 19:04 ` Grzegorz Kossakowski
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=493EDBA2.3070404@tuffmail.com \
--to=grek@tuffmail.com \
--cc=git@vger.kernel.org \
--cc=sam@vilain.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).