If a file does not contain newline in the last line, and the file has
changed somewhere
in other branch, and the newline has not been not added in that
change, when I cherry-pick the commit, the commit does contain the
newline in the last line. This sometimes leads to conflict and in
general looks unexpected.

Such files are not uncommon nowadays and however bad it is, I think
merging and cherry-picking should try to keep is as long as the
newline is not added in some of the changes. Are there any option to
preserve the absence of the closing newline? Or maybe the commands
should preserve it unconditionally?

To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to