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

git svn show-externals output format

From
AGAlexander Groß <agross@therightstuff.de>
Date
Aug 19, 2017, 08:24 UTC
Message-ID
<CACcHa=NYgir8HDeR1ES9mKsqTQYk=90Z38csTgK-vfD=fQmHLg@mail.gmail.com>
Hi all,

I am playing with svn-to-git conversion and wanted to have a look at the svn:externals of a test SVN repository.

$ git svn clone svn://svn.code.sf.net/p/svn-to-git/code/ svn-to-git-code
The SVN repo in HEAD revision contains three externals:

$ cd svn-to-git-code $ git svn show-externals

# /trunk/ /trunk/https://svn.code.sf.net/p/gc-webdav/svn webdav /trunk/https://svn.code.sf.net/p/gc-webdav/svn@1 webdav-at-revision

# /trunk/sub directory/ /trunk/sub directory/https://svn.code.sf.net/p/gc-webdav/svn 'webdav in subdir'

An earlier version contains just one external:
$ git svn show-externals --revision 8

# /trunk/ /trunk/webdav https://svn.code.sf.net/p/gc-webdav/svn/

It seems like the output is inconsistent. In SVN revision 8 the output looks like it's formatted like <path> <URL>

In the HEAD revision it looks mangled <path prefix><URL> <path suffix>

This makes consuming the output of git svn show-externals in HEAD difficult because the parts are not clearly separated by space and sometimes the path is the first element, sometimes it's a combination of first and last elements.

I am able to checkout both revisions including externals using native svn.
Am I doing something wrong?
Thanks!
Alex
-- 
Alexander Groß
http://therightstuff.de/
Next: Andreas Heiduk
Message 1 of 3 in “git svn show-externals output format”
  1. Alexander GroßAug 19, 2017
  2. Andreas HeidukAug 19, 2017
  3. Alexander GroßAug 19, 2017

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.