From: Junio C Hamano <gitster@pobox.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Jeff King <peff@peff.net>, Git List <git@vger.kernel.org>,
Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: [PATCH v4 0/6] Support triangular workflows
Date: Sun, 31 Mar 2013 22:35:05 -0700 [thread overview]
Message-ID: <7vhajqlsom.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <7vppyeltz7.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Sun, 31 Mar 2013 22:07:08 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Junio C Hamano <gitster@pobox.com> writes:
>
>> Ramkumar Ramachandra <artagnon@gmail.com> writes:
>>
>>> Junio C Hamano wrote:
>>>> Jeff King <peff@peff.net> writes:
>>>>> [...]
>>>> Thanks. That is one of the reasons why we do not want to see too
>>>> many custom test helper functions.
>>>
>>> I noticed that you queued my original series without modification in
>>> rr/triangle. Should I submit a re-roll with Peff's suggestion
>>> incorporated?
>>
>> If you want the topic to make progress, yes.
>
> By the way, this series seems to break a few tests in the test
> suite,...
I suspect this could be interaction with push-default change near
the tip of 'pu'. Setting push.default explicitly to matching in the
test may be necessary.
Also the t5516 is involved in in-flight churns, so there could be
some merge mixups.
next prev parent reply other threads:[~2013-04-01 5:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 13:26 [PATCH v4 0/6] Support triangular workflows Ramkumar Ramachandra
2013-03-28 13:26 ` [PATCH 1/6] remote.c: simplify a bit of code using git_config_string() Ramkumar Ramachandra
2013-03-28 13:26 ` [PATCH 2/6] t5516 (fetch-push): update test description Ramkumar Ramachandra
2013-03-28 13:26 ` [PATCH 3/6] t5516 (fetch-push): drop implicit arguments from helper functions Ramkumar Ramachandra
2013-03-28 13:26 ` [PATCH 4/6] remote.c: introduce a way to have different remotes for fetch/push Ramkumar Ramachandra
2013-03-28 13:26 ` [PATCH 5/6] remote.c: introduce remote.pushdefault Ramkumar Ramachandra
2013-03-28 13:26 ` [PATCH 6/6] remote.c: introduce branch.<name>.pushremote Ramkumar Ramachandra
2013-03-28 15:02 ` [PATCH v4 0/6] Support triangular workflows Junio C Hamano
2013-03-28 15:35 ` Jeff King
2013-03-28 16:54 ` Junio C Hamano
2013-03-31 20:54 ` Ramkumar Ramachandra
2013-04-01 1:56 ` Junio C Hamano
2013-04-01 3:36 ` Junio C Hamano
2013-04-01 5:07 ` Junio C Hamano
2013-04-01 5:35 ` Junio C Hamano [this message]
2013-03-31 20:51 ` Ramkumar Ramachandra
2013-03-31 21:43 ` Jeff King
2013-04-01 1:50 ` 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=7vhajqlsom.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
/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).