Partial Archive

Nick Peeples nick.peeples at gmail.com
Wed Jan 2 11:55:26 CST 2008


Ok, here is what I have come up with for anyone else looking for the same thing:

Assuming rev is calculated from last-build + 1

hg export -a 55: > build.patch

Move build.patch to production folders and using
http://gnuwin32.sourceforge.net/packages/patch.htm (thanks Mark)

patch -i build.patch -p 1 --binary

This seems to handle just about everything, deletions, binary changes,
etc. Anything seem wrong with this?

P.S. - when I was going through this, I assumed that

hg export -o file.patch rev:tip

would generate the same results as

hg export rev:tip > file.patch

but it doesn't. It seems that using the -o flag, at least on Windows
XP with hg version feac5b0bf9ba+win32extras will only output the last
revision in the array. Is this a bug? or did I miss something about
the -o flag?

-Nick

On Dec 31, 2007 9:42 PM, Mark A. Flacy <mflacy at verizon.net> wrote:
>
> On 2007.12.31 13:03, Nick Peeples wrote:
> > I have read up on some of the discussion about the partial clone, but
> > I don't think that will quite accomplish what I am looking at doing.
> >
> > I'm looking at bundle, trying to see if this would work, but tying the
> > production stuff to a mercurial repository is not ideal.
> >
> > What I need is a way to create an archive of only files changed
> > between revisions. This would allow me to push changes to production
> > sites, but I don't necessarily want those production sites under the
> > same source control as development. I'm thinking that if I could just
> > get a list of files changed between two repositories, then I could use
> > archive with the -I param, but I'm struggling with that too.
> >
> > Does this make sense, something silly to do?
>
> What's wrong with export from the repository and using patch to apply
> the changes at the target?
>
> --
> Mark A. Flacy
>
>
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
>


More information about the Mercurial mailing list