Kristian Amlie <kristian.amlie@xxxxxxxxx> writes:
> ext Junio C Hamano wrote:
> ...
>> For example, you may notice that, after making a clean checkout, one path
>> has a wrong attribute assigned to it, and may try to correct it. But how?
>>
>> $ edit .gitattributes ;# mark foo.dat as binary
>> $ rm foo.dat
>> $ git checkout foo.dat ;# make sure the new settings is correct???
>
> As far as I can see, this works without any modifications to the patch.
> Is that maybe because git_attr_set_direction() is not called if you use
> that form of checkout?
But that in itself can be seen as a bug, right? In another use case,
suppose you botched your .gitattributes in HEAD version and noticed that
foo.dat is checked out with a wrong attribute. You try to fix it like
this:
$ git reset HEAD^ .gitattributes
$ rm foo.dat
$ git checkout foo.dat
If you do not flip the direction, the one from the work tree is used which
is not what you want. If you do, then you break the other use case.
Either way, you cannot win.
In any case, I think I already queued the patch in 'pu' but without
documentation updates nor additional tests, so no need to include the
patch itself when you send in an update.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
