From: "Marc-André Lureau" <marcandre.lureau@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "SZEDER Gábor" <szeder.dev@gmail.com>,
"Eric Sunshine" <sunshine@sunshineco.com>,
"Git List" <git@vger.kernel.org>
Subject: Re: [PATCH] branch: let '--edit-description' default to rebased branch during rebase
Date: Fri, 7 Feb 2020 20:09:16 +0100 [thread overview]
Message-ID: <CAJ+F1C+qGo=6QrRw2299Apr2+-CHNWQyzWjvWbXJN5KC+T63AQ@mail.gmail.com> (raw)
In-Reply-To: <xmqq1rr6444s.fsf@gitster-ct.c.googlers.com>
Hi
On Fri, Feb 7, 2020 at 7:57 PM Junio C Hamano <gitster@pobox.com> wrote:
>
> Marc-André Lureau <marcandre.lureau@gmail.com> writes:
>
> > Also, when doing --edit-description there are comments like:
> >
> > # Please edit the description for the branch
> > # unrelated-history
> >
> > What else do you suggest?
>
> How about teaching "git branch --edit-description [HEAD]" notice
> when/if HEAD is detached and always error out, no matter what
> operation is in progress?
Then --edit-description during won't default to the branch you started
from the bisect. So we are back to my original proposal only, having
branch default during rebase. Eric, do you mind?
--
Marc-André Lureau
next prev parent reply other threads:[~2020-02-07 19:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-11 12:35 [PATCH] branch: let '--edit-description' default to rebased branch during rebase marcandre.lureau
2020-01-11 13:26 ` Eric Sunshine
2020-01-11 14:54 ` Marc-André Lureau
2020-01-12 1:27 ` Eric Sunshine
2020-01-12 6:44 ` Marc-André Lureau
2020-01-12 12:14 ` SZEDER Gábor
2020-01-13 1:59 ` Eric Sunshine
2020-01-24 22:41 ` SZEDER Gábor
2020-01-30 21:37 ` Marc-André Lureau
2020-01-31 15:52 ` SZEDER Gábor
2020-01-31 15:59 ` Marc-André Lureau
2020-01-31 16:16 ` SZEDER Gábor
2020-02-06 22:26 ` Marc-André Lureau
2020-02-07 10:02 ` SZEDER Gábor
2020-02-07 14:16 ` Marc-André Lureau
2020-02-07 18:57 ` Junio C Hamano
2020-02-07 19:09 ` Marc-André Lureau [this message]
2020-02-07 19:12 ` Junio C Hamano
2020-02-07 19:29 ` Eric Sunshine
2020-02-07 20:14 ` 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
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='CAJ+F1C+qGo=6QrRw2299Apr2+-CHNWQyzWjvWbXJN5KC+T63AQ@mail.gmail.com' \
--to=marcandre.lureau@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sunshine@sunshineco.com \
--cc=szeder.dev@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).