Thread (1 message) 1 message, 1 author, 2016-06-15
  • (off-list ancestor, not in this archive)
  • Re: Are these bugs? · Jay Soffian <hidden> · 2016-06-15

Re: Are these bugs?

From: Jay Soffian <hidden>
Date: 2016-06-15 22:45:14

Oops, should've gone to list.


---------- Forwarded message ----------
From: Jay Soffian <redacted>
Date: Wed, Aug 27, 2008 at 9:25 PM
Subject: Re: Are these bugs?
To: Junio C Hamano <redacted>


On Wed, Aug 27, 2008 at 7:47 PM, Junio C Hamano [off-list ref] wrote:
"Jay Soffian" [off-list ref] writes:
quoted
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.
quoted
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.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help