exit
code in any command will stop the && chain.
Signed-off-by: Prathamesh Chavan
---
Hi, I am Prathamesh Chavan. This is my microproject which I have attempted
for Google Summer of Code for 2017.
Also in this new version of patch I have changed sendemail.name configuration
of the .gitcon
Hey everyone,
I am Prathamesh. I am studying Computer Science and Engineering at IIT
Kharagpur. I am interested to participate in Google Summer of Code 2017
under Git organization. I attempted "Avoid pipes in git related commands
for test suite" as my microproject[1].
As a part of GSoC, I would l
On Thu, Mar 9, 2017 at 6:00 PM, Christian Couder
wrote:
> On Thu, Mar 9, 2017 at 10:53 AM, Prathamesh Chavan wrote:
>> Whenever a git command is present in the upstream of a pipe, its failure
>> gets masked by piping and hence it should be avoided for testing the
>> ups
From: Prathamesh
Whenever a git command is present in the upstream of a pipe, its failure
gets masked by piping and hence it should be avoided for testing the
upstream git command. By writing out the output of the git command to
a file, we can test the exit codes of both the commands as a failure
From: Prathamesh
Whenever a git command is present in the upstream of a pipe, its failure
gets masked by piping and hence it should be avoided for testing the
upstream git command. By writing out the output of the git command to
a file, we can test the exit codes of both the commands as a failure
From: Prathamesh
Whenever a git command is present in the upstream of a pipe, its failure
gets masked by piping and hence it should be avoided for testing the
upstream git command. By writing out the output of the git command to
a file, we can test the exit codes of both the commands as a failure
Whenever a git command is present in the upstream of a pipe, its failure
gets masked by piping and hence it should be avoided for testing the
upstream git command. By writing out the output of the git command to
a file, we can test the exit codes of both the commands as a failure exit
code in any c
The exit code of the upstream of a pipe is ignored thus we should avoid
using it. By writing out the output of the git command to a file, we
can test the exit codes of both the commands.
Signed-off-by: Prathamesh
---
t/t2027-worktree-list.sh | 14 +++---
1 file changed, 7 insertions(+),
On Thu, Mar 9, 2017 at 1:38 PM, Christian Couder
wrote:
> On Wed, Mar 8, 2017 at 4:13 PM, Prathamesh Chavan wrote:
>> The exit code of the upstream of a pipe is ignored thus we should avoid
>> using it.
>
> You might want to say more specifically that we should avoid piping
, Prathamesh Chavan wrote:
> On Wed, Mar 8, 2017 at 11:33 AM, Jeff King wrote:
>> On Tue, Mar 07, 2017 at 12:52:49PM -0800, Stefan Beller wrote:
>>
>>> On Tue, Mar 7, 2017 at 12:39 PM, Johannes Sixt wrote:
>>>
>>> > Welcome to the Git community!
>>>
&g
PM, Jon Loeliger wrote:
> So, like, Prathamesh Chavan said:
>> The exit code of the upstream of a pipe is ignored thus we should avoid
>> using it. By writing out the output of the git command to a file, we
>> can test the exit codes of both the commands.
>>
&
But when I read the function carefully, it only removes the trash files created
when test_failure is equal to zero. But as far as I know, I can see the files
being removed even when a test_failure is non-zero for some test script.
On Thu, Mar 9, 2017 at 3:08 AM, Prathamesh Chavan wrote
The exit code of the upstream of a pipe is ignored thus we should avoid
using it. By writing out the output of the git command to a file, we
can test the exit codes of both the commands.
Signed-off-by: Prathamesh
---
t/t2027-worktree-list.sh | 14 +++---
1 file changed, 7 insertions(+),
On Wed, Mar 8, 2017 at 11:33 AM, Jeff King wrote:
> On Tue, Mar 07, 2017 at 12:52:49PM -0800, Stefan Beller wrote:
>
>> On Tue, Mar 7, 2017 at 12:39 PM, Johannes Sixt wrote:
>>
>> > Welcome to the Git community!
>>
>> >
>> > Actually, being a *micro* project, it should stay so. Not doing all of t
Hi,
I'm Prathamesh Chavan. As a part of my micropraoject I have been working on
"Avoid pipes for git related commands in test suites". I tried sending the
patch, but it got blocked since the mail contained more than 100 000
characters.
Hence, I have made the required changes in bra
Hi,
I'm Prathamesh Chavan. As a part of my micropraoject I have been working on
"Avoid pipes for git related commands in test suites". I tried sending the
patch, but it got blocked since the mail contained more than 100 000
characters.
Hence I'll like to attach the link to m
On Tue, Mar 7, 2017 at 3:52 PM, Vedant Bassi wrote:
> Hi,
>
> I would like to participate in GSoC 2017 and I have chosen the Use
> unsigned integral type for collection of bits , idea from the Micro
> projects list.
>
> I request the help of the community for clarifying a few questions that I
> h
201 - 217 of 217 matches
Mail list logo