From: Jeff King <peff@peff.net>
To: Dun Peal <dunpealer@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Efficiently detecting paths that differ from each other only in case
Date: Fri, 8 Oct 2010 09:50:34 -0400 [thread overview]
Message-ID: <20101008135034.GC5163@sigill.intra.peff.net> (raw)
In-Reply-To: <AANLkTimGAbosbD0pprROu_g-UW38faotYA2dTxj9scsP@mail.gmail.com>
On Fri, Oct 08, 2010 at 01:13:07AM -0500, Dun Peal wrote:
> Etc. I know how to do it by listing paths with ls-files, but my repo
> contains many thousands of files, so I was wondering if there was a
> more efficient way than for every commit:
>
> 1. Get a list of all paths in the repo from ls-files.
> 2. Lowercase all paths.
> 3. Check for repeats.
You can do:
git ls-files | tr A-Z a-z | sort | uniq -d
but:
1. It will print only the lowercased version, not all versions.
2. It doesn't handle filenames with embedded newlines.
You could fix both with something like:
git ls-files -z | perl -0ne '
push @{$h{lc($_)}}, $_;
END {
print join("\n", @{$h{$_}}) . "\n\n"
foreach grep { @{$h{$_}} > 1 } keys(%h);
}
'
-Peff
next prev parent reply other threads:[~2010-10-08 13:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 6:13 Efficiently detecting paths that differ from each other only in case Dun Peal
2010-10-08 13:50 ` Jeff King [this message]
2010-10-08 19:44 ` Dun Peal
2010-10-08 19:51 ` Jeff King
2010-10-08 19:57 ` Dun Peal
2010-10-08 20:06 ` Jeff King
2010-10-08 22:57 ` Dun Peal
2010-10-09 8:47 ` Jakub Narebski
2010-10-09 22:00 ` Dun Peal
2010-10-09 22:31 ` Jakub Narebski
2010-10-11 3:07 ` Jeff King
2010-10-16 22:37 ` Dun Peal
2010-10-17 4:25 ` Jeff King
2010-10-08 19:56 ` Jonathan Nieder
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101008135034.GC5163@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=dunpealer@gmail.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).