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

Re: [PATCH v2] git-svn: use SVN::Ra::get_dir2 when possible

From
HLHin-Tak Leung <htl10@users.sourceforge.net>
Date
Nov 1, 2014, 06:13 UTC
Message-ID
<1414822394.95382.YahooMailBasic@web172305.mail.ir2.yahoo.com>
In-Reply-To
<20141101031352.GA17306@dcvr.yhbt.net>

-------------------------------------------- On Sat, 1/11/14, Eric Wong <normalperson@yhbt.net> wrote:

 Hin-Tak Leung <htl10@users.sourceforge.net>
 wrote:
> > While my 2.10 + 11 patches
 continue to fetch, where it was stuck, now
 > it does "Couldn't find
 revmap..." - also, the single branch clone is doing
 > the 'trunk/branches/... thing - are
 these supposed to happen?
 
> I'm afraid this is a problem with the vbox
 repo not publishing anything
 but trunk, but
 their svn:mergeinfo refers to non-public branches.
 
> This shows only changes to
 trunk:
 
>     svn log -v http://www.virtualbox.org/svn/vbox
> I do not know what their
 development process is like.  From the looks of
 it, every change is made by a
 "vboxsync" user.  I suspect that's driven
 by an automated export script, and the real
 development happens in a
 different (private)
 repo...
 
They are Sun/Oracle technology so have that sort of style, I think.
(Think Java and everything to do with Java).

I did get a bit confused about that - their web code broswing interface shows a number of merges and deleted branches.

Previous: Eric Wong
Message 5 of 5 in “Re: [PATCH v2] git-svn: use SVN::Ra::get_dir2 when possible”
  1. Hin-Tak LeungOct 31, 2014
  2. Eric WongOct 31, 2014
  3. Hin-Tak LeungNov 1, 2014
  4. Eric WongNov 1, 2014
  5. Hin-Tak LeungNov 1, 2014

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.