From: Paul Mackerras <paulus@samba.org>
To: Brandon Casey <casey@nrlssc.navy.mil>
Cc: git@vger.kernel.org
Subject: Re: [patch] prefer "git COMMAND" over "git-COMMAND" in gitk
Date: Wed, 21 Mar 2007 22:04:45 +1100 [thread overview]
Message-ID: <17921.4429.408665.577258@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0703191746150.5525@torch.nrlssc.navy.mil>
Brandon Casey writes:
> Preferring git _space_ COMMAND over git _dash_ COMMAND allows the
> user to have only git and gitk in their path. e.g. when git and gitk
> are symbolic links in a personal bin directory to the real git and gitk.
Thanks for the patch. It was whitespace-damaged but I fixed it up
(this once) and applied it. Also, if you send any larger patches in
future I'd like a Signed-off-by line with them (this one was trivial
enough that I applied it without).
Paul.
prev parent reply other threads:[~2007-03-21 11:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 23:00 [patch] prefer "git COMMAND" over "git-COMMAND" in gitk Brandon Casey
2007-03-21 11:04 ` Paul Mackerras [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=17921.4429.408665.577258@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=casey@nrlssc.navy.mil \
--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).