Re: t3600: refactor code according to comtemporary guidelines

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: t3600: refactor code according to comtemporary guidelines
From: Rohit Ashiwal <rohit.ashiwal265@xxxxxxxxx>
Date: Sun, 3 Mar 2019 19:43:58 +0530
Cc: Johannes.Schindelin@xxxxxx, christian.couder@xxxxxxxxx, git@xxxxxxxxxxxxxxx, rohit.ashiwal265@xxxxxxxxx, t.gummerer@xxxxxxxxx
In-reply-to: <xmqqwolgytk5.fsf@gitster-ct.c.googlers.com>
References: <xmqqwolgytk5.fsf@gitster-ct.c.googlers.com>

I agree to all the points that you mentioned.

On 2019-03-03 13:30 UTC Junio C Hamano <gitster@xxxxxxxxx> wrote:

> We prefer "test ..." over "[ ... ]" (Documentation/CodingGuidelines).

At first I thought this should go in [PATCH 3/3] but now I think this is
its real place.

Thanks
Rohit

References:
- Re: [PATCH 2/3] t3600: refactor code according to contemporary guidelines
  - From: Junio C Hamano

Prev by Date: Clearing logic
Next by Date: Re: [PATCH 2/2] tests: introduce --stress-jobs=<N>
Previous by thread: Re: [PATCH 2/3] t3600: refactor code according to contemporary guidelines
Next by thread: [PATCH 3/3] t3600: use helper functions from test-lib-functions
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel Development] [Gcc Help] [IETF Annouce] [DCCP] [Netdev] [Networking] [Security] [V4L] [Bugtraq] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux SCSI] [Fedora Users]

Powered by Linux