From: "Tadeusz Andrzej Kadłubowski" <yess@hell.org.pl>
To: git@vger.kernel.org
Subject: [PATCH v2 0/2] Documentation: filter-branch env-filter example
Date: Thu, 21 Feb 2013 21:21:38 +0100 [thread overview]
Message-ID: <512681D2.6020902@hell.org.pl> (raw)
Hello,
Indeed the use case proposed by Junio C. Hamano is more realistic than mine.
I also included a minor clarification of how identity environment variables are
used to cover the edge case raised by Jeff King. As far as the need to export
those variables goes, I saw the wrong behavior on Solaris.
--
Tadeusz Andrzej Kadłubowski
reply other threads:[~2013-02-21 20:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=512681D2.6020902@hell.org.pl \
--to=yess@hell.org.pl \
--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.
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).