Re: Are these bugs?

From: Jay Soffian <jaysoffian@gmail.com>
Date: Aug 28, 2008, 01:26 UTC
Message-ID: <76718490808271826y4ff8bc37ub046de3be5111eb5@mail.gmail.com>
In-Reply-To: <76718490808271825j68ac6abch406a8e12b5849b1a@mail.gmail.com>

Oops, should've gone to list.

---------- Forwarded message ----------
From: Jay Soffian <jaysoffian@gmail.com>
Date: Wed, Aug 27, 2008 at 9:25 PM
Subject: Re: Are these bugs?
To: Junio C Hamano <gitster@pobox.com>

On Wed, Aug 27, 2008 at 7:47 PM, Junio C Hamano <gitster@pobox.com> wrote:

Show 6 quoted lines

> "Jay Soffian" <jaysoffian@gmail.com> writes:
>
>> I understand why "git reset" failed, but at best the error message is
>> confusing to a new user.
>
> This is in "patches welcome" category.

Okay, good to know. I'll add it to me "things to do in spare time" list.

Show 11 quoted lines

>> 2. "git add --ignore-errors" doesn't work with ignored files:
>>
>> $ git add --ignore-errors foo bar
>
> The option, IIRC, is more about filesystem errors (failure to read), not
> about safety against user errors (specifying otherwise ignored paths).
>
> If you are automating something that uses xargs to drive addition to the
> index, and the feeder to xargs knows better than .gitignore files, then
> probably your script should be using '-f' unconditionally.  So I do not
> see why you would think #2 could be a bug.

Well that's just it, my feeder to xargs did *not* know better than the .gitignore files so -f would have done the exact opposite of what I wanted. The git-add man page's description of --ignore-errors agrees with what you write above though, so I'll just move along on this one.

j.