From: Jed Brown <jed@59A2•org>
To: Junio C Hamano <gitster@pobox•com>
Cc: Felipe Contreras <felipe.contreras@gmail•com>,
Max Horn <max@quendi•de>, John Keeping <john@keeping•me.uk>,
git@vger•kernel.org, Jeff King <peff@peff•net>
Subject: Re: [PATCH 00/13] remote-hg: general updates
Date: Thu, 04 Apr 2013 14:23:01 -0500 [thread overview]
Message-ID: <87sj36qewa.fsf@59A2.org> (raw)
In-Reply-To: <7vip42i1r0.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox•com> writes:
> So,... is there a concrete proposal for _me_ to act on? Do you want
> to see contrib/remtote-hg out of my tree, and have it compete with
> the other one (which also shouldn't be in my tree) in the open?
Three months ago, I would have said yes. Now I don't know. It looks
like remote-hg has improved and is perhaps stable enough to remain, but
I think it needs a much more complete test suite [1] and some visible
documentation about its mapping semantics. There is no way a change
like "force-push by default" should come without the user knowing about
it. (I don't think force-push should become the default in any case,
but something is wrong with the process if there isn't a good way to
communicate such behavioral turmoil.) A separate project making its own
releases has a more visible place to indicate such changes.
[1] Max and I have no love for the "obfuscated shell scripting" in
gitifyhg's 'py.test'- and 'sh'-based test suite, and we expressed early
on that we'd rather have git-style shell scripts. So while porting
these would provide a good start, they can't just be dropped into
git.git.
next prev parent reply other threads:[~2013-04-04 19:23 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 19:02 [PATCH 00/13] remote-hg: general updates Felipe Contreras
2013-04-02 19:02 ` [PATCH 01/13] remote-hg: trivial cleanups Felipe Contreras
2013-04-02 19:02 ` [PATCH 02/13] remote-hg: add missing config variable in doc Felipe Contreras
2013-04-02 19:02 ` [PATCH 03/13] remote-hg: properly report errors on bookmark pushes Felipe Contreras
2013-04-02 19:02 ` [PATCH 04/13] remote-hg: fix for files with spaces Felipe Contreras
2013-04-02 19:02 ` [PATCH 05/13] remote-hg: make sure fake bookmarks are updated Felipe Contreras
2013-04-02 19:02 ` [PATCH 06/13] remote-hg: trivial test cleanups Felipe Contreras
2013-04-02 19:02 ` [PATCH 07/13] remote-hg: redirect buggy mercurial output Felipe Contreras
2013-04-02 19:58 ` Junio C Hamano
2013-04-02 20:22 ` Felipe Contreras
2013-04-02 20:36 ` Junio C Hamano
2013-04-04 15:07 ` Felipe Contreras
2013-04-04 16:29 ` Junio C Hamano
2013-04-02 19:02 ` [PATCH 08/13] remote-hg: split bookmark handling Felipe Contreras
2013-04-02 19:02 ` [PATCH 09/13] remote-hg: refactor export Felipe Contreras
2013-04-02 19:02 ` [PATCH 10/13] remote-hg: update remote bookmarks Felipe Contreras
2013-04-02 19:03 ` [PATCH 11/13] remote-hg: force remote push Felipe Contreras
2013-04-02 19:03 ` [PATCH 12/13] remote-hg: don't update bookmarks unnecessarily Felipe Contreras
2013-04-02 19:03 ` [PATCH 13/13] remote-hg: update tags globally Felipe Contreras
2013-04-02 19:55 ` [PATCH 00/13] remote-hg: general updates Junio C Hamano
2013-04-02 20:27 ` Felipe Contreras
2013-04-02 20:47 ` Junio C Hamano
2013-04-02 20:09 ` John Keeping
2013-04-02 22:23 ` Max Horn
2013-04-03 1:31 ` Felipe Contreras
2013-04-03 9:20 ` Felipe Contreras
2013-04-03 9:23 ` Antoine Pelisse
2013-04-05 8:26 ` Felipe Contreras
2013-04-04 0:25 ` Max Horn
2013-04-04 6:42 ` Felipe Contreras
2013-04-04 6:46 ` Felipe Contreras
2013-04-04 9:07 ` Max Horn
2013-04-04 9:35 ` Felipe Contreras
2013-04-05 22:30 ` Max Horn
2013-04-06 0:45 ` Felipe Contreras
2013-04-06 14:09 ` Philip Oakley
2013-04-06 16:01 ` Felipe Contreras
2013-04-06 1:28 ` Junio C Hamano
2013-04-06 1:47 ` Felipe Contreras
2013-04-07 3:32 ` Junio C Hamano
2013-04-04 18:11 ` Jed Brown
2013-04-04 18:34 ` Junio C Hamano
2013-04-04 19:23 ` Jed Brown [this message]
2013-04-04 19:45 ` Felipe Contreras
2013-04-04 18:41 ` Felipe Contreras
2013-04-04 19:01 ` Jed Brown
2013-04-04 16:14 ` Felipe Contreras
2013-04-05 11:45 ` 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=87sj36qewa.fsf@59A2.org \
--to=jed@59a2$(echo .)org \
--cc=felipe.contreras@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=john@keeping$(echo .)me.uk \
--cc=max@quendi$(echo .)de \
--cc=peff@peff$(echo .)net \
/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