From: "Carlos Martín Nieto" <cmn@elego.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2011, #06; Wed, 21)
Date: Thu, 22 Sep 2011 10:37:06 +0200 [thread overview]
Message-ID: <1316680641.11165.2.camel@bee.lab.cmartin.tk> (raw)
In-Reply-To: <7vaa9xyxpf.fsf@alter.siamese.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 328 bytes --]
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?
cmn
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-09-22 8:37 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 [this message]
2011-09-22 9:14 ` Michael Schubert
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=1316680641.11165.2.camel@bee.lab.cmartin.tk \
--to=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 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).