git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Bryan Larsen <bryanlarsen@yahoo.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
	bryan.larsen@gmail.com, pasky@suse.cz, git@vger.kernel.org
Subject: Re: [PATCH 3/6] git-gnu-progs-Makefile: git Makefile update
Date: Mon, 11 Jul 2005 14:59:58 -0700	[thread overview]
Message-ID: <7vmzotovfl.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <42D2E47E.8060602@yahoo.com> (Bryan Larsen's message of "Mon, 11 Jul 2005 17:28:30 -0400")

Bryan Larsen <bryanlarsen@yahoo.com> writes:

> For the record, "${XARGS} -0r" may be uglier than "xargs -0r", but
> replacing it with several lines of shell magic is a loss.

OK, OK, the one I suggested for xargs was _U_G_L_Y_.

The one Linus suggested looks to me the cleanest.  That is, to
give an extra parameter upfront to the command run by xargs.  My
favorite trick is like this:

  git-fsck-cache --cache --unreachable "$@" |
  sed -ne '/unreachable /{
      s/unreachable [^ ][^ ]* //
      s|\(..\)|\1/|p
  }' | {
          cd "$GIT_OBJECT_DIRECTORY" || exit
-         xargs -r $dryrun rm -f
+         xargs $dryrun rm -f ""
  }

Dry-run would say: 

    rm -f  00/012345...
    rm -f  01/234567...

without visual distraction of having printable phoney names, or
just (with an invisible trailing space):

    rm -f  

During a real run, "rm -f" would not complain "cannot remove `':
Is a directory", either.

  reply	other threads:[~2005-07-11 22:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-11 10:14 [PATCH 0/6] parameterize gnu tool names; add Portfile for OS X darwinports Bryan Larsen
2005-07-11 10:14 ` [PATCH 1/6] git-gnu-progs: parameterize git Bryan Larsen
2005-07-11 10:14 ` [PATCH 2/6] config-sh: find and verify utils Bryan Larsen
2005-07-11 10:15 ` [PATCH 3/6] git-gnu-progs-Makefile: git Makefile update Bryan Larsen
2005-07-11 19:02   ` Junio C Hamano
2005-07-11 19:10     ` Linus Torvalds
2005-07-11 19:42       ` Bryan Larsen
2005-07-11 20:00         ` Linus Torvalds
2005-07-12  9:03           ` Matthias Urlichs
2005-07-11 20:14         ` Junio C Hamano
2005-07-11 20:22           ` Bryan Larsen
2005-07-11 20:30           ` Junio C Hamano
2005-07-11 21:28             ` Bryan Larsen
2005-07-11 21:59               ` Junio C Hamano [this message]
2005-07-11 19:21     ` Bryan Larsen
2005-07-11 10:15 ` [PATCH 4/6] cogito-gnu-progs: parameterize cogito Bryan Larsen
2005-07-11 10:15 ` [PATCH 5/6] cogito-gnu-progs-Makefile: cogito Makefile update Bryan Larsen
2005-07-11 10:15 ` [PATCH 6/6] darwinports-Portfile: Portfile for cogito Bryan Larsen

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=7vmzotovfl.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=bryan.larsen@gmail.com \
    --cc=bryanlarsen@yahoo.com \
    --cc=git@vger.kernel.org \
    --cc=pasky@suse.cz \
    --cc=torvalds@osdl.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).