git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Sahil Dua <sahildua2305@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Sep 2017, #03; Fri, 15)
Date: Mon, 25 Sep 2017 09:40:31 +0900	[thread overview]
Message-ID: <xmqq7ewnhaps.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CALiud+mjN=cTg_CXWNWnE=0N5RiT-FEN5JMGbYW0byMbmexQvQ@mail.gmail.com> (Sahil Dua's message of "Sun, 24 Sep 2017 18:16:48 +0200")

Sahil Dua <sahildua2305@gmail.com> writes:

> On Fri, Sep 22, 2017 at 5:39 AM, Junio C Hamano <gitster@pobox.com> wrote:
>>
>> So here is such an update.  As the topic is not in 'next' yet, it
>> could also be implemented by replacing patch(es) in the series, but
>> doing it as a follow-up fix made it easier to see what got changed
>> (both in the code and in the tests), so that is how I decided to do
>> this patch.
>>
> Awesome! Thanks for the patch. It was easier than I'd have expected it
> to be. Looks like it fixes the concerns of moving head. Is there
> anythign required from my side on this features / series of patches?

If you now agree with the updated behaviour and think it makes more
sense that "git branch -c new HEAD" does not check out 'new', then
there is nothing required.  Well, other than the usual finding,
reporting and optionally fixing bugs in the documentation and the
code, that is ;-)

Thanks.

      reply	other threads:[~2017-09-25  0:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-15  5:58 What's cooking in git.git (Sep 2017, #03; Fri, 15) Junio C Hamano
2017-09-15  7:50 ` Lars Schneider
2017-09-19  1:18   ` Junio C Hamano
2017-09-15 19:14 ` Johannes Schindelin
2017-09-15 20:33   ` Junio C Hamano
2017-09-15 19:23 ` Johannes Schindelin
2017-09-15 20:49   ` Junio C Hamano
2017-09-29 11:39     ` Johannes Schindelin
2017-09-21 21:14 ` Sahil Dua
2017-09-22  0:59   ` Junio C Hamano
2017-09-22  3:39     ` Junio C Hamano
2017-09-24 16:16       ` Sahil Dua
2017-09-25  0:40         ` Junio C Hamano [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=xmqq7ewnhaps.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=sahildua2305@gmail.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).