From: Jed Brown <jed@59A2•org>
To: Felipe Contreras <felipe.contreras@gmail•com>, Max Horn <max@quendi•de>
Cc: John Keeping <john@keeping•me.uk>,
git@vger•kernel.org, Junio C Hamano <gitster@pobox•com>,
Jeff King <peff@peff•net>
Subject: Re: [PATCH 00/13] remote-hg: general updates
Date: Thu, 04 Apr 2013 13:11:38 -0500 [thread overview]
Message-ID: <871uaqrwrp.fsf@59A2.org> (raw)
In-Reply-To: <CAMP44s3DETFBhexPhEEMP1TZGNrc91266=t16H2t_+VB_4V38w@mail.gmail.com>
Felipe Contreras <felipe.contreras@gmail•com> writes:
> I still don't see any good reason why a user might prefer gitifyhg,
> even more importantly, why gitifyhg developers don't contribute to
> remote-hg.
Felipe, I read your blog announcement [1] and got the impression that
remote-hg was ready for daily use. When I tried to use it, it promptly
crashed in my first attempt to clone. I opened up the script, fixed
whatever caused the first stack trace and made it slighly further before
it crashed again. I couldn't tell what was expected to work, what was a
known problem, and what was an unknown problem. Many things clearly did
not work and it had the look of a project that was not getting active
use. I felt that it was wildly oversold and that putting it into
git.git was premature.
I tried gitifyhg later and it basically worked out of the box. All
known problems were marked by 'xfail' test cases. At that time,
remote-hg failed almost all the gitifyhg tests. I contributed a few
things to gitifyhg, including the notes support (essential when talking
via email with other people using Mercurial). Since then, the last
major project I'm involved with has switched to Git so I rarely need
gitifyhg or remote-hg any more.
FWIW, I also thought Dusty's original announcement oversold gitifyhg, but
it was closer to the truth and upon cloning the repo, it was more clear
what didn't work. The early history of gitifyhg is quite chaotic and I
didn't realize at first how much code turned out to be borrowed from
remote-hg. I don't know whether you wrote all of remote-hg or borrowed
significant parts from elsewhere. To be honest, I don't really care,
but it would be good to coalesce around one project that is well-tested
and has documented behavior so that the poor folks stuck with Mercurial
upstreams can have dependable behavior.
[1] http://felipec.wordpress.com/2012/11/13/git-remote-hg-bzr-2/
next prev parent reply other threads:[~2013-04-04 18:12 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 [this message]
2013-04-04 18:34 ` Junio C Hamano
2013-04-04 19:23 ` Jed Brown
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=871uaqrwrp.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