From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH 0/3] commit-tree updates
Date: Wed, 9 Nov 2011 13:01:32 -0800 [thread overview]
Message-ID: <1320872495-7545-1-git-send-email-gitster@pobox.com> (raw)
Here are a handful of patches to the lowest level plumbing commit-tree to
teach it to record extended headers. With this series, scripted Porcelain
like rebase--am can propagate the "mergetag" header while rebasing.
Junio C Hamano (3):
commit-tree: update the command line parsing
commit-tree: teach -m/-F options to read logs from elsewhere
commit-tree: teach -x <extra>
Documentation/git-commit-tree.txt | 17 ++++++-
builtin/commit-tree.c | 92 ++++++++++++++++++++++++++++++-------
2 files changed, 89 insertions(+), 20 deletions(-)
--
1.7.8.rc1.82.gde0f9
next reply other threads:[~2011-11-09 21:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 21:01 Junio C Hamano [this message]
2011-11-09 21:01 ` [PATCH 1/3] commit-tree: update the command line parsing Junio C Hamano
2011-11-09 21:01 ` [PATCH 2/3] commit-tree: teach -m/-F options to read logs from elsewhere Junio C Hamano
2011-11-09 21:01 ` [PATCH 3/3] commit-tree: teach -x <extra> Junio C Hamano
2011-11-09 22:19 ` Brad King
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=1320872495-7545-1-git-send-email-gitster@pobox.com \
--to=gitster@pobox.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).