From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Junio C Hamano <gitster@pobox.com>,
Dmitry Potapov <dpotapov@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH] rebase -i: commit when continuing after "edit"
Date: Tue, 25 Sep 2007 16:16:19 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0709251615220.28395@racer.site> (raw)
In-Reply-To: <46F922E0.80504@viscovery.net>
Hi,
On Tue, 25 Sep 2007, Johannes Sixt wrote:
> Johannes Schindelin schrieb:
>
> > On Tue, 25 Sep 2007, Johannes Sixt wrote:
> >
> > > Johannes Schindelin schrieb:
> > >
> > > > On Tue, 25 Sep 2007, Johannes Sixt wrote:
> > > > > How about:
> > > > >
> > > > > eval "$author_script"
> > > > > GIT_AUTHOR_NAME="$GIT_AUTHOR_NAME" \
> > > > > GIT_AUTHOR_EMAIL="$GIT_AUTHOR_EMAIL" \
> > > > > GIT_AUTHOR_DATE="$GIT_AUTHOR_DATE" \
> > > > > $USE_OUTPUT git commit -F "$MSG" $EDIT_COMMIT
> > > > >
> > > > > and if you dislike that, put the two questionable lines in
> > > > > parenthesis.
> > > >
> > > > That looks ugly. I'd rather have something like
> > > >
> > > > eval "$USE_OUTPUT $author_script git commit -F \"$MSG\" $EDIT_COMMIT"
> > > >
> > > > but I'm not quite certain if that is enough, what with the funny
> > > > characters people put into path names these days ($MSG points to
> > > > "$DOTEST"/message).
> > >
> > > I, too, find it ugly, but I think it's the most readable way to do
> > > it. Your version is certainly underquoted.
> > >
> > > I poked around a bit, but one major obstacle is that the assignments
> > > in $author_script are on separate lines, which you would have to
> > > splice into a single line before you can insert them in the eval.
> >
> > But is your version not underquoted, too? For example, if the author
> > name is, say 'Johannes "Dscho" Schindelin', would your version still
> > get the \" in the name?
>
> No, it's not underquoted; yes, it would still get the \" in the name.
> The shell parses the assignments
>
> GIT_AUTHOR_NAME="$GIT_AUTHOR_NAME"
>
> only once; it does not parse it again after the dq'd string was expanded.
Ah, okay. I'll go with your version then.
Ciao,
Dscho
next prev parent reply other threads:[~2007-09-25 15:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-23 22:45 git-rebase--interactive needs a better message Dmitry Potapov
2007-09-23 23:56 ` Johannes Schindelin
2007-09-24 0:29 ` [PATCH] rebase -i: commit when continuing after "edit" Johannes Schindelin
2007-09-24 9:11 ` Dmitry Potapov
2007-09-25 5:37 ` Junio C Hamano
2007-09-25 12:32 ` Johannes Schindelin
2007-09-25 13:26 ` Johannes Sixt
2007-09-25 13:50 ` Johannes Schindelin
2007-09-25 14:17 ` Johannes Sixt
2007-09-25 14:31 ` Johannes Schindelin
2007-09-25 15:01 ` Johannes Sixt
2007-09-25 15:16 ` Johannes Schindelin [this message]
2007-09-25 14:46 ` David Kastrup
2007-09-25 15:54 ` Johannes Sixt
2007-09-25 16:04 ` David Kastrup
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0709251615220.28395@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=dpotapov@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
/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://80x24.org/mirrors/git.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).