git-svn and logging.. new to git

> 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

> 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.

> On Wed, 05 Mar 2008 23:01:34 +1100, David Symonds wrote:
>
>
>  > 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?

> On Thu, Mar 6, 2008 at 3:03 AM, Kenneth P. Turvey
> <kt-usenet@squeakydolphin.com> wrote:
> > On Wed, 05 Mar 2008 23:01:34 +1100, David Symonds wrote:
> >
> >
> > > 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?
> 
> I believe git-svn completely replaces svnimport. Check the git-svn
> manpage, which is quite extensive.