Re: What's cooking (incremental)

From: Junio C Hamano <gitster@pobox.com>
Date: Apr 25, 2012, 15:17 UTC
Message-ID: <xmqq8vhjet85.fsf@junio.mtv.corp.google.com>
In-Reply-To: <87r4vcqiy8.fsf@thomas.inf.ethz.ch>

Thomas Rast <trast@student.ethz.ch> writes:

Show 19 quoted lines

> 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 :-)

Authors do not need to "scramble"; they are trusted to have done as good a job as they can possibly do before submitting anyway.

It is sufficient to just use the resulting Git in your daily work, but paying extra attention to notice if there is any behaviour that feels strange.