Re: Issues with higher-order stages in dircache

2005-04-16 Thread Junio C Hamano
> "LT" == Linus Torvalds <[EMAIL PROTECTED]> writes: >> - When merging two trees, i.e. "read-tree -m A B", shouldn't >> we collapse identical stage-1/2 into stage-0? LT> How do you actually intend to merge two trees? How silly of me. *BLUSH* - To unsubscribe from this list: send the line

Re: Issues with higher-order stages in dircache

2005-04-16 Thread Linus Torvalds
On Sat, 16 Apr 2005, Junio C Hamano wrote: > > I am wondering if you have a particular reason not to do the > same for the removing half. No. Except for me being silly. Please just make it so. > Also do you have any comments on this one from the same message? > > * read-tree > >- When

Re: Issues with higher-order stages in dircache

2005-04-16 Thread Junio C Hamano
Linus, earlier I wrote [*R1*]: - An explicit "update-cache [--add] [--remove] path" should be taken as a signal from the user (or Cogito) to tell the dircache layer "the merge is done and here is the result". So just delete higher-order stages for the path and record th

Issues with higher-order stages in dircache

2005-04-16 Thread Junio C Hamano
> "JCH" == Junio C Hamano <[EMAIL PROTECTED]> writes: JCH> So what's next? Here is my current thinking on the impact your higher-order stage dircache entries would have to the rest of the system and how to deal with them. * read-tree - When merging two trees, i.e. "read-tree -m A B", sh