From: Junio C Hamano <gitster@pobox•com>
To: David Kastrup <dak@gnu•org>
Cc: Philippe Vaucher <philippe.vaucher@gmail•com>,
"git\@vger.kernel.org" <git@vger•kernel.org>
Subject: Re: [PATCH 0/4] remote-hg: more improvements
Date: Wed, 14 May 2014 15:24:51 -0700 [thread overview]
Message-ID: <xmqq61l8hubw.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <87mweku2pt.fsf@fencepost.gnu.org> (David Kastrup's message of "Wed, 14 May 2014 11:30:38 +0200")
David Kastrup <dak@gnu•org> writes:
> Philippe Vaucher <philippe.vaucher@gmail•com> writes:
>
>> Thanks for the explanation. I think it underlines well the A)
>> technical issues (quality commits) and the B) social issues (ability
>> to communicate in a friendly way & respond constructively), which we
>> discovered are both *essential* for contributing to git.
>
> I'm not entirely convinced of that: there is something akin to drop-dead
> gorgeous code: code that is so well done that it would not matter with
> regard to its maintenance whether or not its author dropped dead because
> it's both done well as well as documented in a manner where the original
> author could not offer significant additional help.
I would have to say that you are living in a fantasy land. During
the entire life of Git, I do not think I ever saw such a code that
is perfect from the get-go and did not require any maintenance to
adjust to the changing time.
next prev parent reply other threads:[~2014-05-14 22:25 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-04 2:16 [PATCH 0/4] remote-hg: more improvements Felipe Contreras
2014-05-04 2:16 ` [PATCH 1/4] remote-hg: add more tests Felipe Contreras
2014-05-04 9:40 ` Eric Sunshine
2014-05-04 2:16 ` [PATCH 2/4] t: remote-hg: add file operation tests Felipe Contreras
2014-05-04 2:16 ` [PATCH 3/4] t: remote-hg: trivial cleanups and fixes Felipe Contreras
2014-05-04 2:16 ` [PATCH 4/4] remote-hg: add support for hg v3.0 Felipe Contreras
2014-05-07 18:12 ` [PATCH 0/4] remote-hg: more improvements Junio C Hamano
2014-05-07 19:01 ` Felipe Contreras
2014-05-07 20:28 ` Junio C Hamano
2014-05-07 20:37 ` Felipe Contreras
2014-05-07 23:59 ` Junio C Hamano
2014-05-08 1:09 ` Felipe Contreras
2014-05-08 1:34 ` James Denholm
2014-05-08 20:15 ` Felipe Contreras
2014-05-11 19:33 ` Philippe Vaucher
2014-05-12 12:19 ` Philippe Vaucher
2014-05-12 19:50 ` Junio C Hamano
2014-05-12 20:19 ` Felipe Contreras
2014-05-12 20:40 ` Junio C Hamano
2014-05-12 22:21 ` Felipe Contreras
2014-05-14 9:12 ` Philippe Vaucher
2014-05-14 9:30 ` David Kastrup
2014-05-14 9:36 ` Philippe Vaucher
2014-05-14 9:55 ` David Kastrup
2014-05-14 12:11 ` Philippe Vaucher
2014-05-14 12:50 ` David Kastrup
2014-05-14 13:13 ` Philippe Vaucher
2014-05-14 13:51 ` David Kastrup
2014-05-14 16:06 ` Philippe Vaucher
2014-05-14 20:19 ` Felipe Contreras
2014-05-14 20:58 ` David Kastrup
2014-05-14 21:39 ` Felipe Contreras
2014-05-14 22:12 ` David Kastrup
2014-05-14 22:30 ` Felipe Contreras
2014-05-15 6:03 ` David Kastrup
2014-05-14 22:24 ` Junio C Hamano [this message]
2014-05-14 22:30 ` David Kastrup
2014-05-14 22:34 ` Junio C Hamano
2014-05-08 0:00 ` Junio C Hamano
2014-05-08 1:36 ` Felipe Contreras
2014-05-08 18:36 ` Junio C Hamano
2014-05-08 19:56 ` Felipe Contreras
2014-05-08 22:22 ` Junio C Hamano
2014-05-08 22:42 ` Felipe Contreras
2014-05-08 23:06 ` Junio C Hamano
2014-05-08 23:39 ` Felipe Contreras
2014-05-09 0:23 ` Felipe Contreras
2014-05-09 17:16 ` Junio C Hamano
2014-05-09 17:59 ` 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=xmqq61l8hubw.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=dak@gnu$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=philippe.vaucher@gmail$(echo .)com \
/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