Hey Junio,
On Sun, Jan 8, 2017 at 2:48 AM, Junio C Hamano wrote:
> I see v3 that has 2>&1 but according to Luke's comment ("the message
> comes from cat"), it shouldn't be there? I am behind clearing the
> backlog in my mailbox and I could tweak it out from v3 while
>
Pranit Bauva writes:
> Hey Johannes,
>
> On Sun, Jan 1, 2017 at 8:20 PM, Johannes Sixt wrote:
>> which makes me wonder: Is the message that we do expect not to occur
>> actually printed on stdout? It sounds much more like an error message, i.e.,
>> text
On Sat, Dec 31, 2016 at 3:44 AM, Pranit Bauva wrote:
> test_must_fail should only be used for testing git commands. To test the
> failure of other commands use `!`.
>
> Reported-by: Stefan Beller
> Signed-off-by: Pranit Bauva
Hey Johannes,
On Sun, Jan 1, 2017 at 8:20 PM, Johannes Sixt wrote:
> which makes me wonder: Is the message that we do expect not to occur
> actually printed on stdout? It sounds much more like an error message, i.e.,
> text that is printed on stderr. Wouldn't we need this?
>
>
On 1 January 2017 at 14:50, Johannes Sixt wrote:
> Am 01.01.2017 um 15:23 schrieb Luke Diamand:
>>
>> On 31 December 2016 at 11:44, Pranit Bauva wrote:
>>>
>>> diff --git a/t/t9813-git-p4-preserve-users.sh
>>> b/t/t9813-git-p4-preserve-users.sh
>>> index
Am 01.01.2017 um 15:23 schrieb Luke Diamand:
On 31 December 2016 at 11:44, Pranit Bauva wrote:
diff --git a/t/t9813-git-p4-preserve-users.sh b/t/t9813-git-p4-preserve-users.sh
index 0fe231280..2384535a7 100755
--- a/t/t9813-git-p4-preserve-users.sh
+++
On 31 December 2016 at 11:44, Pranit Bauva wrote:
> test_must_fail should only be used for testing git commands. To test the
> failure of other commands use `!`.
>
> Reported-by: Stefan Beller
> Signed-off-by: Pranit Bauva
>
test_must_fail should only be used for testing git commands. To test the
failure of other commands use `!`.
Reported-by: Stefan Beller
Signed-off-by: Pranit Bauva
---
t/t3510-cherry-pick-sequence.sh | 6 +++---
t/t5504-fetch-receive-strict.sh | 2
8 matches
Mail list logo