Re: [PATCH v2 09/11] t/t3437: cleanup the 'setup' test and use named commits in the tests

2 messages, 2 authors, 2021-02-09 · open the first message on its own page

Re: [PATCH v2 09/11] t/t3437: cleanup the 'setup' test and use named commits in the tests

From: Junio C Hamano <hidden>
Date: 2021-02-08 21:43:14

Charvi Mendiratta [off-list ref] writes:
Remove unnecessary curly braces and use the named commits in the
tests so that they will still refer to the same commit if the setup
gets changed in the future whereas 'branch~2' will change which commit
it points to.
Doing two things in the same commit?  I think ${EMPTY} thing is a
general style clean-up, while tagging is a bit more meaningful
change to make it easier to understand tests and is a change at a
more conceptual level.  The ${EMPTY} change would be better done at
the same time when the here document was cleaned up in [v2 05/11],
I would think.

Thanks.

Re: [PATCH v2 09/11] t/t3437: cleanup the 'setup' test and use named commits in the tests

From: Charvi Mendiratta <hidden>
Date: 2021-02-09 07:14:54

On Tue, 9 Feb 2021 at 03:11, Junio C Hamano [off-list ref] wrote:
Charvi Mendiratta [off-list ref] writes:
quoted
Remove unnecessary curly braces and use the named commits in the
tests so that they will still refer to the same commit if the setup
gets changed in the future whereas 'branch~2' will change which commit
it points to.
Doing two things in the same commit?  I think ${EMPTY} thing is a
general style clean-up, while tagging is a bit more meaningful
change to make it easier to understand tests and is a change at a
more conceptual level.  The ${EMPTY} change would be better done at
the same time when the here document was cleaned up in [v2 05/11],
I would think.
Okay, will move it to the other patch.

Thanks and Regards,
Charvi
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help