From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: しらいしななこ <nanako3@bluebottle.com>
Cc: GIT <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH (3rd try)] Add git-stash script
Date: Sat, 30 Jun 2007 16:41:11 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0706301641000.4438@racer.site> (raw)
In-Reply-To: <200706300539.l5U5dHLh003989@mi1.bluebottle.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1104 bytes --]
Hi,
On Sat, 30 Jun 2007, しらいしななこ wrote:
> diff --git a/git-stash.sh b/git-stash.sh
> [...]
> + printf >&2 'Saved WIP on %s\n' "$msg"
You have an awful lot of printfs in the code. Why not just use echos?
> +list_stash () {
> + git-log --pretty=oneline -g "$@" $ref_stash |
Wouldn't you want "--default $ref_stash" here?
> +apply_stash () {
> + git-diff-files --quiet ||
> + die 'Cannot restore on top of a dirty state'
You meant "no_changes", right? I think you miss changes in the index
otherwise.
> + git-diff --cached --name-only --diff-filter=A $c_tree >"$a" &&
> + git-read-tree --reset $c_tree &&
> + git-update-index --add --stdin <"$a" ||
> + die "Cannot unstage modified files"
Isn't there a way to avoid the temporary file here?
> + else
> + # Merge conflict
> + exit 1
Since $? is already != 0, and it might tell the savvy user what kind of
error merge-recursive returned, why not use "exit", which is equivalent to
"exit $?"?
> + set x -n 10
> + shift
This is more elegantly written as "set -- -n 10", or in our context even
"set -- -10".
Ciao,
Dscho
next prev parent reply other threads:[~2007-06-30 15:41 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-30 1:29 [PATCH (2nd try)] Add git-stash script しらいしななこ
2007-06-30 2:05 ` Johannes Schindelin
2007-06-30 5:37 ` [PATCH (3rd " しらいしななこ
2007-06-30 6:12 ` Jeff King
2007-06-30 6:25 ` Junio C Hamano
2007-06-30 15:41 ` Johannes Schindelin [this message]
2007-06-30 17:19 ` Junio C Hamano
2007-06-30 23:27 ` しらいしななこ
2007-06-30 15:44 ` [PATCH] Add a manual page for git-stash Johannes Schindelin
2007-06-30 16:38 ` Frank Lichtenheld
2007-06-30 17:48 ` Johannes Schindelin
2007-06-30 18:45 ` Frank Lichtenheld
2007-06-30 17:44 ` Junio C Hamano
2007-06-30 17:56 ` Johannes Schindelin
2007-06-30 18:13 ` Junio C Hamano
2007-06-30 18:44 ` Johannes Schindelin
2007-07-01 5:26 ` [PATCH] Document git-stash しらいしななこ
2007-07-01 6:48 ` Junio C Hamano
2007-07-01 8:07 ` Jeff King
2007-07-01 8:38 ` Junio C Hamano
2007-07-01 9:06 ` しらいしななこ
[not found] ` <200707010910.l619A23c027837@mi0.bluebottle.com>
2007-07-01 9:19 ` Jeff King
2007-07-01 21:39 ` Junio C Hamano
2007-07-02 4:08 ` Jeff King
2007-07-01 21:54 ` Junio C Hamano
2007-07-01 22:57 ` Johannes Schindelin
2007-07-02 4:10 ` Jeff King
2007-07-02 10:33 ` Johannes Schindelin
2007-07-02 10:44 ` [PATCH] git-stash: Make "save" the default operation again Johannes Schindelin
2007-07-02 11:00 ` Jeff King
2007-07-02 11:15 ` Johannes Schindelin
2007-07-02 23:11 ` Junio C Hamano
2007-07-01 5:20 ` [PATCH] Add a manual page for git-stash Junio C Hamano
2007-06-30 16:06 ` [PATCH] Add tests " Johannes Schindelin
[not found] <200706302327.l5UNRMtc027974@mi0.bluebottle.com>
2007-07-01 0:16 ` [PATCH (3rd try)] Add git-stash script Johannes Schindelin
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=Pine.LNX.4.64.0706301641000.4438@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nanako3@bluebottle.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).