From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Cc: Johannes Sixt <j.sixt@viscovery.net>,
Jonathan Nieder <jrnieder@gmail.com>,
Yaroslav Halchenko <debian@onerussian.com>
Subject: [PATCH 0/4] fmt-merge-msg improvements
Date: Fri, 20 Aug 2010 17:53:57 +0530 [thread overview]
Message-ID: <1282307041-19681-1-git-send-email-artagnon@gmail.com> (raw)
Hi,
The first three parts make `merge.log` and `--log` an integer. While
at it, drop the deprecated `--summary` option: blame tells me that it
was marked deprecated back in 2008. The series is based on pu for no
good reason.
Thanks to Johannes and Jonathan for their inputs.
-- Ram
Ramkumar Ramachandra (4):
fmt-merge-msg: Make the number of log entries in commit message
configurable
fmt-merge-msg: Update command line options to sync with config
options
fmt-merge-msg: Update fmt-merge-msg and merge-config documentation
fmt-merge-msg: Remove deprecated --summary option
Documentation/git-fmt-merge-msg.txt | 28 +++++++----------------
Documentation/merge-config.txt | 8 +++++-
builtin/fmt-merge-msg.c | 41 ++++++++++++++++------------------
3 files changed, 34 insertions(+), 43 deletions(-)
next reply other threads:[~2010-08-20 12:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-20 12:23 Ramkumar Ramachandra [this message]
2010-08-20 12:23 ` [PATCH 1/4] fmt-merge-msg: Make the number of log entries in commit message configurable Ramkumar Ramachandra
2010-08-20 12:23 ` [PATCH 2/4] fmt-merge-msg: Update command line options to sync with config options Ramkumar Ramachandra
2010-08-20 12:24 ` [PATCH 3/4] fmt-merge-msg: Update fmt-merge-msg and merge-config documentation Ramkumar Ramachandra
2010-08-20 12:39 ` Ramkumar Ramachandra
2010-08-20 12:44 ` Johannes Sixt
2010-08-20 13:12 ` Ramkumar Ramachandra
2010-08-20 14:10 ` Jonathan Nieder
2010-08-20 15:00 ` Ramkumar Ramachandra
2010-08-20 12:24 ` [PATCH 4/4] fmt-merge-msg: Remove deprecated --summary option Ramkumar Ramachandra
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=1282307041-19681-1-git-send-email-artagnon@gmail.com \
--to=artagnon@gmail.com \
--cc=debian@onerussian.com \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--cc=jrnieder@gmail.com \
/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).