[PATCH 1/2] Use extended SHA1 syntax in merge-recursive conflicts.
- From
Shawn O. Pearce <spearce@spearce.org>
- Date
- Dec 23, 2006, 08:44 UTC
- Message-ID
- <20061223084400.GA10203@spearce.org>
When we get a line-level conflict in merge-recursive and print out the two sides in the conflict hunk header and footer we should use the standard extended SHA1 syntax to specify the specific blob, as this allows the user to copy and paste the line right into 'git show' to view the complete version.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org> --- merge-recursive.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/merge-recursive.c b/merge-recursive.c index ae7ae4c..abebb95 100644 --- a/merge-recursive.c +++ b/merge-recursive.c @@ -649,8 +649,8 @@ static struct merge_file_info merge_file(struct diff_filespec *o, char *name1, *name2; int merge_status; - name1 = xstrdup(mkpath("%s/%s", branch1, a->path)); - name2 = xstrdup(mkpath("%s/%s", branch2, b->path)); + name1 = xstrdup(mkpath("%s:%s", branch1, a->path)); + name2 = xstrdup(mkpath("%s:%s", branch2, b->path)); fill_mm(o->sha1, &orig); fill_mm(a->sha1, &src1);
-- 1.4.4.3.g87d8