From: Junio C Hamano <gitster@pobox.com>
To: Andrea Stacchiotti <andreastacchiotti@gmail.com>
Cc: Andrea Stacchiotti via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH] branch: move multiple branches in a single --force
Date: Thu, 12 Jun 2025 02:55:31 -0700 [thread overview]
Message-ID: <xmqqjz5hffn0.fsf@gitster.g> (raw)
In-Reply-To: <CAEgWtF9MRbRASg1Jb3n6Ggvh8viZOpyev+OyX5DSpWQ7bMF8dg@mail.gmail.com> (Andrea Stacchiotti's message of "Thu, 12 Jun 2025 02:19:18 +0200")
Andrea Stacchiotti <andreastacchiotti@gmail.com> writes:
> So, if I may ask, is the proposed patch as written (branch -f A B C X)
> acceptable and you just need me to rewrite the commit message
> or are you not interested in it at all?
As I said, I personally am not interested in such a mode, but you
may be able to interest other people in it, and with wider support
I may change my mind. But I do not think the feature should not be
tied to "--force" option at all. "git branch A B C X" should be
able to create three new branches A B C that all tracks X if none of
them exist without "--force".
next prev parent reply other threads:[~2025-06-12 9:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 9:07 [PATCH] branch: move multiple branches in a single --force Andrea Stacchiotti via GitGitGadget
2025-06-10 21:25 ` Junio C Hamano
2025-06-10 22:17 ` Andrea Stacchiotti
2025-06-11 0:22 ` Junio C Hamano
2025-06-11 8:34 ` Andrea Stacchiotti
2025-06-11 15:26 ` Junio C Hamano
2025-06-12 0:19 ` Andrea Stacchiotti
2025-06-12 9:55 ` Junio C Hamano [this message]
2025-06-12 15:48 ` Junio C Hamano
2025-06-12 16:51 ` Andrea Stacchiotti
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=xmqqjz5hffn0.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=andreastacchiotti@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@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.