Hi,
On Sun, 11 Feb 2007, Shawn O. Pearce wrote:
Unlike Kay, I'm not looking to merge git-gui into git.git to abandon it.
That's great!
It may be saner for all involved if that development happens in the
git-gui.git repository, with drops made to git.git by way of merging the
"subproject" every so often.
Fully agree.
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?
Ciao,
Dscho