From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: phillip.wood@dunelm.org.uk, Warren He <pickydaemon@gmail.com>,
git@vger.kernel.org, wh109@yahoo.com
Subject: Re: [PATCH v2] rebase: introduce --update-branches option
Date: Mon, 09 Sep 2019 11:11:38 -0700 [thread overview]
Message-ID: <xmqqwoehjq5h.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1909091605540.5377@tvgsbejvaqbjf.bet> (Johannes Schindelin's message of "Mon, 9 Sep 2019 16:13:16 +0200 (CEST)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> In contrast, I would think that
>
> label --update-branch my-side-track
>
> would make for a nicer read than
>
> label my-side-track
> branch my-side-track
Because labelling while recreating a mergey history is conceptually
the same as temporarily updating the branch head from end users'
point of view, so this sounds quite sensible.
next prev parent reply other threads:[~2019-09-09 18:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 23:41 [PATCH] rebase: introduce --update-branches option Warren He
2019-09-02 23:41 ` Warren He
2019-09-03 13:26 ` Johannes Schindelin
2019-09-07 23:44 ` [PATCH v2] " Warren He
2019-09-07 23:44 ` Warren He
2019-09-09 10:44 ` Phillip Wood
2019-09-09 14:13 ` Johannes Schindelin
2019-09-09 18:11 ` Junio C Hamano [this message]
2019-09-23 9:40 ` Phillip Wood
2019-09-03 0:50 ` [PATCH] " brian m. carlson
2019-09-03 1:21 ` Junio C Hamano
2019-09-03 1:39 ` Taylor Blau
2019-09-07 23:41 ` Warren He
2019-09-08 18:04 ` brian m. carlson
2019-09-03 12:19 ` Phillip Wood
2019-09-07 23:43 ` Warren He
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=xmqqwoehjq5h.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=phillip.wood@dunelm.org.uk \
--cc=pickydaemon@gmail.com \
--cc=wh109@yahoo.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).