(off-list ancestor, not in this archive)
Re: How to selectively recreate merge state? · Junio C Hamano <hidden> · 2016-06-15
[PATCH 0/3] Update advice in commit/status output · Junio C Hamano <hidden> · 2016-06-15
[PATCH 1/3] commit/status: check $GIT_DIR/MERGE_HEAD only once · Junio C Hamano <hidden> · 2016-06-15
[PATCH 2/3] commit/status: "git add <path>" is not necessarily how to resolve · Junio C Hamano <hidden> · 2016-06-15
[PATCH 3/3] status/commit: do not suggest "reset HEAD <path>" while merging · Junio C Hamano <hidden> · 2016-06-15
Re: [PATCH 2/3] commit/status: "git add <path>" is not necessarily how to resolve · Jeff King <hidden> · 2016-06-15
Re: [PATCH 2/3] commit/status: "git add <path>" is not necessarily how to resolve · Nanako Shiraishi <hidden> · 2016-06-15
Re: [PATCH 0/3] Update advice in commit/status output · Sverre Rabbelier <hidden> · 2016-06-15
Re: [PATCH 0/3] Update advice in commit/status output · Jay Soffian <hidden> · 2016-06-15

Re: [PATCH 0/3] Update advice in commit/status output

From: Sverre Rabbelier <hidden>
Date: 2016-06-15 22:47:54

Possibly related (same subject, not in this thread)

2016-06-15 · Re: [PATCH 0/3] Update advice in commit/status output · Junio C Hamano <hidden>

Heya,

On Sat, Dec 12, 2009 at 10:02, Junio C Hamano [off-list ref] wrote:

In neither case, "git reset HEAD <path>" is absolutely a wrong thing to do
while merging.

From the patches I'm guessing you mean "In either case" instead?

-- 
Cheers,

Sverre Rabbelier