From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2015, #05; Mon, 22)
Date: Wed, 24 Jun 2015 09:16:02 +0200 [thread overview]
Message-ID: <ad998ee2d8387401a3ceb6a7df7457ab@www.dscho.org> (raw)
In-Reply-To: <xmqq616ecfuq.fsf@gitster.dls.corp.google.com>
Hi Junio,
On 2015-06-23 22:46, Junio C Hamano wrote:
> Johannes Schindelin <johannes.schindelin@gmx.de> writes:
>
>> On 2015-06-23 00:49, Junio C Hamano wrote:
>>
>>> * js/rebase-i-clean-up-upon-continue-to-skip (2015-06-18) 3 commits
>>> - rebase -i: do not leave a CHERRY_PICK_HEAD file behind
>>> - SQUASH: test_must_fail is a shell function
>>> - t3404: demonstrate CHERRY_PICK_HEAD bug
>>>
>>> Abandoning an already applied change in "git rebase -i" with
>>> "--continue" left CHERRY_PICK_HEAD and confused later steps.
>>>
>>> Expecting a reroll.
>>> ($gmane/271856)
>>
>> Actually, there had been two re-rolls, and v3 seemed to be okay:
>> $gmane/272037. It also looks as if 726a35ebd^..726a35ebd^2 is
>> identical with v3... Anything you want me to change in addition?
>
> Thanks for a pointer; I think I updated the topic and then forgot to
> update the reference in "whats cooking". I'll take a look at 272037
> and if I have anything further will comment there.
Thanks.
>> Also:
>>
>>> * js/fsck-opt (2015-06-22) 19 commits
>>> [...]
>>>
>
> [...]
>
> If the for-layout is the only thing that is questionable thing to
> fix in what I queued, I think I can locally fix-up without an extra
> roundtrip.
It is the only thing (and not even questionable ;-)).
Thanks!
Dscho
prev parent reply other threads:[~2015-06-24 7:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 22:49 What's cooking in git.git (Jun 2015, #05; Mon, 22) Junio C Hamano
2015-06-23 17:24 ` Johannes Schindelin
2015-06-23 20:46 ` Junio C Hamano
2015-06-24 7:16 ` Johannes Schindelin [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ad998ee2d8387401a3ceb6a7df7457ab@www.dscho.org \
--to=johannes.schindelin@gmx.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).