From: Paolo Bonzini <paolo.bonzini@lu.unisi.ch>
To: Junio C Hamano <junkio@cox.net>
Cc: bonzini@gnu.org, git@vger.kernel.org
Subject: Re: [PATCH] git-fetch, git-parse-remote: Cleanup implementation of '.'
Date: Fri, 16 Mar 2007 10:38:03 +0100 [thread overview]
Message-ID: <45FA657B.1010709@lu.unisi.ch> (raw)
In-Reply-To: <7vps79v8ik.fsf@assigned-by-dhcp.cox.net>
> I may not be really thinking straight tonight (no I am not
> drunk, but just a tad sick), but I wonder if this is sufficient?
>
> $(git-for-each-ref --format='%(refname):')
>
> Shorter and one less process and pipe.
It is. Would you take care of that?
Paolo
next prev parent reply other threads:[~2007-03-16 9:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-15 8:23 [PATCH, fixed] git-fetch, git-branch: Support local --track via a special remote `.' Paolo Bonzini
2007-03-16 0:21 ` Junio C Hamano
2007-03-16 8:38 ` [PATCH] git-fetch, git-parse-remote: Cleanup implementation of '.' Paolo Bonzini
2007-03-16 9:32 ` Junio C Hamano
2007-03-16 9:38 ` Paolo Bonzini [this message]
2007-03-16 10:00 ` Junio C Hamano
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=45FA657B.1010709@lu.unisi.ch \
--to=paolo.bonzini@lu.unisi.ch \
--cc=bonzini@gnu.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).