From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Shourya Shukla <shouryashukla.oo@gmail.com>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH 0/3] t6025: updating tests
Date: Thu, 16 Jan 2020 22:46:36 +0100 (CET) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.2001162243100.46@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <20200116203622.4694-1-shouryashukla.oo@gmail.com>
Hi,
On Fri, 17 Jan 2020, Shourya Shukla wrote:
> Greetings everyone!
>
> This is my first ever contribution in the Open-Source Community and I chose Git
> for this purpose as I have been using this important tool to maintain my projects
> regularly.
>
> In this patch, I have:
>
> - modernized these tests so that they meet current Git CodingGuidlines[1]
> - replaced the pipe operator with the redirection operator so that one can
> detect the errors easily and precisely
> - used helper function 'test_path_is_file()' to replace 'test -f' checks in
> in the program as it improves the readability of the code and provides
> better error messages
>
> Also, I have some questions to better my understanding of the code:
> - In the statement,
> > git hash-object -t blob -w --stdin
> is it necessary to explicitly specify the type 'blob' of the hash-object?
> I have this question because it is the default type of hash-object.
It is the default type, but:
1) the code is not broken, so why fix it?
2) it _might_ be possible that the default changes, or can be configured
in the future. The original author might just have wanted to stay safe.
> - In the statement,
> > l=$(printf file | git hash-object -t blob -w --stdin)
> I have not used the redirection operator as this sub-shell will be executed
> separately, hence its error cannot be captured therefore the presence of '>'
> will not matter. Will using '>' improve the code?
It will be enhanced, though:
printf file >file &&
l=$(git hash-object -t blob -w --stdin)
will have a non-zero exit code if the `hash_object` call fails.
>
> Thanks,
> Shourya Shukla
>
> Shourya Shukla (3):
> t6025: modernize style
> t6025: replace pipe with redirection operator
> t6025: use helpers to replace test -f <path>
Apart from one little issue in the first patch, this all looks very good
to me.
Thanks,
Johannes
>
> t/t6025-merge-symlinks.sh | 97 ++++++++++++++++++++-------------------
> 1 file changed, 50 insertions(+), 47 deletions(-)
>
> --
> 2.20.1
>
prev parent reply other threads:[~2020-01-16 21:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 20:36 [PATCH 0/3] t6025: updating tests Shourya Shukla
2020-01-16 20:36 ` [PATCH 1/3] t6025: modernize style Shourya Shukla
2020-01-16 21:42 ` Johannes Schindelin
2020-01-16 20:36 ` [PATCH 2/3] t6025: replace pipe with redirection operator Shourya Shukla
2020-01-16 22:57 ` Junio C Hamano
2020-01-16 20:36 ` [PATCH 3/3] t6025: use helpers to replace test -f <path> Shourya Shukla
2020-01-16 22:58 ` Junio C Hamano
2020-01-17 20:44 ` [PATCH 0/3] t6025: amended changes after suggestions from the community Shourya Shukla
2020-01-17 20:44 ` [PATCH 1/3] t6025: modernize style Shourya Shukla
2020-01-17 21:15 ` Eric Sunshine
2020-01-17 21:28 ` Junio C Hamano
2020-01-17 20:44 ` [PATCH 2/3] t6025: replace pipe with redirection operator Shourya Shukla
2020-01-17 21:24 ` Eric Sunshine
2020-01-18 8:33 ` [PATCH 0/3] t6025: updating tests Shourya Shukla
2020-01-18 8:33 ` [PATCH 1/3] t6025: modernize style Shourya Shukla
2020-01-18 8:33 ` [PATCH 2/3] t6025: replace pipe with redirection operator Shourya Shukla
2020-01-18 8:33 ` [PATCH 3/3] t6025: use helpers to replace test -f <path> Shourya Shukla
2020-01-18 8:33 ` [PATCH v3 0/2] t025: amended changes after suggestions from the community Shourya Shukla
2020-01-18 8:33 ` [PATCH v3 1/2] t6025: modernize style Shourya Shukla
2020-01-21 21:57 ` Junio C Hamano
2020-01-18 8:33 ` [PATCH v3 2/2] t6025: use helpers to replace test -f <path> Shourya Shukla
2020-01-21 21:58 ` Junio C Hamano
2020-01-17 20:44 ` [PATCH 3/3] " Shourya Shukla
2020-01-16 21:46 ` Johannes Schindelin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nycvar.QRO.7.76.6.2001162243100.46@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=shouryashukla.oo@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).