From: David Kastrup <dak@gnu.org>
To: Michael Haggerty <mhagger@alum.mit.edu>
Cc: "Felipe Contreras" <felipe.contreras@gmail.com>,
git@vger.kernel.org, git-fc@googlegroups.com,
"Richard Hansen" <rhansen@bbn.com>,
"Torsten Bögershausen" <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 13:00:20 +0200 [thread overview]
Message-ID: <87wqdruurf.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <53709788.2050201@alum.mit.edu> (Michael Haggerty's message of "Mon, 12 May 2014 11:42:32 +0200")
Michael Haggerty <mhagger@alum.mit.edu> writes:
> This email is written in sorrow, not in anger. Felipe, you seem to
> have so much potential. If you would put as much effort in conducting
> social interactions as you do in coding, [...]
I think that's where you are mistaken. We are not talking about a lack
of effort here. It is just not spent conducively.
--
David Kastrup
next prev parent reply other threads:[~2014-05-12 11:01 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
2014-05-12 17:13 ` Felipe Contreras
2014-05-12 11:00 ` David Kastrup [this message]
[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=87wqdruurf.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--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=mhagger@alum.mit.edu \
--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 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.