All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Rast <trast@inf.ethz.ch>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Jeff King" <peff@peff.net>, "René Haber" <rene@habr.de>,
	git@vger.kernel.org, "Will Palmer" <wmpalmer@gmail.com>
Subject: Re: Bug: pull --rebase with é in name
Date: Tue, 6 Mar 2012 09:36:31 +0100	[thread overview]
Message-ID: <87399mazxs.fsf@thomas.inf.ethz.ch> (raw)
In-Reply-To: <7v8vjf2c8o.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Mon, 05 Mar 2012 09:23:19 -0800")

Junio C Hamano <gitster@pobox.com> writes:

> Jeff King <peff@peff.net> writes:
>
>> It would be nice if the --pretty format placeholders had a "shell-quote"
>> modifier, and we could just do:
>>
>>   git show --format='GIT_AUTHOR_NAME=%(an:shell)'
>>
>> or something similar. for-each-ref knows about shell-quoting, but we
>> can't use it here, because we are looking at arbitrary commits, not just
>> ones pointed to by refs.
>
> You guys seem to have been having a lot of fun overnight. Perhaps I
> should live on European time?

IIUC Peff just got up at an unreasonably early time to have fun with us
Europeans?

> I think there were talks about cross pollinating and eventually
> unifying the placeholder languages of pretty and for-each-ref, and
> if we were to do so, I agree that --pretty definitely should learn
> to do --sq. But I do not think we want to teach everything :shell;
> following the style of %w(), something more generic that would apply
> to any payload would be preferred, perhaps giving an end result like
> this:
>
> 	git show -s --format='
> 		GIT_AUTHOR_NAME=%(sq-begin)%an%(sq-end)
>                 GIT_AUTHOR_EMAIL=%(sq-begin)%ae%(sq-end)
>         '

How about something along the lines of %Q(%an) instead?  Though at least
implementation-wise, it should be possible to make %'%an%' work, too,
which would be rather cute.

> In any case, my reading of the conclusion you guys have already
> reached in this thread is that the issue is not even a bug in Git,
> but is a broken build/installation of sed by a third-party.  I am
> inclined to suggest any change to get_author_ident_from_commit
> helper backburnered before we teach --sq to --pretty machinery.

Ok.

This is the second "victim" of this broken install of sed, however.  I
wonder where René and Will got it from?  Perhaps this is "the" common
way of getting GNU sed on OS X, and thus more widespread than we might
think.

-- 
Thomas Rast
trast@{inf,student}.ethz.ch

  parent reply	other threads:[~2012-03-06  8:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-05  9:59 Bug: pull --rebase with é in name René Haber
2012-03-05 10:26 ` Jeff King
2012-03-05 10:37   ` Thomas Rast
2012-03-05 11:42     ` René Haber
2012-03-05 11:58       ` Jeff King
2012-03-05 12:36         ` Jakub Narebski
2012-03-05 12:46         ` René Haber
2012-03-05 13:04           ` Thomas Rast
2012-03-05 13:19             ` René Haber
2012-03-05 13:29             ` Jeff King
2012-03-05 13:40               ` Thomas Rast
2012-03-05 13:50                 ` Jeff King
2012-03-05 17:23               ` Junio C Hamano
2012-03-06  8:23                 ` Jeff King
2012-03-06  8:36                 ` Thomas Rast [this message]
2012-03-06  9:02                   ` Jeff King
2012-03-06 18:31                   ` 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=87399mazxs.fsf@thomas.inf.ethz.ch \
    --to=trast@inf.ethz.ch \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --cc=rene@habr.de \
    --cc=wmpalmer@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 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.