From: Eugene Sajine <euguess@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Ralf Thielow <ralf.thielow@gmail.com>, git <git@vger.kernel.org>,
Andrew Ardill <andrew.ardill@gmail.com>
Subject: Re: Help creating git alias
Date: Wed, 30 Oct 2013 21:26:52 -0400 [thread overview]
Message-ID: <CAPZPVFarK_jKpM2f62mErAmL+mck6EN1QPfHDHqqfJbJ2AfzXg@mail.gmail.com> (raw)
In-Reply-To: <xmqq61sebhh3.fsf@gitster.dls.corp.google.com>
On Wed, Oct 30, 2013 at 5:02 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Eugene Sajine <euguess@gmail.com> writes:
>
>> On Wed, Oct 30, 2013 at 3:57 PM, Ralf Thielow <ralf.thielow@gmail.com> wrote:
>>> lg=!git log --pretty=format:'%h %ad %ae %s' --date=short | sed 's/@\\S*//g'
>>>
>>> should work.
>>
>>
>> It did! thanks! I didn't know that "!sh -c" is not needed
>
> "sh -c" is often used when you pass arguments to your scriptlets,
> e.g. to allow
>
> git lg master..next
>
> you would want
>
> sh -c 'git log ... "$@" | sed ...' -
>
> so that
>
> git lg master..next
>
> turns into
>
> sh -c 'git log ... "$@" | sed ...' - master..next
>
> which makes $1="master..next" and fed to "git log".
Junio,
That was my initial intention, because I would like to be able to pass
parameters like to git log or git blame correctly without the explicit
use of $1. Could you please advise about how to make it work with the
!sh -c ?
Because the same exact (sed 's/@\\S*//') syntax didn't work with "sh -c".
Thanks,
Eugene
next prev parent reply other threads:[~2013-10-31 1:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 19:34 Help creating git alias Eugene Sajine
2013-10-30 19:47 ` Andrew Ardill
2013-10-30 19:53 ` Eugene Sajine
2013-10-30 19:57 ` Ralf Thielow
2013-10-30 20:10 ` Eugene Sajine
2013-10-30 21:02 ` Junio C Hamano
2013-10-31 1:26 ` Eugene Sajine [this message]
2013-10-31 3:54 ` Junio C Hamano
2013-10-31 15:36 ` Eugene Sajine
2013-10-31 17:40 ` David Aguilar
2013-10-31 18:07 ` Junio C Hamano
2013-10-31 18:15 ` David Aguilar
2013-10-31 19:31 ` Eugene Sajine
2013-10-31 19:41 ` Junio C Hamano
2013-10-31 20:06 ` Eugene Sajine
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=CAPZPVFarK_jKpM2f62mErAmL+mck6EN1QPfHDHqqfJbJ2AfzXg@mail.gmail.com \
--to=euguess@gmail.com \
--cc=andrew.ardill@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ralf.thielow@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.
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 NNTP newsgroup(s).