From: Jeff King <peff@peff.net>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2008, #05; Mon, 29)
Date: Tue, 30 Sep 2008 23:31:29 -0400 [thread overview]
Message-ID: <20081001033129.GD24513@coredump.intra.peff.net> (raw)
In-Reply-To: <20080930183759.GF21310@spearce.org>
On Tue, Sep 30, 2008 at 11:37:59AM -0700, Shawn O. Pearce wrote:
> * mw/sendemail (Mon Sep 29 12:41:06 2008 -0500) 8 commits
> - send-email: signedoffcc -> signedoffbycc, but handle both
> - Docs: send-email: Create logical groupings for man text
> - Docs: send-email: Remove unnecessary config variable description
> - Docs: send-email: --chain_reply_to -> --[no-]chain-reply-to
> - send-email: change --no-validate to boolean --[no-]validate
> - Docs: send-email: Man page option ordering
> - Docs: send-email usage text much sexier
> - Docs: send-email's usage text and man page mention same options
>
> This series has already gone through 3 iterations before I could
> start to carry it in-tree. I haven't had a chance to read it yet
> myself, so its sitting around in `pu` for futher review.
I think today's revision is probably ready for 'next'.
> * pb/commit-where (Mon Sep 8 01:05:41 2008 +0200) 1 commit
> + builtin-commit.c: show on which branch a commit was added
>
> [jc: Tentatively kicked back to "still cooking" status after
> Jeff voiced his annoyance. I personally do not like making this
> multi-line as Jeff suggested as an alternative (the message already
> is too verbose to my taste).]
>
> Agree with Junio. Hence its still here.
Definitely leave this out of master for now. I think there is some good
discussion going on, and I am hoping to get comments on Andreas' or my
patches.
-Peff
prev parent reply other threads:[~2008-10-01 3:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 18:37 What's cooking in git.git (Sep 2008, #05; Mon, 29) Shawn O. Pearce
2008-10-01 3:31 ` Jeff King [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=20081001033129.GD24513@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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).