From: "Chris Riddoch" <riddochc@gmail.com>
To: git@vger.kernel.org
Subject: The patch documenting --pretty options (oops)
Date: Fri, 17 Nov 2006 23:28:47 -0700 [thread overview]
Message-ID: <6efbd9b70611172228p69ecb3e6mfd1c60d349968cce@mail.gmail.com> (raw)
Hi, folks.
I'm terribly sorry about the repost of my old patch. I fixed it,
adding more information about the rest of the output formats and the
'Merge: ' line, but then accidentally reposted the original one. I
hope this new version addresses your original concerns with my patch,
Junio.
--
epistemological humility
reply other threads:[~2006-11-18 6:28 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=6efbd9b70611172228p69ecb3e6mfd1c60d349968cce@mail.gmail.com \
--to=riddochc@gmail.com \
--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).