Home » Mailing list archives » git » 2006 » November » 30

Re: [PATCH 0/2] Making "git commit" to mean "git commit -a".

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
[view in full thread]
From: Carl Worth <cworth@...>
To: Nicolas Pitre <nico@...>
Cc: Linus Torvalds <torvalds@...>, Theodore Tso <tytso@...>, Andreas Ericsson <ae@...>, Johannes Schindelin <Johannes.Schindelin@...>, Junio C Hamano <junkio@...>, <git@...>
Subject: Re: [PATCH 0/2] Making "git commit" to mean "git commit -a".
Date: Thursday, November 30, 2006 - 2:51 pm

On Thu, 30 Nov 2006 10:38:25 -0800, Carl Worth wrote:

By the way, I think I've said all I can in this thread.

If the "create file; git add; edit file; git commit" confusion isn't
blisteringly obvious to the git maintainers then I think I have to
give up here.

And this isn't just CVS-induced brain damage. It's the user being
required to mentally juggle 3 states for the file, (the last
"committed" state, the current "working tree" state, and this
"something else" state). The sequence above, (which is very natural),
exposes this "something else" state that to a new user.

If we imagine a new user as coming, not from cvs, but coming from
no revision control system, then it's less confusing to add one single
new state, (the "last committed" state), in addition to the "working
tree" state the user is familiar with.

Forcing the user to learn two instead of one is just plain harder,
(which is completely separate from git _allowing_ this extra state
once you learn it).

So if git is determined to just be harder to learn this way, then I
don't know what more I can do to help here.

I love git, and I think everyone should use it. I would just like to
help make it a bit easier for people to do that.

-Carl
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
Messages in current thread:
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Junio C Hamano, (Wed Nov 29, 9:03 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Junio C Hamano, (Wed Nov 29, 9:22 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Johannes Schindelin, (Wed Nov 29, 10:11 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Linus Torvalds, (Wed Nov 29, 11:10 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Andreas Ericsson, (Thu Nov 30, 7:09 am)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Linus Torvalds, (Thu Nov 30, 11:58 am)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Theodore Tso, (Thu Nov 30, 12:40 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Linus Torvalds, (Thu Nov 30, 1:13 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Carl Worth, (Thu Nov 30, 2:09 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Linus Torvalds, (Thu Nov 30, 2:33 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Nicolas Pitre, (Thu Nov 30, 1:37 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Carl Worth, (Thu Nov 30, 2:38 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Carl Worth, (Thu Nov 30, 2:51 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Robert Shearman, (Thu Nov 30, 5:33 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Linus Torvalds, (Thu Nov 30, 3:55 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Nicolas Pitre, (Thu Nov 30, 4:47 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Junio C Hamano, (Thu Nov 30, 5:19 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Nicolas Pitre, (Thu Nov 30, 6:21 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Andreas Ericsson, (Fri Dec 1, 4:59 am)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Alan Chandler, (Fri Dec 1, 7:36 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Junio C Hamano, (Thu Nov 30, 7:02 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Nicolas Pitre, (Thu Nov 30, 9:20 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Linus Torvalds, (Thu Nov 30, 7:40 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Junio C Hamano, (Thu Nov 30, 8:24 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Carl Worth, (Thu Nov 30, 8:13 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Linus Torvalds, (Thu Nov 30, 8:21 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Carl Worth, (Thu Nov 30, 9:10 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Linus Torvalds, (Thu Nov 30, 9:32 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Carl Worth, (Thu Nov 30, 10:08 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Linus Torvalds, (Thu Nov 30, 10:44 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Michael K. Edwards, (Thu Nov 30, 11:52 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Carl Worth, (Thu Nov 30, 11:40 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Linus Torvalds, (Thu Nov 30, 5:03 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Andy Parkins, (Fri Dec 1, 4:34 am)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Alan Chandler, (Fri Dec 1, 7:33 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Johannes Schindelin, (Thu Nov 30, 6:27 am)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Steven Grimm, (Wed Nov 29, 9:58 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Junio C Hamano, (Wed Nov 29, 10:12 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Sam Vilain, (Wed Nov 29, 10:04 pm)