> Yup, it uses "git-ls-files --others", which considers that
Patch looks good here! Thanks!
% git status
#
# Updated but not checked in:
# (will commit)
#
# modified: file1
# deleted: file2
#
#
# Changed but not updated:
# (use git-update-index to mark for commit)
#
# unmerged: file3
#
But I have a lingering question. Same script as before.
% git diff file3
* Unmerged path file3
% cat file3
Stuff for a conflict.
Why didn't file3 show something like:
% cat file3
<<<<<
Stuff for a conflict.
=====
Another file!
>>>>>
That is, after the merge, file3 appears to have simply kept
the contents of the current, master branch. Why wasn't the
dev branch represented here?
I _almost_ think I get it, and then *poof*...
Thanks,
jdl
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author] Next message: [thread] [date] [author]
Messages in current thread:
Re: Expected Behavior?, Jon Loeliger, (Mon Nov 7, 11:43 pm)