Vinay Sajip <vinay_sa...@yahoo.co.uk> added the comment: > Éric Araujo <mer...@netwok.org> added the comment: > > My GSoC student found the reason of the problem: When we put a full > Mercurial >URI like http://blah#branch, the patch generation fails, we have to go to the >edit repo form (on another page) and fill in separately the base URI and the >branch. > > It would be easier if both fields (repo and branch) were on the same page >(i.e. the issue page), and/or the repo field parsed URIs like blah#branch.
I had the impression from reading some posts about Mercurial integration (I think by MvL, but I may be misremembering that) that the system was already parsing branches from the blah#branch form - since then, that's how I've been adding repo URLs to the tracker. _______________________________________________________ PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za> <http://psf.upfronthosting.co.za/roundup/meta/issue405> _______________________________________________________ _______________________________________________ Tracker-discuss mailing list Tracker-discuss@python.org http://mail.python.org/mailman/listinfo/tracker-discuss
