From: Sven van Haastregt <svenvh@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-submodule.sh: shorten submodule SHA-1s using rev-parse
Date: Tue, 22 Jan 2019 21:38:12 +0000 [thread overview]
Message-ID: <5C478D44.2070405@gmail.com> (raw)
In-Reply-To: <xmqqfttkfnmy.fsf@gitster-ct.c.googlers.com>
On 22/01/19 20:22, Junio C Hamano wrote:
> One thing it is not clear to me is that this codepath is prepared to
> handle sha1_src and sha1_dst referring to an object that does not
> exist (i.e. $missing_(src|dst)=t); the original code will still give
> us 7 hexdigit to show on the headline, but does the updated code
> that uses "rev-parse --short" give us a reasonable output?
Good point, I expect it will output an error message in that case. I
suppose we can fallback to the old echo and cut if the object does not
exist; I'll update the patch.
>> diff --git a/git-submodule.sh b/git-submodule.sh
>> index 5e608f8bad..a422b0728d 100755
>> --- a/git-submodule.sh
>> +++ b/git-submodule.sh
>> @@ -850,8 +850,8 @@ cmd_summary() {
>> ;;
>> esac
>>
>> - sha1_abbr_src=$(echo $sha1_src | cut -c1-7)
>> - sha1_abbr_dst=$(echo $sha1_dst | cut -c1-7)
>> + sha1_abbr_src=$(GIT_DIR="$name/.git" git rev-parse --short $sha1_src)
>> + sha1_abbr_dst=$(GIT_DIR="$name/.git" git rev-parse --short $sha1_dst)
>> if test $status = T
>> then
>> blob="$(gettext "blob")"
>
prev parent reply other threads:[~2019-01-22 21:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-20 20:46 [PATCH] git-submodule.sh: shorten submodule SHA-1s using rev-parse Sven van Haastregt
2019-01-22 15:24 ` Johannes Schindelin
2019-01-22 20:23 ` Junio C Hamano
2019-01-24 21:49 ` Jeff King
2019-01-25 13:05 ` Johannes Schindelin
2019-01-22 20:22 ` Junio C Hamano
2019-01-22 21:38 ` Sven van Haastregt [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5C478D44.2070405@gmail.com \
--to=svenvh@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.