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

Re: Problem with git-svn

From
EWEric Wong <normalperson@yhbt.net>
Date
Dec 20, 2007, 18:30 UTC
Message-ID
<20071220183007.GA26767@untitled>
In-Reply-To
<47690031.7090409@obry.net>
Pascal Obry <pascal.obry@gmail.com> wrote:
Show 31 quoted lines
> Hi Eric,
> 
> > Can you show me the output of `svn log -v -r9458 svn+ssh://myserver/'?
> 
> $ svn log -v -r9458  svn+ssh://myserver/
> ------------------------------------------------------------------------
> r9458 | (no author) | 1998-04-22 19:07:08 +0200 (Wed, 22 Apr 1998) | 1 line
> Changed paths:
>    A /importfromcvs
>    A /importfromcvs/branches
>    A /importfromcvs/tags
>    A /importfromcvs/trunk
> 
> New repository initialized by cvs2svn.
> ------------------------------------------------------------------------
> 
> > So did svn+ssh://importfromcvs/trunk/file.el at r9458?  If so, git-svn
> > is behaving as expected.  If not, can you tell me where "file.el" was at
> > r9458?
> 
> file.el was not imported at r9458 but at r9459, just after the creation
> of the /importfromcvs directories above.
> 
> ------------------------------------------------------------------------
> r9459 | author | 1998-04-22 19:07:08 +0200 (Wed, 22 Apr 1998) | 2 lines
> Changed paths:
>    A /importfromcvs/trunk/file.el
> 
> Initial revision
> 
> ------------------------------------------------------------------------

Ah, oops, I was off-by-one with the revision number. But git-svn does look to be doing the right thing here, because it followed history into /importfromcvs/trunk/ and file.el was part of it.

-- 
Eric Wong
Previous: Pascal ObryNext: Pascal Obry
Message 6 of 11 in “Problem with git-svn”
  1. Pascal ObryDec 16, 2007
  2. Peter BaumannDec 16, 2007
  3. Pascal ObryDec 16, 2007
  4. Eric WongDec 19, 2007
  5. Pascal ObryDec 19, 2007
  6. Eric WongDec 20, 2007
  7. Pascal ObryDec 20, 2007
  8. Pascal ObryDec 21, 2007
  9. Eric WongDec 22, 2007
  10. Pascal ObryDec 22, 2007
  11. Pascal ObryDec 20, 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.