git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2 11/13] remote-hg: force remote push

From
Jed Brown <jed@59a2.org>
Date
Apr 5, 2013, 12:16 UTC
Message-ID
<876201qijy.fsf@59A2.org>
In-Reply-To
<kjlr4o$jil$1@ger.gmane.org>
Joachim Schmitz <jojo@schmitz-digital.de> writes:
Show 6 quoted lines
> Jed Brown wrote:
>>
>> Really?  If there is no Hg Team, why bother with an Hg upstream?
>
> Huh? the counterpart of "every user" wpuld be "some users" and not "no user" 
> or "no HG team", isn't it?

I'm not sure what you're getting at here, but the whole premise of a two-way git-remote-X is that the users of git-remote-X have less influence in the project than the users of X have in the project. Usually this means that the project workflow is whatever the X users find comfortable rather than whatever git-remote-X users prefer.

If you are the sole publisher to a remote repository, sending pull requests to upstream, and if they are comfortable with pulling bookmarks (much more likely if they use a pull-request model rather than a shared repo), then force-pushing by default is more reasonable. An imperfect analogy is Git's push.default=simple, which is more friendly to beginners and to those sharing a remote.

Previous: Joachim SchmitzNext: Felipe Contreras
Message 26 of 30 in “remote-hg: general updates”
  1. 00/13 remote-hg: general updatesFelipe Contreras, Apr 4, 2013
  2. 01/13 remote-hg: trivial cleanupsFelipe Contreras, Apr 4, 2013
  3. 02/13 remote-hg: add missing config variable in docFelipe Contreras, Apr 4, 2013
  4. 03/13 remote-hg: properly report errors on bookmark pushesFelipe Contreras, Apr 4, 2013
  5. 04/13 remote-hg: fix for files with spacesFelipe Contreras, Apr 4, 2013
  6. 05/13 remote-hg: make sure fake bookmarks are updatedFelipe Contreras, Apr 4, 2013
  7. 06/13 remote-hg: trivial test cleanupsFelipe Contreras, Apr 4, 2013
  8. 07/13 remote-hg: redirect buggy mercurial outputFelipe Contreras, Apr 4, 2013
  9. Junio C HamanoApr 4, 2013
  10. 08/13 remote-hg: split bookmark handlingFelipe Contreras, Apr 4, 2013
  11. 09/13 remote-hg: refactor exportFelipe Contreras, Apr 4, 2013
  12. 10/13 remote-hg: update remote bookmarksFelipe Contreras, Apr 4, 2013
  13. 11/13 remote-hg: force remote pushFelipe Contreras, Apr 4, 2013
  14. Junio C HamanoApr 4, 2013
  15. Felipe ContrerasApr 4, 2013
  16. Junio C HamanoApr 4, 2013
  17. Jed BrownApr 4, 2013
  18. Felipe ContrerasApr 4, 2013
  19. Jed BrownApr 4, 2013
  20. Felipe ContrerasApr 4, 2013
  21. Jed BrownApr 4, 2013
  22. Felipe ContrerasApr 4, 2013
  23. Jed BrownApr 4, 2013
  24. Felipe ContrerasApr 4, 2013
  25. Joachim SchmitzApr 5, 2013
  26. Jed BrownApr 5, 2013
  27. 12/13 remote-hg: update tags globallyFelipe Contreras, Apr 4, 2013
  28. 13/13 remote-hg: push to the appropriate branchFelipe Contreras, Apr 4, 2013
  29. Junio C HamanoApr 4, 2013
  30. Felipe ContrerasApr 5, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.