git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Tags/Branches missing in GIT

From
Michael Haggerty <mhagger@alum.mit.edu>
Date
Apr 18, 2012, 07:34 UTC
Message-ID
<4F8E6E74.7020403@alum.mit.edu>
In-Reply-To
<1334728490216-7475869.post@n2.nabble.com>
On 04/18/2012 07:54 AM, supadhyay wrote:
Show 12 quoted lines
> 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/
Previous: supadhyayNext: supadhyay
Message 2 of 4 in “Tags/Branches missing in GIT”
  1. supadhyayApr 18, 2012
  2. Michael HaggertyApr 18, 2012
  3. supadhyayApr 18, 2012
  4. Michael HaggertyApr 18, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.