Re: cvs2git master branch empty - can't find trunk anywhere

Michael Haggerty <[email protected]> Tue, 08 Apr 2014 05:51:31 +0200
Newsgroups gmane.comp.version-control.subversion.cvs2svn.user
Message-ID <[email protected]>
On 04/08/2014 01:37 AM, Mark Hedges wrote:
> Hi.  I=E2=80=99m trying to use cvs2git to convert a CVS repository into a
> non-bare git repository.
>=20
> It sort of works =E2=80=93 I end up seeing a bunch of branches.  Except t=
here is
> no branch called TAG.FIXUP like the documentation refers to.=20
> (http://cvs2svn.tigris.org/cvs2git.html)  And the master branch ends up
> empty.
>=20
> I created a new file in trunk in the CVS repo and ran again, then
> exhaustively searched every resulting git branch for the file.  It=E2=80=
=99s not
> there.
>=20
> Would it be better to convert to a bare repo?  If so, how do I then
> merge the contents of that bare repo into an existing remote repo?
>=20
> Thanks for any insight people might be able to share.

You haven't really provided enough information to permit us to help you.

* The TAG.FIXUP branch is of secondary importance.

* The master branch should not end up empty unless all files were
deleted on CVS HEAD and you developed only on branches.  Are you sure
the branch was empty, or was it just that the working copy was empty
because you forgot the step

    git checkout master

?  Try running "git show-ref" in the repository directory and see if it
lists "refs/heads/master".  If it does, try commands like

    git ls-tree refs/heads/master
    git log refs/heads/master

The main reason to convert to a bare repo would be that you plan to put
the Git repository on a server somewhere (repos on servers should
usually be bare).  If the repo is just for your own private use then it
is OK to convert to a non-bare repo.

Michael

--=20
Michael Haggerty
[email protected]
http://softwareswirl.blogspot.com/

------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=3D1670&dsMessageId=3D=
3076048

To unsubscribe from this discussion, e-mail: [[email protected]=
ris.org].