From: Daniel Barkalow <barkalow@iabervon.org>
Date: Mon, 19 May 2008 19:32:14 GMT
Subject: Re: Re* [PATCH] "not uptodate" changed to "has local changes"
Message-ID: <alpine.LNX.1.00.0805191523060.19665@iabervon.org>
In-Reply-To: <7vzlqm89tj.fsf@gitster.siamese.dyndns.org>

On Mon, 19 May 2008, Junio C Hamano wrote:

> Wincent Colaiuta <win@wincent.com> writes:
> 
> > El 17/5/2008, a las 21:03, Junio C Hamano escribió:
> >> +	/* not_uptodate_file */
> >> +	"Entry '%s' not uptodate. Cannot merge.",
> >
> >
> > Minor nit, "uptodate" is not a word. Should be either "up-to-date" or
> > "up to date"; most dictionaries list both.
> 
> Why does *everybody* keep missing the whole point of this patch?

That section needs a comment stating that it's the scripting API, not just 
an arbitrary set of messages. For that matter, maybe those shouldn't be 
the default set, but an alternate set used (as a group) by plumbing 
programs; I don't think it's too likely that there will be a whole lot of 
new plumbing programs, and new porcelain programs that don't specify 
anything probably ought to get something more generic.

	-Daniel
*This .sig left intentionally blank*