Re: [PATCH v4 0/6] Support triangular workflows

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: [PATCH v4 0/6] Support triangular workflows

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:56:33

Jeff King [off-list ref] writes:
Sometimes it's annoyingly verbose to break down a compound function. But
I think in this case, you can make your tests more robust by just
checking the affirmative that the ref is still where we expect it to be,
like:

  check_push_result up_repo $the_first_commit heads/master

Sorry if that was a bit long-winded. I think that practically speaking,
it is not a likely source of problems in this case. But it's an
anti-pattern in our tests that I think is worth mentioning.
Thanks.  That is one of the reasons why we do not want to see too
many custom test helper functions.

Re: [PATCH v4 0/6] Support triangular workflows

From: Ramkumar Ramachandra <hidden>
Date: 2016-06-15 22:56:35

Junio C Hamano wrote:
Jeff King [off-list ref] writes:
quoted
[...]
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?
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help