From: Junio C Hamano <gitster@pobox•com>
To: "Jason Pyeron" <jpyeron@pdinc•us>
Cc: <git@vger•kernel.org>
Subject: Re: RFC: update hook for GPG signed submission on secured branches
Date: Fri, 16 Jan 2015 11:41:01 -0800 [thread overview]
Message-ID: <xmqqoapy1pki.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <xmqqsifa1px6.fsf@gitster.dls.corp.google.com> (Junio C. Hamano's message of "Fri, 16 Jan 2015 11:33:25 -0800")
Junio C Hamano <gitster@pobox•com> writes:
> I am not sure if you need these unsightly backslashes. When you
> stop talking to it after saying "$(", or "$( git cat-file ... |",
> the shell _knows_ that you haven't stopped what you want to tell
> it.
Ehh, s/stopped/finished/, that is.
next prev parent reply other threads:[~2015-01-16 19:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 19:03 RFC: update hook for GPG signed submission on secured branches Jason Pyeron
2015-01-16 19:33 ` Junio C Hamano
2015-01-16 19:41 ` Junio C Hamano [this message]
2015-01-16 19:47 ` Jason Pyeron
2015-01-16 19:59 ` John Keeping
2015-01-16 22:49 ` Junio C Hamano
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=xmqqoapy1pki.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=jpyeron@pdinc$(echo .)us \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox