Scott Lamb <slamb@xxxxxxxxx> writes: > On May 31, 2007, at 4:53 PM, Junio C Hamano wrote: > >> 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. A much more preferable alternative is for you to say "Hey, don't say you want to demote it. I'll keep it maintained, I regularly use p4 and have a strong incentive to keep it working". Then we do not have to do the "patch 0" ;-) - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
