sharing mq patches with subversion repository

[Ryan]

Thanks Augie, sharing and cloning the mqueue repository itself is what I
was looking for.

I had not considered hgsubversion but I will now that you pointed me at it!

Ryan

On Fri, Dec 2, 2011 at 12:12 PM, Augie Fackler <durin42 at gmail.com> wrote:

> On Fri, Dec 2, 2011 at 1:11 PM, Ryan <rnideffer at gmail.com> wrote:
> > I'm using Mercurial with mqueues on top of an open source subversion
> > repository, which is working great. I'm stumbling though when it comes to
> > sharing the patch repository for other people on my team.
>
> Just OOC: have you considered hgsubversion for pulling the svn history
> in? That obviates the need for some of the .hgignore stuff you mention
> below.
>
> >
> > The way I'm using it locally is to 'hg init' the root svn repository,
> then
> > 'hg init --mq' for the patch repo. I've setup .hgignore to ignore all
> > subversion related files, like .svn directories. This means that when I
> > share the repository, anyone cloning it doesn't get the svn repo and
> can't
> > do the qpop-svn up-qpush flow that I can do locally.
> >
> > What I think I'm shooting for is:
> >
> > 1. clone open source svn repo to his machine
> > 2. clone/pull hg mqueue repository to svn repo
> > 3. qpush all patches
> >
> > And I don't know how to arrive at this. Is this the right workflow? How
> do I
> > expose the patch repository, and properly clone/pull/push with it?
>
> The easiest thing (in my experience) has been to publish the mq
> repository as a normal hg repository (it is one, after all) and just
> have people clone it to .hg/patches themselves.
>
> >
> > Thanks,
> > Ryan
> >
> > _______________________________________________
> > Mercurial mailing list
> > Mercurial at selenic.com
> > http://selenic.com/mailman/listinfo/mercurial
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial/attachments/20111202/e1b2fa53/attachment.html>