Thread (1 message) 1 message, 1 author, 2016-06-15

Re: [RFC/PATCH 0/2] New 'stage' command

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:46:33

Felipe Contreras [off-list ref] writes:
On Sun, Apr 5, 2009 at 10:02 PM, Junio C Hamano [off-list ref] wrote:
quoted
Felipe Contreras [off-list ref] writes:
quoted
This is the list of actions I've mapped:

 * add: git stage = git stage add (git add)
 * rm: (git rm --cached)
 * diff: (git rm --cached)
 * import: stage all files; modified, deleted, new
 * ls: (git ls-files --stage)
I do not think these are good ideas at all, as it just spreads more
confusion, not less.
Do you agree that there's already a lot of confusion? (stage, cache,
index, etc.)

And do you agree that many git newbies don't use the stage? Actually
most of them don't even know what it is, and just do "git commit -a".

If so, how do you think these issues should be handled?
Perhaps not spreading "stage" even wider?  That is the newest confusing
term that caused the most harm.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help