[Prbl: pushing does not work]

[Uwe Brauer]

   > This doesn't really have anything to do with hg or hg-git any more -
   > this is purely about how git handles pushes to non-bare repositories,

Yeah I have a bit afraid of it. However I soon might be in a position to
have that scenario. Clone a git repo, clone it via git-hg to a hg, work
and then try to push. (I also have feeling reading previous emails, that
I am not the only once faced  with such a situation)


   > so a discussion on the mercurial-users mailing list is not really the
   > best place for it. However, I'll give it a go:

   > The repository is now in a funny state. The "master" branch has moved
   > on to a new commit, but the working directory is still pointing at an
   > older commit. If you run "git status" in it, I think you'll see some
   > unexpected output (I just tried it, and I got inconsistent results
   > between "git status" and "git diff", so I'm not going to attempt to
   > explain exactly what state it is in, since I don't understand it)

Right.
   > Unless you *really* *really* need to, I would recommend sticking with
   > a *proper* bare repository as your bridge repository. That is, one
   > created with "git clone --bare". Not one where you started with a
   > working copy and then edited the config file.

Ok, thanks very much for clarifying this.
I hope I can then push from that cloned repo to the server.


I think that most likely closes that topic.