From: Sverre Rabbelier <srabbelier@gmail.com>
To: Johan Herland <johan@herland.net>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: What's cooking in git.git (Jan 2010, #06; Wed, 20)
Date: Thu, 21 Jan 2010 03:04:12 +0100 [thread overview]
Message-ID: <fabb9a1e1001201804j4d847569p6c1a9921464e6cd@mail.gmail.com> (raw)
In-Reply-To: <201001210240.10522.johan@herland.net>
Heya,
On Thu, Jan 21, 2010 at 02:40, Johan Herland <johan@herland.net> wrote:
> You misremembered. Only the three first were merged to 'next'. Junio was
> about to merge the rest, but I asked him to hold until I had produced the
> current iteration.
Ah, I should have checked the last what's cooking; or looked at that
inter-diff thingy Junio's contemplating on doing :)
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2010-01-21 2:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 0:52 What's cooking in git.git (Jan 2010, #06; Wed, 20) Junio C Hamano
2010-01-21 1:06 ` Sverre Rabbelier
2010-01-21 1:40 ` Johan Herland
2010-01-21 2:04 ` Sverre Rabbelier [this message]
2010-01-21 4:06 ` Junio C Hamano
2010-01-21 9:18 ` Johan Herland
2010-01-21 17:52 ` Junio C Hamano
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=fabb9a1e1001201804j4d847569p6c1a9921464e6cd@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johan@herland.net \
/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).