Skip to contentSkip to conversation

git-svn and logging.. new to git

DISCUSSION Kenneth P. Turvey 3 participants 5 messages Jun 15, 2016

lore
Share & tools
lore

Kenneth P. Turvey

author
#0 lore raw

I'm in the process of moving to git from subversion and I've run into something I just don't understand. I've moved one project from subversion using git-svnimport and that went successfully. Unfortunately the latest git doesn't include svnimport so I'm trying to do the same thing with git-svn. It seems to have worked without any problem, but when I do "git log" I don't see all the entries I see when I do "svn log" on the same project in subversion. So, now I have to ask myself, "have I lost changes in the import?"

The command I used to import the source code is:

git-svn clone file:///home/kt/oldsvn/Personal/Projects/Journal \
--trunk=trunk --branches=branches --tags=tags

Am I doing something wrong here? Do I need additional options on the git-log command?

Any explanation or assistance would be greatly appreciated.

Thanks.

#1 lore raw
Quoted 9 lines · Kenneth P. Turvey

I'm in the process of moving to git from subversion and I've run into
something I just don't understand. I've moved one project from subversion using git-svnimport and that went successfully. Unfortunately the latest git doesn't include svnimport so I'm trying to do the same thing with git-svn. It seems to have worked without any problem, but when I do "git log" I don't see all the entries I see when I do "svn log" on the same project in subversion. So, now I have to ask myself, "have I lost changes in the import?"

Quoted 4 lines

The command I used to import the source code is:

  git-svn clone file:///home/kt/oldsvn/Personal/Projects/Journal \
  --trunk=trunk --branches=branches --tags=tags

git-svn creates a whole bunch of remote branches -- does "git branch -a" show them up?

Also, you can probably leave out the --trunk, etc., and just use --stdlayout.

Dave.

author
#2 lore raw
Quoted 5 lines · David Symonds

git-svn creates a whole bunch of remote branches -- does "git branch -a" show them up?

Also, you can probably leave out the --trunk, etc., and just use --stdlayout.

Thanks. That's good information to have. Is there a way to just do a straight import like in svnimport? Is svnimport still available somewhere or has it been completely superseded by git-svn?

Signature · 1 line
Kenneth P. Turvey <[email protected]>
#3 lore raw
Quoted 6 lines · Kenneth P. Turvey
Quoted 3 lines · David Symonds

git-svn creates a whole bunch of remote branches -- does "git branch -a" show them up?

Quoted 8 lines
Quoted 2 lines

Also, you can probably leave out the --trunk, etc., and just use --stdlayout.

Thanks. That's good information to have. Is there a way to just do a
straight import like in svnimport? Is svnimport still available somewhere or has it been completely superseded by git-svn?

I believe git-svn completely replaces svnimport. Check the git-svn manpage, which is quite extensive.

Dave.

#4 lore raw
Quoted 13 lines · David Symonds
Quoted 11 lines · Kenneth P. Turvey
Quoted 5 lines · David Symonds

git-svn creates a whole bunch of remote branches -- does "git branch -a" show them up?

Also, you can probably leave out the --trunk, etc., and just use --stdlayout.

Quoted 6 lines
Quoted 3 lines

Thanks. That's good information to have. Is there a way to just do a
straight import like in svnimport? Is svnimport still available somewhere or has it been completely superseded by git-svn?

I believe git-svn completely replaces svnimport. Check the git-svn manpage, which is quite extensive.

You can find git-svnimport in contrib/examples/.

git-svn has more features, and git-svnimport is no longer maintaned.

Signature · 3 lines
Jakub Narebski
Poland
ShadeHawk on #git