From: Damien Robert <email@example.com> To: Junio C Hamano <firstname.lastname@example.org> Cc: email@example.com, Jeff King <firstname.lastname@example.org> Subject: Re: [PATCH v8 1/1] remote.c: fix handling of %(push:remoteref) Date: Fri, 11 Sep 2020 23:43:58 +0200 [thread overview] Message-ID: <20200911214358.acl3hy2e763begoo@feanor> (raw) In-Reply-To: <email@example.com> Hi Junio, From Junio C Hamano, Thu 03 Sep 2020 at 15:01:10 (-0700) : > Anything new on this topic? Unfortunately no, work keep stacking up faster than I can unstack it... > No rush, but I'd hate to see a basically good topic to be left in the stalled state too long. Hum, what about migrating the version that was in next to master? I am not fond of it because the series is not perfect and I am not satisfied with a patch series that is not as good as I would like it to be. So that was why I was arguing against merging it back then. On the other hand it does correct existing bugs, and the bugs it leaves remaining (apart from the memory leak) happens only in exotic cases. So I would not want my sense of perfection to prevent this series from graduating too long. And unfortunately I cannot give you an ETA for a fully satisfying series as I envision it. So I guess it is your call. If you think the version that was in next is good enough to graduate, I can send one last reroll with a commit message explaining the remaining kinks, and iron them out later. Or more precisely, we can: - only use this patch (v8) without the triangular workflow fixes - use this patch (v8) + the triangular workflow fixes from https://firstname.lastname@example.org/ The 'bug' that remains is that it detects a triangular setup, when 1) a branch has a pushRemote but no remote and 2) pushRemote=foobar and origin does not exists while 'git push' treat this as a non triangular workflow. IMHO 'git push' is wrong here and in my ideal perfect series it would be fixed there, but maybe meanwhile we can live with this small discrepancy. What do you think? -- Damien Robert http://www.normalesup.org/~robert/pro
next prev parent reply other threads:[~2020-09-11 21:44 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-02-28 17:24 [PATCH 1/1] remote.c: fix handling of push:remote_ref Damien Robert 2020-02-28 18:23 ` Jeff King 2020-03-01 22:05 ` Damien Robert 2020-03-02 13:32 ` Jeff King 2020-03-03 16:12 ` [PATCH v2 0/2] Damien Robert 2020-03-03 16:12 ` [PATCH v2 1/2] remote: drop "explicit" parameter from remote_ref_for_branch() Damien Robert 2020-03-03 17:51 ` Junio C Hamano 2020-03-03 21:11 ` Jeff King 2020-03-03 22:22 ` Junio C Hamano 2020-03-03 16:12 ` [PATCH v2 2/2] remote.c: fix handling of %(push:remoteref) Damien Robert 2020-03-03 16:29 ` Damien Robert 2020-03-03 18:29 ` Junio C Hamano 2020-03-03 18:21 ` Junio C Hamano 2020-03-03 22:24 ` Damien Robert 2020-03-03 22:48 ` Junio C Hamano 2020-03-12 16:45 ` [PATCH v3 1/1] " Damien Robert 2020-03-25 22:16 ` Damien Robert 2020-03-27 22:08 ` Junio C Hamano 2020-03-28 22:25 ` Damien Robert 2020-03-28 13:15 ` Jeff King 2020-03-28 13:31 ` Jeff King 2020-04-16 15:12 ` Damien Robert 2020-04-06 16:04 ` Damien Robert 2020-04-06 21:46 ` Jeff King 2020-04-06 17:56 ` [RFC PATCH v4 0/2] %(push) and %(push:remoteref) bug fixes Damien Robert 2020-04-06 17:56 ` [PATCH v6 1/2] remote.c: fix %(push) for triangular workflows Damien Robert 2020-04-06 17:56 ` [PATCH v6 2/2] remote.c: fix handling of %(push:remoteref) Damien Robert 2020-04-16 15:03 ` [PATCH v8 1/1] " Damien Robert 2020-04-16 15:21 ` Damien Robert 2020-09-03 22:01 ` Junio C Hamano 2020-09-11 21:43 ` Damien Robert [this message] 2020-09-14 22:21 ` Junio C Hamano 2020-03-03 16:16 ` [PATCH 1/1] remote.c: fix handling of push:remote_ref Damien Robert 2020-03-02 13:48 ` Jeff King 2020-03-03 16:25 ` Damien Robert
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=20200911214358.acl3hy2e763begoo@feanor \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH v8 1/1] remote.c: fix handling of %(push:remoteref)' \ /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
Code repositories for project(s) associated with this 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).