On Sat, 16 Apr 2005, Junio C Hamano wrote:
> LT> NOTE NOTE NOTE! I could make "read-tree" do some of these nontrivial
> LT> merges, but I ended up deciding that only the "matches in all three
> LT> states" thing collapses by default.
> * Understood and agreed.
Having slept on it, I think I'll merge all the trivial cases that don't
involve a file going away or being added. Ie if the file is in all three
trees, but it's the same in two of them, we know what to do.
That way we'll leave thigns where the tree itself changed (files added or
removed at any point) and/or cases where you actually need a 3-way merge.
> The userland merge policies need ways to extract the stage
> information and manipulate them. Am I correct to say that you
> mean by "ls-files -l" the extracting part?
No, I meant "show-files", since we need to show the index, not a tree (no
valid tree can ever have the "modes" information, since (a) it doesn't
have the space for it anyway and (b) we refuse to write out a dirty index
> LT> I should make "ls-files" have a "-l" format, which shows the
> LT> index and the mode for each file too.
> You probably meant "ls-tree". You used the word "mode" but it
> already shows the mode so I take it to mean "stage". Perhaps
> something like this?
> $ ls-tree -l -r 49c200191ba2e3cd61978672a59c90e392f54b8b
> 100644 blob fe2a4177a760fd110e78788734f167bd633be8de COPYING
> 100644 blob b39b4ea37586693dd707d1d0750a9b580350ec50:1
> 100644 blob b39b4ea37586693dd707d1d0750a9b580350ec50:2
> 100664 blob eeed997e557fb079f38961354473113ca0d0b115:3
Apart from the fact that it would be
since there are no tree objects that can have anything but fully merged
> Assuming that you would be working on that, I'd like to take the
> dircache manipulation part. Let's think about the minimally
> necessary set of operations:
> * The merge policy decides to take one of the existing stage.
> In this case we need a way to register a known mode/sha1 at a
> path. We already have this as "update-cache --cacheinfo".
> We just need to make sure that when "update-cache" puts
> things at stage 0 it clears other stages as well.
> * The merge policy comes up with a desired blob somewhere on
> the filesystem (perhaps by running an external merge
> program). It wants to register it as the result of the
> We could do this today by first storing the "desired blob"
> in a temporary file somewhere in the path the dircache
> controls, "update-cache --add" the temporary file, ls-tree to
> find its mode/sha1, "update-cache --remove" the temporary
> file and finally "update-cache --cacheinfo" the mode/sha1.
> This is workable but clumsy. How about:
> $ update-cache --graft [--add] desired-blob path
> to say "I want to register mode/sha1 from desired-blob, which
> may not be of verify_path() satisfying name, at path in the
> * The merge policy decides to delete the path.
> We could do this today by first stashing away the file at the
> path if it exists, "update-cache --remove" it, and restore
> if necessary. This is again workable but clumsy. How about:
> $ update-cache --force-remove path
> to mean "I want to remove the path from dircache even though
> it may exist in my working tree"?
> Am I on the right track?
> You might want to go even lower level by letting them say
> something like:
> * update-cache --register-stage mode sha1 stage path
> Registers the mode/sha1 at stage for path. Does not look at
> the working tree. stage is [0-3]
I'd prefer not. I'd avoid playing games with the stages at any other level
than the "full tree" level until we show a real need for it.
Let's go with the known-needed minimal cases that are high-level enough to
make the scripting simple, and see if there is any reason to ever touch
the tree any other way.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html