From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Johannes Sixt <j.sixt@viscovery.net>,
Yaroslav Halchenko <debian@onerussian.com>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH v4 1/5] fmt-merge-msg: Make the number of log entries in commit message configurable
Date: Sun, 22 Aug 2010 12:23:34 +0530 [thread overview]
Message-ID: <20100822065331.GA15561@kytes> (raw)
In-Reply-To: <20100822033330.GA12380@belmont.cs.uchicago.edu>
Hi Jonathan,
Jonathan Nieder writes:
> Hi again,
>
> Thanks for working on this.
>
> Ramkumar Ramachandra wrote:
>
> > Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com>
> > Reported-by: Yaroslav Halchenko <debian <at> onerussian.com>
>
> Looks like some of the @ signs have been corrupted somehow.
My stupidity- I copied the additional lines off the GMane interface.
[...]
> FWIW if I were writing it, I would make changes in something like this
> order:
>
> - Change fmt_merge_msg API to
>
> int fmt_merge_msg(struct strbuf *in, struct strbuf *out,
> int shortlog_len);
>
> where shortlog_len is 0 for no shortlog, 20 for a shortlog
> with 20 items. Update all callers (the changed function
> signature makes it easy to find them).
>
> - Update merge --log and fmt-merge-msg --log options to take
> an optional "size of shortlog" argument.
>
> - update [merge] log configuration to accept an integer
> "size of shortlog" value.
>
> The first step might look like this.
[...]
Thanks for being so patient! It looks like there's no end to my
mistakes :p
I'll rewrite this and try to follow the guidelines you've outlined in
future- hopefully, I'll become more experienced someday :)
-- Ram
next prev parent reply other threads:[~2010-08-22 7:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-21 9:58 [PATCH v4 0/5] fmt-merge-msg improvements Ramkumar Ramachandra
2010-08-21 9:58 ` [PATCH v4 1/5] fmt-merge-msg: Make the number of log entries in commit message configurable Ramkumar Ramachandra
2010-08-22 3:33 ` Jonathan Nieder
2010-08-22 5:05 ` Junio C Hamano
2010-08-22 6:53 ` Ramkumar Ramachandra [this message]
2010-08-21 9:58 ` [PATCH v4 2/5] fmt-merge-msg: Update command line options to sync with config options Ramkumar Ramachandra
2010-08-21 9:58 ` [PATCH v4 3/5] fmt-merge-msg: Update fmt-merge-msg and merge-config documentation Ramkumar Ramachandra
2010-08-21 9:58 ` [PATCH v4 4/5] fmt-merge-msg: Remove deprecated --summary option Ramkumar Ramachandra
2010-08-21 9:58 ` [PATCH v4 5/5] parse-options: clarify PARSE_OPT_NOARG description 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100822065331.GA15561@kytes \
--to=artagnon@gmail.com \
--cc=debian@onerussian.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).