From: Damien Robert <damien.olivier.robert@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2020, #01; Wed, 15)
Date: Thu, 16 Apr 2020 23:12:08 +0200 [thread overview]
Message-ID: <20200416211208.xqnnrkvcl2jw3ejr@doriath> (raw)
In-Reply-To: <xmqqr1wo4alb.fsf@gitster.c.googlers.com>
From Junio C Hamano, Wed 15 Apr 2020 at 16:01:52 (-0700) :
> * dr/push-remoteref-fix (2020-04-06) 2 commits
> (merged to 'next' on 2020-04-15 at ecf60dc488)
> + remote.c: fix handling of %(push:remoteref)
> + remote.c: fix %(push) for triangular workflows
Hi Junio,
I just sent a new version of this series, which drop the second patch for
now. As outlined in my cover letter in
https://public-inbox.org/git/20200406175648.25737-1-damien.olivier.robert+git@gmail.com/
the triangular workflow patch still leaves some corner cases (and for now
is missing reviews).
I'd prefer to fix all of them at once, rather than have an almost working
patch. Jeff seems to be of the same opinion in
https://public-inbox.org/git/20200406214607.GA1251506@coredump.intra.peff.net/
next prev parent reply other threads:[~2020-04-16 21:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 23:01 What's cooking in git.git (Apr 2020, #01; Wed, 15) Junio C Hamano
2020-04-16 15:28 ` Elijah Newren
2020-04-16 16:37 ` Junio C Hamano
2020-04-16 21:12 ` Damien Robert [this message]
2020-04-16 21:30 ` Jeff King
2020-04-16 22:18 ` Junio C Hamano
2020-04-16 22:47 ` Damien Robert
2020-04-16 23:05 ` Damien Robert
2020-04-16 23:34 ` Junio C Hamano
2020-04-17 12:54 ` Damien Robert
2020-04-17 17:30 ` Junio C Hamano
2020-04-17 22:04 ` Damien Robert
2020-04-17 23:22 ` Junio C Hamano
2020-04-18 17:36 ` Damien Robert
2020-04-17 2:24 ` Danh Doan
2020-04-17 5:38 ` Junio C Hamano
2020-04-17 13:36 ` Danh Doan
2020-04-17 17:40 ` Junio C Hamano
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=20200416211208.xqnnrkvcl2jw3ejr@doriath \
--to=damien.olivier.robert@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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;
as well as URLs for NNTP newsgroup(s).