mirror of
https://github.com/git/git.git
synced 2024-11-19 00:04:01 +01:00
68faf68938
This merge strategy largely piggy-backs on git-merge-recursive. When merging trees A and B, if B corresponds to a subtree of A, B is first adjusted to match the tree structure of A, instead of reading the trees at the same level. This adjustment is also done to the common ancestor tree. If you are pulling updates from git-gui repository into git.git repository, the root level of the former corresponds to git-gui/ subdirectory of the latter. The tree object of git-gui's toplevel is wrapped in a fake tree object, whose sole entry has name 'git-gui' and records object name of the true tree, before being used by the 3-way merge code. If you are merging the other way, only the git-gui/ subtree of git.git is extracted and merged into git-gui's toplevel. The detection of corresponding subtree is done by comparing the pathnames and types in the toplevel of the tree. Heuristics galore! That's the git way ;-). Signed-off-by: Junio C Hamano <junkio@cox.net>
25 lines
588 B
C
25 lines
588 B
C
#include "cache.h"
|
|
#include "tree.h"
|
|
|
|
int main(int ac, char **av)
|
|
{
|
|
unsigned char hash1[20], hash2[20], shifted[20];
|
|
struct tree *one, *two;
|
|
|
|
if (get_sha1(av[1], hash1))
|
|
die("cannot parse %s as an object name", av[1]);
|
|
if (get_sha1(av[2], hash2))
|
|
die("cannot parse %s as an object name", av[2]);
|
|
one = parse_tree_indirect(hash1);
|
|
if (!one)
|
|
die("not a treeish %s", av[1]);
|
|
two = parse_tree_indirect(hash2);
|
|
if (!two)
|
|
die("not a treeish %s", av[2]);
|
|
|
|
shift_tree(one->object.sha1, two->object.sha1, shifted, -1);
|
|
printf("shifted: %s\n", sha1_to_hex(shifted));
|
|
|
|
exit(0);
|
|
}
|