From: Michael Haggerty <mhagger@alum.mit.edu>
To: Felipe Contreras <felipe.contreras@gmail.com>,
git@vger.kernel.org, git-fc@googlegroups.com
Cc: "Richard Hansen" <rhansen@bbn.com>,
"Torsten Bögershaus" <tboegi@web.de>,
"Antoine Pelisse" <apelisse@gmail.com>,
"Christophe Simonis" <christophe@kn.gl>,
"Dusty Phillips" <dusty@linux.ca>, "Jeff King" <peff@peff.net>,
"John Keeping" <john@keeping.me.uk>
Subject: Re: Should git-remote-hg/bzr be part of the core?
Date: Mon, 12 May 2014 15:43:49 +0200 [thread overview]
Message-ID: <5370D015.10300@alum.mit.edu> (raw)
In-Reply-To: <5370beb4b2483_168f13a72fc57@nysa.notmuch>
On 05/12/2014 02:29 PM, Felipe Contreras wrote:
> Michael Haggerty wrote:
> [...]
>> 2. Moving git-remote-hg into the core would require you to continue your
>> presence on the Git mailing list.
>
> That is another red herring. Moving them back to the contrib/ area which
> is what Junio proposed would also require my presence on the list. Is
> that what you want?
No, actually my preference is that git-remote-hg be separated from the
Git project altogether, for the reasons that I stated earlier.
Michael
--
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
next prev parent reply other threads:[~2014-05-12 13:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-11 23:34 Should git-remote-hg/bzr be part of the core? Felipe Contreras
[not found] ` <CA+55aFwf9iAKxbvdPV9Up_T709KwBXJWW4g-F829CRQP4YkivQ@mail.gmail.com>
2014-05-12 7:42 ` Felipe Contreras
2014-05-12 8:12 ` Felipe Contreras
2014-05-12 10:28 ` Stefan Beller
2014-05-12 12:05 ` Felipe Contreras
2014-05-12 9:42 ` Michael Haggerty
2014-05-12 10:35 ` Dennis Kaarsemaker
2014-05-12 10:37 ` Felipe Contreras
2014-05-12 12:05 ` Michael Haggerty
2014-05-12 12:29 ` Felipe Contreras
2014-05-12 13:12 ` David Kastrup
2014-05-12 17:12 ` Felipe Contreras
2014-05-12 13:43 ` Michael Haggerty [this message]
2014-05-12 17:13 ` Felipe Contreras
2014-05-12 11:00 ` David Kastrup
[not found] ` <CAHVLzcmqdkf4fMTok+HsXcDOQ5Oz2QdZti3FuzgBUa2T6AWnfA@mail.gmail.com>
2014-05-12 12:48 ` Felipe Contreras
2014-05-12 13:45 ` Paolo Ciarrocchi
2014-05-12 16:13 ` Stefan Beller
2014-05-12 16:40 ` 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=5370D015.10300@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=apelisse@gmail.com \
--cc=christophe@kn.gl \
--cc=dusty@linux.ca \
--cc=felipe.contreras@gmail.com \
--cc=git-fc@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=john@keeping.me.uk \
--cc=peff@peff.net \
--cc=rhansen@bbn.com \
--cc=tboegi@web.de \
/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;
as well as URLs for NNTP newsgroup(s).