From: Thomas Rast <trast@student.ethz.ch>
To: Junio C Hamano <gitster@pobox.com>
Cc: <git@vger.kernel.org>
Subject: Re: What's cooking (incremental)
Date: Wed, 25 Apr 2012 11:06:23 +0200 [thread overview]
Message-ID: <87r4vcqiy8.fsf@thomas.inf.ethz.ch> (raw)
In-Reply-To: <xmqqobqgeex1.fsf@junio.mtv.corp.google.com> (Junio C. Hamano's message of "Tue, 24 Apr 2012 19:14:18 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> I've merged the following topics to 'next':
>
> * tr/xdiff-fast-hash (2012-04-09) 1 commit
> * cb/daemon-test-race-fix (2012-04-19) 1 commit
> * ld/git-p4-tags-and-labels (2012-04-24) 6 commits
> * nh/empty-rebase (2012-04-24) 4 commits
> * pw/t5800-import-race-fix (2012-04-24) 1 commit
> * nd/i18n (2012-04-24) 10 commits
>
> Some of them are scary and somewhat iffy (I had to apply a last minute
> fix and rebuild 'next' to one of them), so please test them throughly to
> help us avoid breakages on 'master'.
Umm, which one?
As the author of the first, I'm kind of curious whether I need to
scramble to fix (or at least further test) something :-)
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2012-04-25 9:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 22:04 What's cooking in git.git (Apr 2012, #09; Mon, 23) Junio C Hamano
2012-04-24 9:14 ` Nelson Benitez Leon
2012-04-24 18:57 ` Junio C Hamano
2012-04-26 13:16 ` [PATCH] Try an uppercase version of $prot_proxy env var Nelson Benitez Leon
2012-04-26 13:08 ` Jeff King
2012-04-26 15:18 ` Junio C Hamano
2012-04-26 16:29 ` Nelson Benitez Leon
2012-04-27 8:12 ` Jeff King
2012-04-27 15:03 ` Junio C Hamano
2012-04-26 14:04 ` Junio C Hamano
2012-04-25 2:14 ` What's cooking (incremental) Junio C Hamano
2012-04-25 9:06 ` Thomas Rast [this message]
2012-04-25 15:17 ` 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=87r4vcqiy8.fsf@thomas.inf.ethz.ch \
--to=trast@student.ethz.ch \
--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).