Git development
 help / color / mirror / Atom feed
* minor git-svn bug
@ 2009-07-02 17:16 doki_pen
  2009-07-03  6:24 ` Eric Wong
  0 siblings, 1 reply; 2+ messages in thread
From: doki_pen @ 2009-07-02 17:16 UTC (permalink / raw)
  To: git

Is this the right place to bring up bugs?  Or only patches?  Anyway, I 
found a small bug.

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. 

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: minor git-svn bug
  2009-07-02 17:16 minor git-svn bug doki_pen
@ 2009-07-03  6:24 ` Eric Wong
  0 siblings, 0 replies; 2+ messages in thread
From: Eric Wong @ 2009-07-03  6:24 UTC (permalink / raw)
  To: doki_pen; +Cc: git

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2009-07-03  6:24 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-07-02 17:16 minor git-svn bug doki_pen
2009-07-03  6:24 ` Eric Wong

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox