From: Michael Schubert <mschub@elegosoft.com>
To: "Carlos Martín Nieto" <cmn@elego.de>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2011, #06; Wed, 21)
Date: Thu, 22 Sep 2011 11:14:20 +0200 [thread overview]
Message-ID: <4E7AFC6C.7080603@elegosoft.com> (raw)
In-Reply-To: <1316680641.11165.2.camel@bee.lab.cmartin.tk>
On 09/22/2011 10:37 AM, Carlos Martín Nieto wrote:
> On Wed, 2011-09-21 at 22:04 -0700, Junio C Hamano wrote:
>> * cn/eradicate-working-copy (2011-09-21) 2 commits
>> - patch-id.c: use strbuf instead of a fixed buffer
>> - Remove 'working copy' from the documentation and C code
>
> It looks like that first commit sneaked in there. Shouldn't that be its
> own topic?
It's in pu twice:
On 09/22/2011 07:04 AM, Junio C Hamano wrote:
> * cn/eradicate-working-copy (2011-09-21) 2 commits
> - patch-id.c: use strbuf instead of a fixed buffer
> - Remove 'working copy' from the documentation and C code
> * ms/patch-id-with-overlong-line (2011-09-21) 1 commit
> - patch-id.c: use strbuf instead of a fixed buffer
64128da and a6c5c60
There's also a minor typo in the last sentence of the commit message.
Should I resend?
next prev parent reply other threads:[~2011-09-22 9:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 5:04 What's cooking in git.git (Sep 2011, #06; Wed, 21) Junio C Hamano
2011-09-22 8:37 ` Carlos Martín Nieto
2011-09-22 9:14 ` Michael Schubert [this message]
2011-09-22 16:39 ` Junio C Hamano
2011-09-22 23:01 ` Jakub Narebski
2011-09-22 23:12 ` Junio C Hamano
2011-09-22 23:33 ` Jakub Narebski
2011-09-22 23:45 ` Junio C Hamano
2011-09-23 11:00 ` [PATCH] fix push --quiet: add 'quiet' capability to receive-pack Clemens Buchacher
2011-09-23 11:55 ` [PATCH] use -h for synopsis and --help for manpage consistently Clemens Buchacher
2011-09-23 14:44 ` What's cooking in git.git (Sep 2011, #06; Wed, 21) Scott Chacon
2011-09-23 18:00 ` Junio C Hamano
2011-09-23 19:29 ` Junio C Hamano
2011-09-26 14:03 ` Scott Chacon
2011-09-26 18:52 ` Junio C Hamano
2011-09-27 2:08 ` Jay Soffian
[not found] ` <20111003182136.GA6136@ecki.lan>
2011-10-03 22:03 ` [PATCH] use -h for synopsis and --help for manpage consistently Junio C Hamano
2011-10-05 6:33 ` Clemens Buchacher
2011-10-05 6:31 ` [PATCH] fix push --quiet: add 'quiet' capability to receive-pack Clemens Buchacher
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=4E7AFC6C.7080603@elegosoft.com \
--to=mschub@elegosoft.com \
--cc=cmn@elego.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.