From: Junio C Hamano <gitster@pobox.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>,
Ramkumar Ramachandra <artagnon@gmail.com>
Subject: Re: [PATCH v3 0/9] remote-helpers: fixes and cleanups
Date: Fri, 26 Apr 2013 15:23:11 -0700 [thread overview]
Message-ID: <7vsj2due28.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <7vwqrpuedv.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Fri, 26 Apr 2013 15:16:12 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Felipe Contreras <felipe.contreras@gmail.com> writes:
>
>> Updated the commit messages, so we say Bazaar instead of Mercurial, and stuff.
>>
>> Here's a bunch of cleanups mostly to synchronize remote-bzr and remote-hg.
>
> Thanks. Will queue on 'pu' without looking.
Actually, I was going to merge fc/remote-hg and fc/remote-bzr down
to master anyway, so I'll just apply them directly on 'master'.
By the way, I personally do not think the quality of the changes to
remote-bzr matters all that much at this point in its history. It's
not like millions of people use it heavily from the v1.8.2 release.
A huge patch series from its original author and nobody else, either
reviewed or unreviwed, would not hurt them more than the one in the
v1.8.2 version anyway. And it is also not like bzr-to-git population
will grow significantly in the future to require us to pile a lot of
features on remote-bzr that makes the maintenance burden of it
becomes an issue.
Am I underestimating the pain of potentially breaking existing
remote-bzr userbase?
next prev parent reply other threads:[~2013-04-26 22:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 21:12 [PATCH v3 0/9] remote-helpers: fixes and cleanups Felipe Contreras
2013-04-26 21:12 ` [PATCH v3 1/9] remote-helpers: trivial cleanups Felipe Contreras
2013-04-26 21:12 ` [PATCH v3 2/9] remote-hg: remove extra check Felipe Contreras
2013-04-26 21:12 ` [PATCH v3 3/9] remote-bzr: fix bad state issue Felipe Contreras
2013-04-26 21:12 ` [PATCH v3 4/9] remote-bzr: add support to push URLs Felipe Contreras
2013-04-26 21:12 ` [PATCH v3 5/9] remote-hg: use hashlib instead of hg sha1 util Felipe Contreras
2013-04-26 21:12 ` [PATCH v3 6/9] remote-bzr: store converted URL Felipe Contreras
2013-04-26 21:12 ` [PATCH v3 7/9] remote-bzr: tell bazaar to be quiet Felipe Contreras
2013-04-26 21:12 ` [PATCH v3 8/9] remote-bzr: strip extra newline Felipe Contreras
2013-04-26 21:12 ` [PATCH v3 9/9] remote-bzr: use proper push method Felipe Contreras
2013-04-26 22:16 ` [PATCH v3 0/9] remote-helpers: fixes and cleanups Junio C Hamano
2013-04-26 22:23 ` Junio C Hamano [this message]
2013-04-26 22:40 ` Felipe Contreras
2013-04-26 23:04 ` Junio C Hamano
2013-04-27 2:56 ` Ramkumar Ramachandra
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=7vsj2due28.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=artagnon@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox