git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: Troy Telford <ttelford.groups@gmail.com>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: git-svn bug?
Date: Sun, 19 Nov 2006 08:52:21 -0800	[thread overview]
Message-ID: <20061119165221.GA6478@soma> (raw)
In-Reply-To: <op.ti6irtilzidtg1@rygel.lnxi.com>

Troy Telford <ttelford.groups@gmail.com> wrote:
> My 'dummy' repo was imported using git-svn.
> My 'real' repo was imported using git-svnimport.
> 
> Having not read any of the code, I'm just taking a wild guess; but is it  
> reasonable to say that since the repository was originally imported to git  
> using git-svnimport (rather than git-svn), git-svn doesn't have some of  
> the data it needs to push to the remote svn repo?

Exactly, git-svn needs the git-svn-id: lines at the end of each commit
for 'commit' and 'dcommit' to work.  So using a repo created by
git-svnimport will not work.

'commit-diff' will work, however it's intended as a low-level command
('commit' should be that, too).

> Would it be reasonable to use git-svn to import the SVN repository into a  
> new git repo, and then rebase from the old git-svnimport'ed repo into the  
> new git-svn imported one?  (did that even make sense?!?)

Yes, something along those lines would work.

-- 

  reply	other threads:[~2006-11-19 16:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-15 21:05 git-svn bug? Troy Telford
2006-11-15 21:43 ` Junio C Hamano
2006-11-15 22:55   ` Troy Telford
2006-11-17  8:55     ` Eric Wong
2006-11-17 21:17       ` Troy Telford
2006-11-19 16:52         ` Eric Wong [this message]
2006-11-15 22:33 ` Seth Falcon
2006-11-15 22:37   ` Shawn Pearce
2006-11-16 15:32     ` Seth Falcon
2006-11-15 23:09   ` Troy Telford

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061119165221.GA6478@soma \
    --to=normalperson@yhbt.net \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=ttelford.groups@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).