From: "Bert Wesarg" <bert.wesarg@googlemail.com>
To: "Petr Baudis" <pasky@suse.cz>
Cc: "Junio C Hamano" <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [TopGit PATCH] tg-create.sh: Support for multiple {to,cc,bcc} options
Date: Sat, 9 Aug 2008 12:49:35 +0200 [thread overview]
Message-ID: <36ca99e90808090349sf08fab5sa0a3194f8a68ead7@mail.gmail.com> (raw)
In-Reply-To: <20080809082701.GE32184@machine.or.cz>
On Sat, Aug 9, 2008 at 10:27, Petr Baudis <pasky@suse.cz> wrote:
>> >> +
>> >> + git config --get-all topgit.$1 2>/dev/null |
>> >> + sed -e "s/^/$prefix /g"
>> >> +}
> I still don't understand the stderr redirect, though.
Just precaution, I think. It seems unnecessary.
Bert
>
> Petr "Pasky" Baudis
>
prev parent reply other threads:[~2008-08-09 10:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 20:31 [TopGit PATCH] tg-create.sh: Support for multiple {to,cc,bcc} options Bert Wesarg
2008-08-09 0:33 ` Petr Baudis
2008-08-09 1:37 ` Junio C Hamano
2008-08-09 7:23 ` Bert Wesarg
2008-08-09 8:27 ` Petr Baudis
2008-08-09 10:49 ` Bert Wesarg [this message]
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=36ca99e90808090349sf08fab5sa0a3194f8a68ead7@mail.gmail.com \
--to=bert.wesarg@googlemail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pasky@suse.cz \
/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).