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

Re: Problem with case-insensitive file cleanup

From
James Youngman <jay@gnu.org>
Date
May 3, 2007, 21:40 UTC
Message-ID
<c5df85930705031440n3b3025dalf566944da6069262@mail.gmail.com>
In-Reply-To
<87odl2dnbk.fsf@rho.meyering.net>
On 5/3/07, Jim Meyering <jim@meyering.net> wrote:
Show 17 quoted lines
> > Earlier this week, I reported a problem when two case-insensitive files
> > were created, which is a no-no for checkouts on Mac HFS+ or Windows-based
> > platforms [1].  The problem was quickly corrected in CVS (note that
> > _Exit.texi now lives in the attic [2]).  But somehow the git repository
> > still thinks that _Exit.texi belongs to the current tree [3], which leads
> > to this confusing state on a case-insensitive clone:
>
> I've just removed that file manually and pushed the result.
> I suppose that happened because something went wrong with the
> automated git-cvsimport run.
>
> The current procedure is to rsync the CVS repository,
> use that via git-cvsimport into an existing .git repository,
> and then to push the result to savannah.
>
> Obviously, before we do the final CVS-to-GIT switch, I'll rerun
> git-cvsimport from scratch, rather relying on the incrementally-built-up one.

I have had related problems using git-cvsimport with the GNU findutils source base and was eventually reduced to deleting the git repository into which I was pushing the git-cvsimport result. I had added a directory to the CVS repository (findutils/build-aux) and it was not showing up in the target git repository (i.e. the local directory I was specifying as the argument of -C).

Fortunately since git is content-oriented (has foo-nature, whatever, insert hand-wave here), once I have repeated the entire cvsimport operation, pushing the regenerated result to the public git repository only required an incremental amount of work (bandwdth).

But suffice to say, I do not believe that git-cvsimport is very reliable. People more familiar with git than I point the finger at cvsps, but to be honest I don't know enough about either program to arbitrate.

People also pointed me at alternatives to git-cvsimport but they all
had one or more of these drawbacks:
1. No support for incremental import
2. No support for tags
3. No support for branches
James.
Previous: Jim Meyering
Message 4 of 4 in “Problem with case-insensitive file cleanup”
  1. Eric BlakeMay 3, 2007
  2. Alex RiesenMay 3, 2007
  3. Jim MeyeringMay 3, 2007
  4. James YoungmanMay 3, 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.