From: Steven Grimm <koreth@midwinter•com>
To: git@vger•kernel.org
Subject: git-svn: follow parent after the fact?
Date: Mon, 18 Dec 2006 17:14:50 -0800 [thread overview]
Message-ID: <45873D0A.1040804@midwinter.com> (raw)
One of the other git users here just noticed that his git-svn clone of a
particular svn repo has an inconsistent set of files compared to the svn
client. Turns out the repo has had its trunk moved around in the past. A
fresh clone with --follow-parent (which he didn't use) produces the
correct results.
Obviously he can blow away his current repo and make a new one, but it'd
be nicer if he could preserve his local change history. Is there any way
to retroactively apply the additional changes --follow-parent would have
applied if it had been used on the initial fetch?
It would be better, IMO, if you didn't have to figure out whether or not
a given remote svn repository has had branch renames in the past in
order to figure out if you need to provide an extra option to git-svn
fetch. Maybe --follow-parent should be the default behavior and there
should be an option to turn it off? Or is there a good reason to not
want that behavior most of the time? My assumption is that it's not the
default simply because it's a recent addition.
By the way, I'm completely in favor of renaming commit to set-tree. +1
for that change.
next reply other threads:[~2006-12-19 1:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 1:14 Steven Grimm [this message]
2006-12-19 7:47 ` git-svn: follow parent after the fact? Eric Wong
2006-12-19 21:36 ` Steven Grimm
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=45873D0A.1040804@midwinter.com \
--to=koreth@midwinter$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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