dolfin team mailing list archive

["Garth N. Wells" <g.n.wells@xxxxxxxxxx>]

I'm receiving an error when trying to push to the main repository. After
following the procedure in my local repository (edit - commit), I've
tried to push to the fenics.org repository with  

hg push ssh://garth@xxxxxxxxxx/~fenics/hg/projects/dolfin


which gives the error

remote: abort: No such file or
directory: /home/fenics/hg/projects/dolfin/.hg/lock
abort: unexpected response ''!

Any ideas?

Garth

On Thu, 2006-02-02 at 22:55 -0600, Anders Logg wrote:
> Hi everyone!
> 
> The new hg repository is now online. It took a while to convert it but
> everything should be there now. Some sanity checks:
> 
> First changeset (number 0):
> 
> changeset:   0:f89c165cfc8ebce3ace420fdb8242abcd34470f4
> user:        logg
> date:        Fri Sep 13 07:55:37 2002 +0000
> files:       .hgignore AUTHORS COPYING [...]
> description:
> Tailorized "2002-09-13 07:55:37 by logg"
> Initial revision
> 
> Latest changeset before my new test commits (number 1604):
> 
> changeset:   1604:ba21732cdb0078ff3882bb10e60c8c27e7e6b0fa
> user:        johanjan
> date:        Thu Feb  2 16:22:22 2006 +0000
> files:       
> description:
> Tailorized "2006-02-02 16:22:22 by johanjan"
> Build:
> 
> Removed old lib directory.
> 
> Here follows a short list of instructions for DOLFIN maintainers
> (Hoffman, Jansson, Logg, Wells) included here for reference:
> 
> Get an initial copy of the repository by doing
> 
>     hg clone http://www.fenics.org/hg/dolfin
> 
> Then work as usual with
> 
>     hg add file
>     hg remove file
>     hg status file
> 
> When you're done, commit your changes by
> 
>     hg commit
> 
> and write a nice log message (set EDITOR if you don't want to be
> thrown into vi). Note that this only commits the changes to your own
> repository. To get things into the primary repository on fenics.org,
> you must push your changes there, by doing
> 
>     hg push ssh://dolfin@xxxxxxxxxx/~fenics/hg/projects/dolfin
> 
> To make life simpler, you can add the following to the file .hg/hgrc
> at the top level of the repository:
> 
>     [paths]
>     default = ssh://dolfin@xxxxxxxxxx/~fenics/hg/projects/dolfin
> 
> Then you only need to do
> 
>     hg push default
> 
> It is good practice to keep multiple repositories when you work with
> stuff. Keep one of them as your primary repository and push from there
> to fenics.org. Whenever you work with something new, make a clone of
> your primary repository and let the changes propagate through it to
> the primary on fenics.org. Say you want to work with some of the
> demos, then just to place yourself in the directory above your primary
> repository (called dolfin) and do
> 
>     hg clone dolfin dolfin-demo
> 
> Then work in dolfin-demo, commit there and when you're happy, pull the
> changes to dolfin or push from dolfin-demo, that is, either
> 
>     hg pull ../dolfin-demo
> 
> or
> 
>     hg push ../dolfin
> 
> Other things to try:
> 
>     hg log
>     hg log -r tip
>     hg log -vr tip
>     hg log -r 0
>     hg log -r -1
>     hg log -r -5:-1
> 
> etc.
> 
> Oh, and when you update your primary repository from the primary on
> fenics.org, just do
> 
>     hg pull default
> 
> if you have set the path in .hg/hgrc. To actually update your files
> and not only the repository in .hg, you need to do
> 
>     hg update
> 
> If something has changed on your side as well, you need to merge,
> which is done by
> 
>     hg update -m
> 
> Happy hacking
> /Anders
> 
> _______________________________________________
> DOLFIN-dev mailing list
> DOLFIN-dev@xxxxxxxxxx
> http://www.fenics.org/cgi-bin/mailman/listinfo/dolfin-dev