From: Jed Brown <jed@59a2•org>
To: Felipe Contreras <felipe.contreras@gmail•com>
Cc: Max Horn <max@quendi•de>, 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 14:01:07 -0500 [thread overview]
Message-ID: <87vc82qfws.fsf@59A2.org> (raw)
In-Reply-To: <CAMP44s3zm+-220Xpqv_=JkJ=g2pS79hUNjacVZ=JejitcG=B8A@mail.gmail.com>
Felipe Contreras <felipe.contreras@gmail•com> writes:
> Where is the evidence? You say remote-hg doesn't work, I say it does,
> the difference is that I have evidence to prove it.
There are many projects that don't do what they claim. I gave remote-hg
a few minutes and moved on since (at the time) it didn't seem
interesting enough to be worth the effort of making proper bug reports.
There's a lot of low-quality code in the world and I'm willing to
tolerate a certain false-positive rate. I apologize for misdiagnosing
your project and I'm happy to believe that you have since fixed the
bugs. I was merely answering you question of why some of us contributed
to gitifyhg in preference to remote-hg.
I see no value in dwelling on the value judgement I made a few months
ago. Additionally, I have almost no use for either project any more.
> remote-hg doesn't fail with the non-fast-forward error, in fact, it
> doesn't fail at all, it pushes correctly, and that's reported as a
> failure.
I don't agree that force-pushing by default is "correct" behavior.
next prev parent reply other threads:[~2013-04-04 19:01 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
2013-04-04 19:45 ` Felipe Contreras
2013-04-04 18:41 ` Felipe Contreras
2013-04-04 19:01 ` Jed Brown [this message]
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=87vc82qfws.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