Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: "Volodymyr Vriukalo" <0@zitro.id>,
	"Atharva Raykar" <raykar.ath@gmail.com>,
	"Jean-Noël Avila" <jn.avila@free.fr>,
	"Olamide Caleb Bello" <belkid98@gmail.com>,
	"Glen Choo" <glencbz@gmail.com>,
	"Jonathan Tan" <jonathantanmy@fastmail.com>
Subject: Re: [PATCH 0/2] branch: fix --recurse-submodules with a nameless start point
Date: Mon, 02 Nov 2026 01:01:20 -0800	[thread overview]
Message-ID: <xmqqbj87mwtb.fsf@gitster.g> (raw)
In-Reply-To: <20260822-vv-branch-recurse-no-start-ref-v1-0-46dc140acaa8@zitro.id> (Volodymyr Vriukalo's message of "Sat, 22 Aug 2026 01:01:40 +0200")

Volodymyr Vriukalo <0@zitro.id> writes:

> vv/branch-recurse-no-start-ref
>
> "git branch" with submodule.propagateBranches enabled mishandled a
> start point that names no ref, such as a raw object id.  In a
> repository with no submodules it aborted with a BUG after having
> already moved the branch; with submodules it failed earlier, when the
> helper it invokes rejected a truncated argument list.  Both are the
> same missing tracking name, which has been corrected.

This has seen no reactions let alone reviews.  Nobody is interested?

Unless we see some volunteers to give it a review in a few weeks, I
will discard the topic out of my tree, as 'seen' has been crowded
with topics that have been collecting dust without getting many
reviews.

Thanks.

      parent reply	other threads:[~2026-11-02  9:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-21 23:01 [PATCH 0/2] branch: fix --recurse-submodules with a nameless start point Volodymyr Vriukalo
2026-08-21 23:01 ` [PATCH 1/2] branch: do not track a start point with no ref Volodymyr Vriukalo
2026-08-21 23:01 ` [PATCH 2/2] branch: allow recursion with no tracking name Volodymyr Vriukalo
2026-11-02  9:01 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqbj87mwtb.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=0@zitro.id \
    --cc=belkid98@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=glencbz@gmail.com \
    --cc=jn.avila@free.fr \
    --cc=jonathantanmy@fastmail.com \
    --cc=raykar.ath@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox