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

Re: git-svn confused by "empty" (svn prop change) commit

From
SRSverre Rabbelier <alturin@gmail.com>
Date
Nov 21, 2008, 06:32 UTC
Message-ID
<bd6139dc0811202232l592ea240s89088f78014b6906@mail.gmail.com>
In-Reply-To
<m23ahlj26u.fsf@gmail.com>
On Fri, Nov 21, 2008 at 02:30, paulfred <paul.fredrickson@gmail.com> wrote:
Show 9 quoted lines
> $ git svn dcommit
> Unable to determine upstream SVN information from HEAD history.
> Perhaps the repository is empty. at /usr/local/libexec/git-core/git-svn line 435.
>
> So apparently my problem is NOT the empty commit at all, but trying to use
> noMetadata.  I am surprised that it fails on a fresh download though. Is there
> something I might have done while hacking that would cause git-svn to lose
> track of trunk again?  Is my only option to convince everyone to ignore
> the "noise" in my comments?

Uhm, as I understand it, git svn needs that metadata to dcommit, unless the .git/svn/git-svn/.rev_db is intact. The --no-metadata switch should be used only when you're doing a one-time import of a svn repo. During my usage of git svn, it removed the git-svn-id tags from the commit message when you 'git svn dcommit', so I don't understand why you need to use --no-metadata in the frist place.

-- 
Cheers,

Sverre Rabbelier
Previous: paulfred
Message 3 of 3 in “git-svn confused by "empty" (svn prop change) commit”
  1. paulfredNov 20, 2008
  2. paulfredNov 21, 2008
  3. Sverre RabbelierNov 21, 2008

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.