From: Ted Zlatanov <tzz@lifelogs.com>
To: git@vger.kernel.org
Cc: Felipe Contreras <felipe.contreras@gmail.com>
Subject: Re: [PATCH v2 00/18] remote-bzr: massive changes
Date: Fri, 03 Jan 2014 15:17:14 -0500 [thread overview]
Message-ID: <8761q0hlbp.fsf@flea.lifelogs.com> (raw)
In-Reply-To: 7vehdq5yvc.fsf@alter.siamese.dyndns.org
On Wed, 01 May 2013 11:38:47 -0700 Junio C Hamano <gitster@pobox.com> wrote:
JCH> Felipe Contreras <felipe.contreras@gmail.com> writes:
>> On Wed, May 1, 2013 at 11:39 AM, Junio C Hamano <gitster@pobox.com> wrote:
>>> Felipe Contreras <felipe.contreras@gmail.com> writes:
>>>
>>>>> So let's go ahead and apply these directly on top of 'master', once
>>>>> we hear from Emacs folks and they are happy with it. I'll queue it
>>>>> on 'pu' so that I do not have to go back to the list archive when it
>>>>> happens.
>>>>
>>>> I already heard that everything seems to be working correctly, except
>>>> one feature, the biggest change, which I screwed up with a one-liner
>>>> commit. That's why I added a test. Anyway, I've fixed it in my github
>>>> branch and in this patch series, and I've told them to try the fix.
>>>
>>> Let us know when they make progress on that front.
>>>
>>> If Emacs decides to switch to Git and decides to use this version of
>>> remote-bzr for their conversion, or at least a nontrivial group of
>>> developers favor to do so, without seeing concrete technical points
>>> that say remote-bzr is not yet ready (e.g. "the conversion is still
>>> wrong and X, Y and Z needs to be fixed"), that would be a very
>>> welcome solid vote of confidence in favor of us going ahead with
>>> this.
>>
>> Seems unlikely for political reasons (isn't it always for GNU?), since
>> RMS is heavily involved in the decision.
JCH> I am very aware of that discussion (and the original one when they
JCH> decided to use bzr). That is exactly why I said "at least ... favor
JCH> to do so".
FYI, in case you're not aware, there's a pretty strong feeling on
emacs-devel that the switch to Git will happen and RMS is not opposed.
I don't know if they'll use remote-bzr, though. It's more likely
they'll use one of the already-existing mirrors and sync it up, based on
the feedback so far. It's a good time to bring remote-bzr up on
emacs-devel if you want it to be considered.
HTH
Ted
prev parent reply other threads:[~2014-01-03 20:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 1:09 [PATCH v2 00/18] remote-bzr: massive changes Felipe Contreras
2013-05-01 1:09 ` [PATCH v2 01/18] remote-bzr: cleanup CustomTree Felipe Contreras
2013-05-01 1:09 ` [PATCH v2 02/18] remote-bzr: delay blob fetching until the very end Felipe Contreras
2013-05-01 1:09 ` [PATCH v2 03/18] remote-bzr: fix order of locking in CustomTree Felipe Contreras
2013-05-01 1:09 ` [PATCH v2 04/18] remote-bzr: always try to update the worktree Felipe Contreras
2013-05-01 1:09 ` [PATCH v2 05/18] remote-bzr: add support to push merges Felipe Contreras
2013-05-01 1:09 ` [PATCH v2 06/18] remote-bzr: fixes for branch diverge Felipe Contreras
2013-05-01 1:09 ` [PATCH v2 07/18] remote-bzr: fix partially pushed merge Felipe Contreras
2013-05-01 1:10 ` [PATCH v2 08/18] remote-bzr: use branch variable when appropriate Felipe Contreras
2013-05-01 1:10 ` [PATCH v2 09/18] remote-bzr: add support for bzr repos Felipe Contreras
2013-05-01 1:10 ` [PATCH v2 10/18] remote-bzr: fix branch names Felipe Contreras
2013-05-01 1:10 ` [PATCH v2 11/18] remote-bzr: add support for shared repo Felipe Contreras
2013-05-01 1:10 ` [PATCH v2 12/18] remote-bzr: improve author sanitazion Felipe Contreras
2013-05-01 1:10 ` [PATCH v2 13/18] remote-bzr: add custom method to find branches Felipe Contreras
2013-05-01 1:10 ` [PATCH v2 14/18] remote-bzr: add option to specify branches Felipe Contreras
2013-05-01 1:10 ` [PATCH v2 15/18] remote-bzr: improve progress reporting Felipe Contreras
2013-05-01 1:10 ` [PATCH v2 16/18] remote-bzr: iterate revisions properly Felipe Contreras
2013-05-01 1:10 ` [PATCH v2 17/18] remote-bzr: delay peer branch usage Felipe Contreras
2013-05-01 1:10 ` [PATCH v2 18/18] remote-bzr: access branches only when needed Felipe Contreras
2013-05-01 5:44 ` [PATCH v2 00/18] remote-bzr: massive changes Junio C Hamano
2013-05-01 6:36 ` Felipe Contreras
2013-05-01 16:39 ` Junio C Hamano
2013-05-01 18:35 ` Felipe Contreras
2013-05-01 18:38 ` Junio C Hamano
2014-01-03 20:17 ` Ted Zlatanov [this message]
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=8761q0hlbp.fsf@flea.lifelogs.com \
--to=tzz@lifelogs.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
/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.