Re: [PATCH v2 10/10] dir: do not use untracked cache ident anymore

On Thu, Dec 17, 2015 at 7:33 PM, Junio C Hamano wrote: > Christian Couder writes: > >> In the "git worktree" documentation there is: >> >> "If you move a linked working tree to another file system, or within a >> file system that does not support

Re: [PATCH v2 10/10] dir: do not use untracked cache ident anymore

On Tue, Dec 15, 2015 at 8:49 PM, Junio C Hamano wrote: > Christian Couder writes: > >> +/* >> + * We used to save the location of the work tree and the kernel version, >> + * but it was not a good idea, so we now just save an empty string. >> + */ >

Re: [PATCH v2 10/10] dir: do not use untracked cache ident anymore

Christian Couder writes: > In the "git worktree" documentation there is: > > "If you move a linked working tree to another file system, or within a > file system that does not support hard links, you need to run at least > one git command inside the linked working

[PATCH v2 10/10] dir: do not use untracked cache ident anymore

A previous commit disabled the check to see if the untracked cache ident field was matching the current environment. So this field is now useless and we can remove some related code. We don't remove the ident field from "struct untracked_cache" as it would break compatibility with old indexes

Re: [PATCH v2 10/10] dir: do not use untracked cache ident anymore

Christian Couder writes: > +/* > + * We used to save the location of the work tree and the kernel version, > + * but it was not a good idea, so we now just save an empty string. > + */ I do agree that storing the kernel version (or hostname or whatever specific to