On Sun, Jan 17, 2010 at 11:14:58PM +0100, Bert Huijben wrote: > If you want to fix this behavior, you would have to check the exact status > information to determine that you are exactly in the replacement without > history case. > > This is one of the hardest statuses to detect with WC-NG (which was easy as > entries), but luckily we don't need it any more for the processing in the > three tree storage model with a SHA-1 based pristine store. There we store a > hash in BASE and in WORKING.
So... you're saying we should wait with fixing this until the wc-ng pristine store has been implemented? Stefan
