From: Eric Wong <normalperson@yhbt.net>
To: doki_pen <doki_pen@doki-pen.org>
Cc: git@vger.kernel.org
Subject: Re: minor git-svn bug
Date: Thu, 2 Jul 2009 23:24:16 -0700 [thread overview]
Message-ID: <20090703062416.GA23128@dcvr.yhbt.net> (raw)
In-Reply-To: <4A4CEB81.4080309@doki-pen.org>
doki_pen <doki_pen@doki-pen.org> wrote:
> Is this the right place to bring up bugs? Or only patches? Anyway, I
> found a small bug.
Yes to both. Also, feel free to Cc: me on git svn questions since
it halves the chance of me losing track of it.
> Due to some strange structure on the svn host, I have manually added the
> fetch lines to the [svn-remote] section of config. There are hundreds
> of branches and tags, so I only have lines for what I need. I removed
> one that I thought I didn't need anymore, and also removed the remote
> tracking branch. When I discovered that I needed the branch again, I
> added it back to svn-remotes and did a git svn fetch. There were no new
> commits on the branch, so the remote tracking branch was not recreated.
> The work around was to do a commit on the branch via svn, then git svn
> fetch. This caused the remote tracking branch to reappear. --
If you have reflogs (on by default), then it would've been possible to
recreate the ref without hitting the network at all by creating the
ref based on the reflog.
git svn not detecting that a remote ref was manually removed was
probably caused by lingering metadata in .git/svn/$remote_branch/.
Clobbering that directory alone should've been sufficient for
"git svn fetch" to work...
--
Eric Wong
prev parent reply other threads:[~2009-07-03 6:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 17:16 minor git-svn bug doki_pen
2009-07-03 6:24 ` Eric Wong [this message]
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=20090703062416.GA23128@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--cc=doki_pen@doki-pen.org \
--cc=git@vger.kernel.org \
/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