Re: Unexpected behavior with branch.*.{remote,pushremote,merge}

From: Felipe Contreras <felipe.contreras@gmail.com>
Date: Dec 4, 2020, 21:29 UTC
Message-ID: <CAMP44s391U8B5c0iLX84Gqcbg++nbaXs+g_duP82R--JAmLvcA@mail.gmail.com>
In-Reply-To: <601563bf-ed54-4795-917a-fce6e9343b79@www.fastmail.com>

On Fri, Dec 4, 2020 at 10:45 AM Ben Denhartog <ben@sudoforge.com> wrote:

>
> I'm just now hearing the terminology "triangular workflow" (I may live under a rock), but that aptly and succintly describes the workflow I was attempting to simplify with my initial configuration.
>
> I read the article on your blog, and the solution you propose makes sense to me, at least in the context of triangular workflows. I don't see any public feedback on your patch; bummer to see. Is it something you've brought up since 2014?

It did receive some positive public feedback. At least v3 of the series:

https://lore.kernel.org/git/xmqq38hkx4lr.fsf@gitster.dls.corp.google.com/

But my patches have a tendency to enact resistance. Perhaps more so back then.

I have not brought it up since then. I currently have like 4 patch series stuck, doesn't seem wise to add another one. But I likely will at some point.

It is the single most important feature I think Git is lacking. Having accustomed myself to the publish branch, I now feel like missing a finger without it on git vanilla.

Cheers.

-- 
Felipe Contreras