git/list[1] front-page[2] threads[3] people[4] search[5] about
 

git-svn: surprising behaviors/bugs?

From
GHGustaf Hendeby <hendeby@gmail.com>
Date
Nov 22, 2007, 13:37 UTC
Message-ID
<bf7b2dda0711220537h3f37c84ag899b74daa9a8fe1f@mail.gmail.com>

I've been running git for most my stuff for some time now, and am really pleased with what it has to offer. However, all my coworkers aren't gitified yet, and therefore I sometimes have to work with svn. I've learned to appreciate git-svn for this, since it lets me utilize the strengths of git and still allows for my coworkers to think I use their svn setup. Thanks to all who contribute to this wonderful tools!

In my work with git-svn I have stumbled upon the following two unexpected behaviors. Basically, am I doing/understanding something wrong, or is this buggy behavior in git-svn? (I'm presently using git 1.5.3.6, but have been experiencing these things for a while.)

1.  I don't really like svn's committer info, so I got an authorsfile
set.  This works great when I'm fetching/dcommitting from the
top-directory in my git checkout (the one with .git in), however, if
I'm in a subdirectory the authorsfile doesn't kick in and I get the
svn commiter info.  This is not a big deal, but a bit surprising and
my history gets a bit ugly.
2.  My second problem involves getting the support in git-svn for tags
and branches to work.  Having a standard layout of the svn repository,
in this case
   /source/project/(trunk|branch|tags)
svn clone -s only works as expected sometimes.  Sometimes I only get
the revision history, not including any actual content (ie none files
of the files under control turns up in git) from the clone.  When I
get this problem I usually clone the trunk only, and add tags myself.
This is far from optimal, and also error prone.  Other times, the
clone works as expected and gives me the tags and branches and all the
content.

I think the problem occurs when I'm not the owner of the svn repository, and only have access (read/write) to the project/(trunk|branch|tag) part, and don't have any access at all to source. Ie, svn ls works for /source/project and /source/project/trunk etc, but not /source (where I returns 403 Forbidden access). All svn access is through a svn-server that I can't control myself.

I've had a quick look in git-svn.perl, but the code is to beyond my limited perl knowledge. I'd be happy to provide more details if anyone is interested in looking deeper into this. Any ideas or comments are greatly appreciated!

/Gustaf
Next: Eric Wong
Message 1 of 3 in “git-svn: surprising behaviors/bugs?”
  1. Gustaf HendebyNov 22, 2007
  2. Eric WongNov 29, 2007
  3. Gustaf HendebyNov 29, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.