git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Eric Blake" <ebb9@byu.net>
Cc: git@vger.kernel.org, bug-gnulib <bug-gnulib@gnu.org>
Subject: Re: Problem with case-insensitive file cleanup
Date: Thu, 3 May 2007 15:32:41 +0200	[thread overview]
Message-ID: <81b0412b0705030632k5056ffc9sada117111598006d@mail.gmail.com> (raw)
In-Reply-To: <4639DA65.3030401@byu.net>

On 5/3/07, Eric Blake <ebb9@byu.net> wrote:
> Right now, the gnulib repository is mastered in CVS but mirrored by git (I
> am still awaiting the day that Jim decides that his hooks are adequate
> enough that git can be the master and CVS provided by git-cvsserver).
> 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], ...

cvs-to-git conversion seem to be buggy in this respect

> What needs to happen to get rid of the _Exit.texi listing in the git
> repository, so that case insensitive file systems can clone the gnulib.git
> repository?

git update-index --force-remove _Exit.texi
git commit -m 'Really removed _Exit.texi'

  reply	other threads:[~2007-05-03 13:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-03 12:49 Problem with case-insensitive file cleanup Eric Blake
2007-05-03 13:32 ` Alex Riesen [this message]
2007-05-03 13:54 ` Jim Meyering
2007-05-03 21:40   ` James Youngman

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=81b0412b0705030632k5056ffc9sada117111598006d@mail.gmail.com \
    --to=raa.lkml@gmail.com \
    --cc=bug-gnulib@gnu.org \
    --cc=ebb9@byu.net \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).