From: Jed Brown <jed@59a2.org>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Jeff King <peff@peff.net>, Max Horn <max@quendi.de>
Subject: Re: [PATCH v2 11/13] remote-hg: force remote push
Date: Thu, 04 Apr 2013 15:48:08 -0500 [thread overview]
Message-ID: <87li8yqayf.fsf@59A2.org> (raw)
In-Reply-To: <CAMP44s16Yt0mL8FKXMVgLBXw7s9_S8hGyS0YNHX7GrsAXYNDfg@mail.gmail.com>
Felipe Contreras <felipe.contreras@gmail.com> writes:
[...]
>> will need to play by those rules.
>
> No, we don't. The fact that you say so doesn't make it so.
Then perhaps we have different goals [1]. I don't know any Git User that
would prefer to have an Hg upstream accessed through remote-hg. We have
to assume that every Git (remote-hg) User is dealing with Hg Team that
is setting the rules, since otherwise Git User would just change the
whole damn project to Git and be done with it. In that sense, it is
inappropriate to do things that are likely to make Hg Team yell at Git
User.
> I create a branch felipec-bookmarks, and I push as many heads as I
> wish. Who will get affected? Nobody.
Every Hg user will see those heads by default every time they run 'hg
log' or 'hg heads'.
> And who says we are committing upstream?
The discussion is moot if you don't want to push your commits upstream.
[1] As I mentioned earlier, I don't need either tool any more.
next prev parent reply other threads:[~2013-04-04 20:48 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 [this message]
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
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=87li8yqayf.fsf@59A2.org \
--to=jed@59a2.org \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=max@quendi.de \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.