Re: git-p4import.py robustness changes
- From
- Scott Lamb <slamb@slamb.org>
- Date
- Jun 2, 2007, 20:41 UTC
- Message-ID
- <0EDF1E14-3682-4B1E-A7D2-F82388F752AA@slamb.org>
- In-Reply-To
- <7vbqg01reo.fsf@assigned-by-dhcp.cox.net>
On May 31, 2007, at 4:53 PM, Junio C Hamano wrote:
Show 5 quoted lines
> Actually, my preference is to have a "patch 0" before all of the > above, that demotes git-p4import to contrib/ hierarchy. Having > no access to p4 managed repositories (nor much inclination to > get one), I can never test nor maintain it myself, so it is just > crazy for me to be the maintainer for it.
Will do. What does that mean for Documentation/git-p4import.txt and the git-p4 rpm (defined in git.spec.in)? Should I move them with it? (Seems nothing else in the main tree references contrib.) If so, maybe I should set up a common "Documentation/asciidoc.mak" or something for building the man/html pages rather than duplicating all that Makefile logic.
-- Scott Lamb <http://www.slamb.org/>