dolfin team mailing list archive

[Anders Logg <logg@xxxxxxxxx>]

Applied, thanks.

I use

    hg incoming -v -p <bundlefile>

to see what's inside the bundle.

You probably need to sit in a repository that does not contain the
changeset of the bundle to see what's inside.

/Anders


On Mon, Jan 22, 2007 at 06:59:12PM -0300, Pablo De Napoli wrote:
> Ok here is my bundle...
> (but how may I see what it is inside?)
> 
> On 1/22/07, Anders Logg <logg@xxxxxxxxx> wrote:
> 
>     Yes, the hg bundle file is binary but you don't need to read it.
>     I just do
> 
>         hg unbundle bundle.hg
> 
>     or more likely I'll start by doing
> 
>         hg incoming -v -p bundle.hg
> 
>     to see what's in the bundle.
> 
>     If you create a bundle, it's easier to track who made what (hg
>     annotate -u).
> 
>     If you don't mind, please make a bundle instead of a patch.
> 
>     /Anders
> 
> 
>     On Mon, Jan 22, 2007 at 02:54:12PM -0300, Pablo De Napoli wrote:
>     > Thank you for incorporating my patch.
>     > When checking how the manual looks like now, I realized that I've made
>     > a small typo
>     >
>     >
>     > So, here I send you another patch with a correction to this (and a
>     > little improvement to the
>     > writting)
>     >
>     > (when it says "if configure can not find if" it should said "if
>     > configure cannot find it"
>     > but I think that it is better English to say "if configure fails to find
>     > it")
>     >
>     > I've created by hg export (I think that you can apply it by using hg
>     import)
>     >
>     > (Sorry that I cannot publish my repository right now, since I don't
>     > have a permanet server that I can use for this)
>     >
>     > I'm new also to mercurial and I'm trying find the best way to use it.
>     > I see that hg bundle has a problem: it generates a binary file that I
>     > don't how to read
>     > (where as hg export generates a standard patch that is human readable)
>     >
>     > thanks, and sorry for this inconvenience...
>     >
>     > Pablo
> 
>     > # HG changeset patch
>     > # User pdenapo@xxxxxxxxx
>     > # Date 1169487725 10800
>     > # Node ID b5870dbcdab984b9e6668c8def7db48d785bafe7
>     > # Parent  e095ae338f4bdf3e16ec0996cb0520fdb9403422
>     > Fix a typo (and improve the writting)
>     >
>     > diff -r e095ae338f4b -r b5870dbcdab9 doc/manual/chapters/quickstart.tex
>     > --- a/doc/manual/chapters/quickstart.tex      Mon Jan 22 17:34:20 2007
>     +0100
>     > +++ b/doc/manual/chapters/quickstart.tex      Mon Jan 22 14:42:05 2007
>     -0300
>     > @@ -338,7 +338,7 @@ as the file \texttt{dolfin-poisson}. Not
>     >  as the file \texttt{dolfin-poisson}. Note that this requires
>     >  \texttt{pkg-config} to be able to find the file \texttt{dolfin.pc}.
>     >  (That file is generated by the \texttt{configure} script, during the
>     > -configuration of \dolfin{}. If \texttt{pkg-config} can not find if, you
>     need
>     > +configuration of \dolfin{}. If \texttt{pkg-config} fails to find it, you
>     need
>     >  to add the directory containing it to your \texttt{PKG\_CONFIG\_PATH}
>     >  environment variable.)
>     >
> 
>     > _______________________________________________
>     > DOLFIN-dev mailing list
>     > DOLFIN-dev@xxxxxxxxxx
>     > http://www.fenics.org/mailman/listinfo/dolfin-dev
> 
>     _______________________________________________
>     DOLFIN-dev mailing list
>     DOLFIN-dev@xxxxxxxxxx
>     http://www.fenics.org/mailman/listinfo/dolfin-dev
> 
> 


> _______________________________________________
> DOLFIN-dev mailing list
> DOLFIN-dev@xxxxxxxxxx
> http://www.fenics.org/mailman/listinfo/dolfin-dev