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: Jakub Narebski <jnareb@...>
To: <git@...>
Subject: Re: [PATCH 0/2] Making "git commit" to mean "git commit -a".
Date: Thursday, November 30, 2006 - 2:47 pm

Carl Worth wrote:


while in git "git add" means "I want to add this file" (in the state
it is now) and not "I want the system to 'know' about this file".
And "commit" mean "Please commit the current 'known' state of all
files (or/and the current state of files I mention here on the
comand line)".

Yes, this is different than what other SCM do...
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git


-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
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"., Jakub Narebski, (Thu Nov 30, 2:47 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Carl Worth, (Thu Nov 30, 3:04 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Andreas Ericsson, (Fri Dec 1, 4:44 am)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Han-Wen Nienhuys, (Fri Dec 1, 5:31 am)