From: Jed Brown <jed@59A2•org>
To: Joachim Schmitz <jojo@schmitz-digital•de>, git@vger•kernel.org
Subject: Re: [PATCH v2 11/13] remote-hg: force remote push
Date: Fri, 05 Apr 2013 07:16:17 -0500 [thread overview]
Message-ID: <876201qijy.fsf@59A2.org> (raw)
In-Reply-To: <kjlr4o$jil$1@ger.gmane.org>
Joachim Schmitz <jojo@schmitz-digital•de> writes:
> 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.
next prev parent reply other threads:[~2013-04-06 16:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 15:30 [PATCH v2 00/13] remote-hg: general updates Felipe Contreras
2013-04-04 15:30 ` [PATCH v2 01/13] remote-hg: trivial cleanups Felipe Contreras
2013-04-04 15:30 ` [PATCH v2 02/13] remote-hg: add missing config variable in doc Felipe Contreras
2013-04-04 15:30 ` [PATCH v2 03/13] remote-hg: properly report errors on bookmark pushes Felipe Contreras
2013-04-04 15:30 ` [PATCH v2 04/13] remote-hg: fix for files with spaces Felipe Contreras
2013-04-04 15:30 ` [PATCH v2 05/13] remote-hg: make sure fake bookmarks are updated Felipe Contreras
2013-04-04 15:30 ` [PATCH v2 06/13] remote-hg: trivial test cleanups Felipe Contreras
2013-04-04 15:30 ` [PATCH v2 07/13] remote-hg: redirect buggy mercurial output Felipe Contreras
2013-04-04 16:40 ` Junio C Hamano
2013-04-04 15:30 ` [PATCH v2 08/13] remote-hg: split bookmark handling Felipe Contreras
2013-04-04 15:30 ` [PATCH v2 09/13] remote-hg: refactor export Felipe Contreras
2013-04-04 15:30 ` [PATCH v2 10/13] remote-hg: update remote bookmarks Felipe Contreras
2013-04-04 15:30 ` [PATCH v2 11/13] remote-hg: force remote push Felipe Contreras
2013-04-04 16:44 ` Junio C Hamano
2013-04-04 18:56 ` Felipe Contreras
2013-04-04 19:06 ` Junio C Hamano
2013-04-04 18:17 ` Jed Brown
2013-04-04 19:13 ` Felipe Contreras
2013-04-04 20:14 ` Jed Brown
2013-04-04 20:35 ` Felipe Contreras
2013-04-04 20:48 ` Jed Brown
2013-04-04 21:34 ` Felipe Contreras
2013-04-04 22:27 ` Jed Brown
2013-04-04 23:06 ` Felipe Contreras
2013-04-05 6:31 ` Joachim Schmitz
2013-04-05 12:16 ` Jed Brown [this message]
2013-04-04 15:30 ` [PATCH v2 12/13] remote-hg: update tags globally Felipe Contreras
2013-04-04 15:30 ` [PATCH v2 13/13] remote-hg: push to the appropriate branch Felipe Contreras
2013-04-04 16:50 ` Junio C Hamano
2013-04-05 9:16 ` Felipe Contreras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=876201qijy.fsf@59A2.org \
--to=jed@59a2$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=jojo@schmitz-digital$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox