Am 8/30/2013 0:46, schrieb Dave Williams:
> +-i, --ignore-index::
> + Don't look in the index when undertaking the checks. This means
> + the results deviate from those seen by git add and git status
> + but is useful when understanding why a path became tracked by
> + e.g. git add
Duy Nguyen writes:
> On Fri, Aug 30, 2013 at 5:46 AM, Dave Williams
> wrote:
>> check-ignore currently shows how .gitignore rules would treat untracked
>> paths. Tracked paths do not generate useful output. This prevents
>> debugging of why a path became tracked unexpectedly unless that path is
Dave Williams writes:
> check-ignore currently shows how .gitignore rules would treat untracked
> paths. Tracked paths do not generate useful output. This prevents
> debugging of why a path became tracked unexpectedly unless that path is
> first removed from the index with git rm --cached
>
> T
On Fri, Aug 30, 2013 at 5:46 AM, Dave Williams
wrote:
> check-ignore currently shows how .gitignore rules would treat untracked
> paths. Tracked paths do not generate useful output. This prevents
> debugging of why a path became tracked unexpectedly unless that path is
> first removed from the in
On Thu, Aug 29, 2013 at 11:46:52PM +0100, Dave Williams wrote:
> check-ignore currently shows how .gitignore rules would treat untracked
> paths. Tracked paths do not generate useful output. This prevents
> debugging of why a path became tracked unexpectedly unless that path is
> first removed fro
check-ignore currently shows how .gitignore rules would treat untracked
paths. Tracked paths do not generate useful output. This prevents
debugging of why a path became tracked unexpectedly unless that path is
first removed from the index with git rm --cached
This option (-i, --ignore-index) sim
6 matches
Mail list logo
