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]
To: Michael K. Edwards <medwards.linux@...>
Cc: Jakub Narebski <jnareb@...>, <git@...>
Date: Thursday, November 30, 2006 - 5:50 pm

On Thu, 30 Nov 2006 13:41:37 -0800, "Michael K. Edwards" wrote:

I actually thought of that. But compared to "refresh" it sounds more
like something that suggests marking a file path rather than copying
contents, so our dark lord might not approve of the wrong ideas it
might allow to persist in brain-damaged heads.

It is nice and short, which is a bonus though.

-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"., Johannes Schindelin, (Thu Nov 30, 6:25 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Josef Weidendorfer, (Thu Nov 30, 6:07 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Michael K. Edwards, (Thu Nov 30, 5:41 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Carl Worth, (Thu Nov 30, 5:50 pm)
Re: [PATCH 0/2] Making "git commit" to mean "git commit -a"., Johannes Schindelin, (Thu Nov 30, 6:26 pm)