From: Nicolas Pitre <nico@cam.org>
Date: Thu, 22 Feb 2007 21:09:55 GMT
Subject: Re: [PATCH] Fix 'git commit -a' in a newly initialized repository
Message-ID: <alpine.LRH.0.82.0702221605080.27932@xanadu.home>
In-Reply-To: <Pine.LNX.4.63.0702222157000.22628@wbgn013.biozentrum.uni-wuerzburg.de>

On Thu, 22 Feb 2007, Johannes Schindelin wrote:

> Hi,
> 
> On Thu, 22 Feb 2007, Nicolas Pitre wrote:
> 
> > On Thu, 22 Feb 2007, Johannes Schindelin wrote:
> > 
> > > On Thu, 22 Feb 2007, Fredrik Kuivinen wrote:
> > > 
> > > > +		die 'nothing to commit (use "git add file1 file2" to include for commit)'
> > > 
> > > Would it not make more sense to tell the user about "git add ."?
> > 
> > Isn't what the patch does?  IMHO it looks just like the empty commit 
> > message which is good.
> 
> I wanted to get at the "." thing. You know, when I start a project with 
> git, there are usually some files there already. Provided I have a 
> .gitignore there, I can just say "git add ." and be done.
> 
> But maybe that is _not_ common practice?

Well... If you're that acquainted with GIT to perform the above, I'm 
sure a message like "use "git add file1 file2" to include for commit" 
won't leave you puzzled.  ;-)


Nicolas