Elazar Leibovich writes:
> ignore unused information, such as commit
> 2cb45e95438c113871fbbea5b4f629f9463034e7
> which ignores st_dev, because it doesn't actually matter, or
I do not think it ignores because "it doesn't matter". st_dev is
known not to be stable (e.g. across reboots and reconne
On 12/07/2017 05:31 PM, Junio C Hamano wrote:
Correct. fakeroot would report that the files that are actually
owned by the user who is running fakeroot are owned by root; the
cached stat information in the index would be "corrected" to say
that they are owned by root. So once the index is refr
Elazar Leibovich writes:
> We noticed some unexpected behavior of git, when running git commands under
> fakeroot, and then running another command without fakeroot.
>
> When running, e.g., git status, or git describe --dirty, git can
> update the index file.
Correct. fakeroot would report that
Hi,
We noticed some unexpected behavior of git, when running git commands under
fakeroot, and then running another command without fakeroot.
When running, e.g., git status, or git describe --dirty, git can
update the index file.
This can happen inadvertently by, e.g., running the make install p
4 matches
Mail list logo
