Re: Please default to 'commit -a' when no changes were added

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: Please default to 'commit -a' when no changes were added

From: Miles Bader <hidden>
Date: 2016-06-15 22:48:42

Jonathan Nieder [off-list ref] writes:
But dense as I am, I still can’t imagine why

echo '[alias] ci = commit -a' >>$HOME/.gitconfig

wouldn’t be better in every way (especially if Jakub’s
commit.preserveindex is enabled).
If the latter is enabled, you can't use "git add" to add new files,
you'll have to remember to use "add -N" (or add some alias for that
too).

-Miles

-- 
/\ /\
(^.^)
(")")
*This is the cute kitty virus, please copy this into your sig so it can spread.

Re: Please default to 'commit -a' when no changes were added

From: Jonathan Nieder <hidden>
Date: 2016-06-15 22:48:42

Miles Bader wrote:
Jonathan Nieder [off-list ref] writes:
quoted
But dense as I am, I still can’t imagine why

echo '[alias] ci = commit -a' >>$HOME/.gitconfig

wouldn’t be better in every way (especially if Jakub’s
commit.preserveindex is enabled).
If the latter is enabled, you can't use "git add" to add new files,
you'll have to remember to use "add -N" (or add some alias for that
too).
Didn’t he first [1] propose a variant in which using ‘git add -N’ was
not necessary?  The rule was something like this: consider each entry.
If it

 - matches HEAD, or
 - matches the work tree, or
 - is an intent-to-add

then we say it is easily recoverable.  If all index entries are
easily recoverable, then let the commit -a go through.

Jonathan

[1] http://thread.gmane.org/gmane.linux.debian.devel.bugs.general/698001/focus=145662
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help