[PATCH] remote-hg: getbundle changed in mercurial 3.0

2014-05-13 Thread William Giokas
In mercurial 3.0, getbundle was moved to the changegroup module, and gained a new argument. Due to this we cannot simply start using getbundle(...) imported from either one unconditionally, as that would cause errors in mercurial 3.0 without changing the syntax, and errors in mercurial 3.0 if we

Re: [PATCH] remote-hg: getbundle changed in mercurial 3.0

2014-05-13 Thread Junio C Hamano
William Giokas 1007...@gmail.com writes: In mercurial 3.0, getbundle was moved to the changegroup module, and gained a new argument. Due to this we cannot simply start using getbundle(...) imported from either one unconditionally, as that would cause errors in mercurial 3.0 without changing

Re: [PATCH] remote-hg: getbundle changed in mercurial 3.0

2014-05-13 Thread Felipe Contreras
Junio C Hamano wrote: The way I envision the longer term shape of git-remote-hg.py in the contrib/ is either one of these two: (1) manage it just like contrib/hooks/multimail/, keeping a reasonably fresh and known-to-be-good snapshot, while making it clear that my tree is not