Re: Fwd: "show-ignore" problem after svn-git clone

[Jamie Jackson <jamiejaxon@gmail.com>]

By the way, my goal is to pull in trunk (only) at first, and possibly
pull in certain branches (later) on an as-needed basis. I'll need to
sync the Git repo with SVN for a while, until we permanently switch to
Git (and put SVN in read-only).
On Wed, Nov 21, 2018 at 10:38 AM Jamie Jackson <jamiejaxon@gmail.com> wrote:
>
> ICF2008571:eclipse-workspace jjackson$ git svn clone \
> >   -r 95115:HEAD https://mydomain.com/svn/HUD/onecpd \
> >   -T trunk \
> >   --no-metadata \
> >   -A ~/eclipse-workspace/scraps/git_migration/users.txt \
> >   hudx-git-migration
> ICF2008571:eclipse-workspace jjackson$ cd hudx-git-migration/
>
> ICF2008571:hudx-git-migration jjackson$ git svn show-ignore
> fatal: bad revision 'HEAD'
> rev-list --first-parent --pretty=medium HEAD --: command returned error: 128
>
> ICF2008571:hudx-git-migration jjackson$ git svn show-ignore --id=origin/trunk
> fatal: bad revision 'HEAD'
> rev-list --first-parent --pretty=medium HEAD --: command returned error: 128
>
> ICF2008571:hudx-git-migration jjackson$ cat .git/config
> [core]
> repositoryformatversion = 0
> filemode = true
> bare = false
> logallrefupdates = true
> ignorecase = true
> precomposeunicode = true
> [svn-remote "svn"]
> noMetadata = 1
> url = https://mydomain.com/svn/HUD
> fetch = onecpd/trunk:refs/remotes/origin/trunk
> [svn]
> authorsfile = /Users/jjackson/eclipse-workspace/scraps/git_migration/users.txt
>
> On Wed, Nov 21, 2018 at 9:44 AM Konstantin Khomoutov <kostix@bswap.ru> wrote:
> >
> > On Wed, Nov 21, 2018 at 08:37:03AM -0500, Jamie Jackson wrote:
> >
> > > I'm brand new to svn-git and I'm having a problem right out of the
> > > gate. I suspect I need a different ID, but I have no clue how to get
> > > it.
> > >
> > > Here's the failed attempt:
> > > https://gist.github.com/jamiejackson/57e90302802f4990b36dfe28c3c71d13
> >
> > Please post the content supposedly available at that link in your mail
> > message, inline.  Otherwise it's impossibly to sensibly comment on it.
> >