public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Michael Haggerty <mhagger@alum•mit.edu>
To: supadhyay <supadhyay@imany•com>
Cc: git@vger•kernel.org
Subject: Re: Tags/Branches missing in GIT
Date: Wed, 18 Apr 2012 09:34:12 +0200	[thread overview]
Message-ID: <4F8E6E74.7020403@alum.mit.edu> (raw)
In-Reply-To: <1334728490216-7475869.post@n2.nabble.com>

On 04/18/2012 07:54 AM, supadhyay wrote:
> I have migrated our version control from CVS to Git (with the help of this
> link  http://cvs2svn.tigris.org/cvs2git.html) and from git I do clone to
> gitolite on the same server.
>
> Now when end user verify their code in GIT (using Tortoisegit/Egit) they
> found differences in number of tags and brances. Some of CVS tags/brances
> are not exists in GIT and some of the new tags created by GIT which is not
> in CVS.
>
>
> Can any one please update me this is known issue or not and how to resolve
> this ?

Questions about cvs2svn/cvs2git belong on the cvs2svn mailing list [1] 
(as I have told you twice before).

It is of course the mission of cvs2git to convert all CVS history 
including all branches and tags.  So if you think you have found a 
problem, you need to provide more detail about how you ran cvs2git and 
what makes you think that the results are incorrect.  Please see the 
cvs2svn FAQ [2] for information about reporting suspected bugs in 
cvs2svn/cvs2git.

[1] users@cvs2svn•tigris.org
[2] http://cvs2svn.tigris.org/faq.html#gettinghelp

-- 
Michael Haggerty
mhagger@alum•mit.edu
http://softwareswirl.blogspot.com/

  reply	other threads:[~2012-04-18  7:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-18  5:54 Tags/Branches missing in GIT supadhyay
2012-04-18  7:34 ` Michael Haggerty [this message]
2012-04-18  8:27   ` supadhyay
2012-04-18 20:43     ` Michael Haggerty

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=4F8E6E74.7020403@alum.mit.edu \
    --to=mhagger@alum$(echo .)mit.edu \
    --cc=git@vger$(echo .)kernel.org \
    --cc=supadhyay@imany$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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