From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: guix-devel <guix-devel@gnu.org>
Subject: Re: pre-push signature hook error reporting [was Re: [PATCH v6] gnu: python-sphinx: Update to 1.4.8.]
Date: Tue, 17 Jan 2017 13:56:29 +0100 [thread overview]
Message-ID: <587E147D.2000203@crazy-compilers.com> (raw)
In-Reply-To: <20170117123424.714a23b5@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 508 bytes --]
Am 17.01.2017 um 12:34 schrieb Danny Milosavljevic:
> For minimal improvement (I don't even think it's measureable), try `git rev-list HEAD` (backquotes) - it prevents having to spawn a subshell.
Huh? I doubt this. The bash manual, section "Command Substitution" does
not distinguish between these both, as far as I understand it.
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
[-- Attachment #2: 0xBF773B65.asc --]
[-- Type: application/pgp-keys, Size: 14855 bytes --]
next prev parent reply other threads:[~2017-01-17 12:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 16:14 [PATCH v6] gnu: python-sphinx: Update to 1.4.8 Danny Milosavljevic
2017-01-05 16:40 ` Marius Bakke
[not found] ` <8760lj5eb6.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me>
[not found] ` <20170113152400.GA24322@jasmine>
2017-01-17 3:14 ` pre-push signature hook error reporting [was Re: [PATCH v6] gnu: python-sphinx: Update to 1.4.8.] Leo Famulari
2017-01-17 11:34 ` Danny Milosavljevic
2017-01-17 12:56 ` Hartmut Goebel [this message]
2017-01-17 19:44 ` Leo Famulari
2017-01-17 19:38 ` Leo Famulari
2017-01-17 14:55 ` Hartmut Goebel
2017-01-17 19:39 ` Leo Famulari
2017-01-20 14:05 ` Ludovic Courtès
2017-01-21 1:39 ` Leo Famulari
2017-02-06 15:39 ` pre-push signature hook error reporting Leo Famulari
2017-02-06 16:37 ` Marius Bakke
2017-02-07 13:15 ` Ludovic Courtès
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: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=587E147D.2000203@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=guix-devel@gnu.org \
/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://git.savannah.gnu.org/cgit/guix.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).