hg-git: push -d default seems not to work.

Dr Rainer Woitok rainer.woitok at gmail.com
Thu May 4 14:51:11 UTC 2017


Uwe,

On Wednesday, 2017-05-03 21:27:03 +0000, you wrote:

> ...
> Because they want clean 'clutter free' commits and they don't want
> branches to be pushed. I could use rebase with the collapse option,
> but then I will not really understand the graph in the future.

I already said it once,  Mercurial Queues  is exactly what you need: you
develop a patch  using as many changesets in your  local "patches/" sub-
repository as you need with all the try and error involved.  When you're
satisfied with the patch there are two choices:

   * Regardless of  how many changesets  you produced in your "patches/"
     sub-repository,  the patch itself is in a single "diff" format file
     in this sub-repository which you can directly send upstream.

   * Alternatively you can  "hg qfinish" your patch,  meaning it will be
     applied to your  local main repository  AS A SINGLE  NEW CHANGESET,
     giving you an opportunity  to provide a commit message containing a
     reasonable patch description.   This new changeset  can then easily
     be pushed.

Sincerely,
  Rainer



More information about the Mercurial mailing list