From: Michael <kensington@astralcloak.net>
To: git@vger.kernel.org
Subject: Build oddities
Date: Sun, 5 Feb 2012 06:34:49 +0000 (UTC) [thread overview]
Message-ID: <loom.20120205T072940-523@post.gmane.org> (raw)
Hi there,
I ran into a build oddity with git today - the environment variable $X is
appended to most binaries. At the time, I had X=last, so I ended up with
gitlast, git-peek-remotelast etc.
Does anyone know why this behaviour exists, and if it is still desired?
Best regards,
Michael
next reply other threads:[~2012-02-05 6:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-05 6:34 Michael [this message]
2012-02-05 6:46 ` Build oddities Nguyen Thai Ngoc Duy
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=loom.20120205T072940-523@post.gmane.org \
--to=kensington@astralcloak.net \
--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