Johannes Schindelin [off-list ref] wrote:
quoted
It may make patching slightly more interesting though, as some
users new to git-gui development may generate a patch in git.git
(using a/git-gui/git-gui.sh as the path) which then would not apply
as-is to the master git-gui development tree.
In this case, a "-p <n>" option to git-am would make sense, no?
Are you saying we just suddenly found a vaild use for a flag which
nobody (except the original submitter) thought was useful? ;-)
Yes, clearly a -p<n> on git-am would solve the problem quite nicely.
--
Shawn.