From: Jing Xue <jingxue@digizenstudio.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git <git@vger.kernel.org>
Subject: Re: [PATCH] Replace the cryptic messages from "git stash show".
Date: Sat, 15 Dec 2007 12:08:05 -0500 [thread overview]
Message-ID: <20071215170805.GA16589@fawkes> (raw)
In-Reply-To: <7v63z0o59r.fsf@gitster.siamese.dyndns.org>
On Fri, Dec 14, 2007 at 10:12:32PM -0800, Junio C Hamano wrote:
>
> Is it just me who feels that the added code is much worse than the
> disease?
I wouldn't be surprised. Shell scripting is by no means my long suit -
in fact, I am not even sure it's "a suit" of mine at all. I didn't like
what I saw and basically had two options:
1. Send a "this is not user friendly" rant and get beaten up by "why
don't you even try?"
2. Try and hack together something, submit it, and keep fixing it until
it makes it - and learn something in the process, maybe at the price of
being mocked at, but I don't care.
In particular, as far as I _could_ see, there are probably at least one
place I'm doing something potentially absurd, but couldn't figure out
anything better:
I'm not sure how to test if there is a stash name specified, so I
tried:
test "$flags" = "$@"
but then it breaks when $@ has a space in it. Hence the pointless
assignment to $arguments first.
The reason I removed the --default option to rev-parse is that it
doesn't distinguish between no stash name or an invalid one.
I'm sure there are other things people don't like - some because my
shell scripting sucks, some others maybe because of style differences.
At any rate, I'm open to criticism. So bring it on. 8-)
--
Jing Xue
prev parent reply other threads:[~2007-12-15 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-14 1:28 [PATCH] Makes 'git-stash show' stay quiet when there are no stashes Jing Xue
2007-12-14 1:34 ` Junio C Hamano
2007-12-15 5:14 ` [PATCH] Replace the cryptic messages from "git stash show" Jing Xue
2007-12-15 6:12 ` Junio C Hamano
2007-12-15 17:08 ` Jing Xue [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=20071215170805.GA16589@fawkes \
--to=jingxue@digizenstudio.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).