From: Bert Wesarg <bert.wesarg@googlemail.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: martin f krafft <madduck@debian.org>, Petr Baudis <pasky@suse.cz>,
git@vger.kernel.org, Adam Simpkins <adam@adamsimpkins.net>
Subject: Re: [TopGit PATCH] tg-graph: print dependency graph like git log --graph
Date: Wed, 20 May 2009 08:07:05 +0200 [thread overview]
Message-ID: <36ca99e90905192307m67c11b83y7af44ccdb48f43e0@mail.gmail.com> (raw)
In-Reply-To: <20090519184402.GA27352@pengutronix.de>
2009/5/19 Uwe Kleine-König <u.kleine-koenig@pengutronix.de>:
> Hi Bert,
>
> On Tue, May 19, 2009 at 03:33:16PM +0200, Bert Wesarg wrote:
>> On Tue, May 19, 2009 at 15:28, martin f krafft <madduck@debian.org> wrote:
>> > also sprach Bert Wesarg <bert.wesarg@googlemail.com> [2009.05.19.0744 +0200]:
>> >> @@ -62,12 +70,33 @@ git for-each-ref refs/top-bases |
>> >> continue
>> >> fi
>> >> if [ -n "$graphviz" ]; then
>> >> +
>> >> + if [ -n "$graphviz_verbose" ]; then
>> >> + type="header"
>> >> + lines=0
>> >> + echo "\t\"$name\" ["
>> >
>> > You need to pass -e to echo for it to honour escape sequences. That
>> > should solve Michael's problem. Alternatively, just use ^I directly.
>> Correct, thanks. Looks like a feature from bash or dash to honor
>> escape sequences without -e'
> quoting
> http://www.gnu.org/software/hello/manual/autoconf/Limitations-of-Builtins.html#Limitations-of-Builtins:
>
> It is not possible to use `echo' portably unless both options
> and escape sequences are omitted.
>
> ... use printf instead.
Thank you for this valuable link, Will switch to printf.
Bert
>
> Best regards
> Uwe
prev parent reply other threads:[~2009-05-20 6:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 5:44 [TopGit PATCH] tg-graph: print dependency graph like git log --graph Bert Wesarg
2009-05-19 10:27 ` Michael Radziej
2009-05-19 10:37 ` Bert Wesarg
2009-05-19 11:08 ` Michael Radziej
2009-05-19 11:47 ` Bert Wesarg
2009-05-19 11:48 ` Bert Wesarg
2009-05-19 13:10 ` Michael Radziej
2009-05-19 13:32 ` Bert Wesarg
2009-05-19 13:39 ` Michael Radziej
2009-05-19 13:51 ` Bert Wesarg
2009-05-19 14:09 ` Michael Radziej
2009-05-19 14:14 ` Bert Wesarg
2009-05-19 14:32 ` Bert Wesarg
2009-05-19 16:45 ` Bert Wesarg
2009-05-19 13:28 ` martin f krafft
2009-05-19 13:33 ` Bert Wesarg
2009-05-19 18:44 ` Uwe Kleine-König
2009-05-20 6:07 ` Bert Wesarg [this message]
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=36ca99e90905192307m67c11b83y7af44ccdb48f43e0@mail.gmail.com \
--to=bert.wesarg@googlemail.com \
--cc=adam@adamsimpkins.net \
--cc=git@vger.kernel.org \
--cc=madduck@debian.org \
--cc=pasky@suse.cz \
--cc=u.kleine-koenig@pengutronix.de \
/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).