Thread (13 messages) flat view 13 messages, 5 authors, 2016-06-15

Re: Merge git-gui into 1.5.0 ?

From: Michael S. Tsirkin <hidden>
Date: 2016-06-15 22:42:53

Quoting Shawn O. Pearce [off-list ref]:
Subject: Re: Merge git-gui into 1.5.0 ?

Johannes Schindelin [off-list ref] wrote:
quoted
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.
Actually, -p<n> option to git-am is also useful for piping
patches to git-am directly from mail: sometimes people would generate
a patch by hand and this results in patches incorrect -p level.
	
-- 
MST
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help