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

Re: problem after cvsimport

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 26, 2007, 03:07 UTC
Message-ID
<7vlkd3c16z.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<46A7FD99.9000305@tplogic.com>
Bert Douglas <bertd@tplogic.com> writes:
Show 27 quoted lines
> I am new to git, so probably doing something wrong.
> Hope somebody can enlighten me.
> Here is what happened so far.
>
> Followed instructions here:
> http://www.kernel.org/pub/software/scm/git/docs/cvs-migration.html
>
> Did command like this:
>
> $ git cvsimport -C <destination> <module>
>
> This was done from top level of existing cvs working directory.
> Destination was new empty directory, outside the cvs tree.
>
> It worked for several hours and seemed to complete ok.
> I can look at history in destination git directory with gitk and git log.
> All the stuff in ".git" looks normal, as far as I can tell.
>
> But I have no files in the working directory.
> When I do command:
> $git checkout master
>
> I get a bunch of lines to console with "D" in front.
> Btw, what does that mean?  Nothing about it in "man git-checkout" or elsewhere that I can find.
> Then it says -- Already on branch "master"
>
> But working directory is still empty.

Have you tried "git checkout -f" after that? With recent enough git, "git cvsimport -C <destination> <module>" from the top level of existing cvs working directory, with nonexistent destination directory (that is, you let "git cvsimport -C" to create that destination directory) would run "git checkout -f" for you.

Previous: Bert DouglasNext: Bert Douglas
Message 2 of 5 in “problem after cvsimport”
  1. Bert DouglasJul 26, 2007
  2. Junio C HamanoJul 26, 2007
  3. Bert DouglasJul 26, 2007
  4. Junio C HamanoJul 26, 2007
  5. Bert DouglasJul 26, 2007

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.