From: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: "ryenus ◇" <ryenus@gmail.com>, git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] repack: find -> /usr/bin/find, as for cygwin
Date: Sat, 19 Mar 2011 16:50:24 +0100 [thread overview]
Message-ID: <4D84D0C0.7080808@lsrfire.ath.cx> (raw)
In-Reply-To: <AANLkTimPbz2s=Maafhqg-7wOk_TT4fFSh7AQ-3rWY0A3@mail.gmail.com>
Am 19.03.2011 13:18, schrieb Nguyen Thai Ngoc Duy:
> On Sat, Mar 19, 2011 at 7:08 PM, ryenus ◇<ryenus@gmail.com> wrote:
>> - for e in `cd "$PACKDIR"&& find . -type f -name '*.pack' \
>> + for e in `cd "$PACKDIR"&& /usr/bin/find . -type f
>
> I'd rather have something like in test-lib.sh (with conditions)
>
> find() {
> /usr/bin/find "$@"
> }
>
> Even better, rewrite this script to C.
That's a good idea, but it's a lot more involved than the original
patch.
Do we need to support pack files in subdirectories of $PACKDIR? If
not -- and I don't immediately see why, except that the current code
does with its find call -- then the following patch might be a quick
bandaid. Untested, please be careful.
René
git-repack.sh | 19 ++++++++++---------
1 files changed, 10 insertions(+), 9 deletions(-)
diff --git a/git-repack.sh b/git-repack.sh
index 624feec..4e49079 100755
--- a/git-repack.sh
+++ b/git-repack.sh
@@ -64,15 +64,16 @@ case ",$all_into_one," in
,t,)
args= existing=
if [ -d "$PACKDIR" ]; then
- for e in `cd "$PACKDIR" && find . -type f -name '*.pack' \
- | sed -e 's/^\.\///' -e 's/\.pack$//'`
- do
- if [ -e "$PACKDIR/$e.keep" ]; then
- : keep
- else
- existing="$existing $e"
- fi
- done
+ existing=$(
+ cd "$PACKDIR" &&
+ for e in *.pack
+ do
+ if test -f "$e" -a ! -e "${e%.pack}.keep"
+ then
+ echo "${e%.pack}"
+ fi
+ done
+ )
if test -n "$existing" -a -n "$unpack_unreachable" -a \
-n "$remove_redundant"
then
next prev parent reply other threads:[~2011-03-19 15:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 12:08 [PATCH] repack: find -> /usr/bin/find, as for cygwin ryenus ◇
2011-03-19 12:18 ` Nguyen Thai Ngoc Duy
2011-03-19 15:50 ` René Scharfe [this message]
2011-03-19 16:07 ` Nguyen Thai Ngoc Duy
2011-03-19 16:15 ` Nguyen Thai Ngoc Duy
2011-03-19 16:32 ` ryenus ◇
2011-03-19 16:43 ` ryenus ◇
2011-03-19 16:47 ` Nguyen Thai Ngoc Duy
2011-03-19 18:17 ` Junio C Hamano
2011-03-20 0:31 ` ryenus ◇
2011-03-20 0:35 ` ryenus ◇
2011-03-20 7:48 ` Matthieu Moy
2011-03-20 8:42 ` ryenus ◇
2011-03-21 9:36 ` Erik Faye-Lund
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=4D84D0C0.7080808@lsrfire.ath.cx \
--to=rene.scharfe@lsrfire.ath.cx \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
--cc=ryenus@gmail.com \
/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).