From: Junio C Hamano <gitster@pobox.com>
To: Oleg Taranenko <olegtaranenko@gmail.com>
Cc: Ben Peart <peartben@gmail.com>, git <git@vger.kernel.org>,
pclouds@gmail.com, Ben Peart <benpeart@microsoft.com>
Subject: Re: [PATCH v3] checkout: eliminate unnecessary merge for trivial checkout
Date: Wed, 14 Sep 2016 08:48:28 -0700 [thread overview]
Message-ID: <xmqqintyscs3.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CABEd3j_FrWhOe_jXcc+VJWiyy80SG1JfbZC9woRU2cqdzjkGyA@mail.gmail.com> (Oleg Taranenko's message of "Wed, 14 Sep 2016 08:30:49 +0200")
Oleg Taranenko <olegtaranenko@gmail.com> writes:
> Sorry for bothering, why not introduce a brand new option like git
> checkout -b foo --skip-worktree-merge for such rare optimization use
> case?
I am not sure what problem such a new option solves. How would you
describe and explain what "--skip-worktree-merge" option to the end
user?
next prev parent reply other threads:[~2016-09-14 15:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 14:26 [PATCH v3] checkout: eliminate unnecessary merge for trivial checkout Ben Peart
2016-09-13 22:34 ` Junio C Hamano
2016-09-14 6:30 ` Oleg Taranenko
2016-09-14 15:48 ` Junio C Hamano [this message]
[not found] ` <BL2PR03MB3232D3128A72D4EC9ADC2C6F4F10@BL2PR03MB323.namprd03.prod.outlook.com>
[not found] ` <BL2PR03MB323E1B2F810C63CB01AA234F4F30@BL2PR03MB323.namprd03.prod.outlook.com>
2016-09-19 13:18 ` Ben Peart
2016-09-19 16:30 ` Junio C Hamano
2016-09-19 17:03 ` Junio C Hamano
2016-09-21 18:32 ` Ben Peart
2016-09-24 14:28 ` Philip Oakley
2016-09-24 18:26 ` Junio C Hamano
2016-09-24 19:31 ` Philip Oakley
-- strict thread matches above, loose matches on Subject: below --
2016-09-28 17:02 Ben Peart
2016-09-28 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=xmqqintyscs3.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=benpeart@microsoft.com \
--cc=git@vger.kernel.org \
--cc=olegtaranenko@gmail.com \
--cc=pclouds@gmail.com \
--cc=peartben@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.