Isn't -C HEAD redundant with --amend's default behavior?
The idea of a shortcut for diff --cached is interesting. Do you use it before committing, or for other purposes? I always commit -v to show that diff in the log editor.
--amend's default behavior is to run the editor so you can edit the log message. `-C HEAD` skips that and reuses the message without change. Very recent git (1.7.9) added `--no-edit`, which does the same thing.
I'm not sure how to characterize my use of git-ix. Right now all I can say is that I use it when I want to see what is staged! I probably use it after a complicated git-add -p to make sure I didn't stage anything I didn't mean to. I will try to notice what else I am doing next time I use it, and let you know.
(no subject)
Date: 2012-02-18 02:05 (UTC)(no subject)
Date: 2012-02-18 02:24 (UTC)I'd put a
set -e
or&&
s in there, just in case.(no subject)
Date: 2012-02-18 03:04 (UTC)(no subject)
Date: 2012-02-20 14:12 (UTC)s = status -s
I also like:
ix = diff --cached
cp = cherry-pick
fixup = commit --amend -C HEAD
(no subject)
Date: 2012-02-20 14:18 (UTC)-C HEAD
redundant with--amend
's default behavior?The idea of a shortcut for
diff --cached
is interesting. Do you use it before committing, or for other purposes? I alwayscommit -v
to show that diff in the log editor.(no subject)
Date: 2012-02-20 15:36 (UTC)I'm not sure how to characterize my use of git-ix. Right now all I can say is that I use it when I want to see what is staged! I probably use it after a complicated git-add -p to make sure I didn't stage anything I didn't mean to. I will try to notice what else I am doing next time I use it, and let you know.
(no subject)
Date: 2012-02-21 14:36 (UTC)w = whatchanged