From: Felipe Contreras <felipe.contreras@gmail.com>
To: Ben Denhartog <ben@sudoforge.com>
Cc: Git <git@vger.kernel.org>
Subject: Re: Unexpected behavior with branch.*.{remote,pushremote,merge}
Date: Fri, 4 Dec 2020 15:29:43 -0600 [thread overview]
Message-ID: <CAMP44s391U8B5c0iLX84Gqcbg++nbaXs+g_duP82R--JAmLvcA@mail.gmail.com> (raw)
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
next prev parent reply other threads:[~2020-12-04 21:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 1:26 Unexpected behavior with branch.*.{remote,pushremote,merge} Ben Denhartog
2020-12-04 2:31 ` Felipe Contreras
2020-12-04 16:44 ` Ben Denhartog
2020-12-04 21:29 ` Felipe Contreras [this message]
2020-12-04 10:13 ` Jeff King
2020-12-04 16:45 ` Ben Denhartog
2020-12-04 19:57 ` Junio C Hamano
2020-12-04 21:00 ` Jeff King
2020-12-04 22:20 ` Ben Denhartog
-- strict thread matches above, loose matches on Subject: below --
2020-10-10 18:27 Ben Denhartog
2020-10-10 18:38 ` Ben Denhartog
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=CAMP44s391U8B5c0iLX84Gqcbg++nbaXs+g_duP82R--JAmLvcA@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=ben@sudoforge.com \
--cc=git@vger.kernel.org \
/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).