From: Jonathan Nieder <jrnieder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
Jeff King <peff@peff.net>,
git@vger.kernel.org, Sverre Rabbelier <srabbelier@gmail.com>
Subject: Re: [PATCH 2/2] transport-helper: update remote helper namespace
Date: Mon, 15 Apr 2013 17:56:58 -0700 [thread overview]
Message-ID: <20130416005658.GA3262@elie.Belkin> (raw)
In-Reply-To: <7vobdh54uh.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> Just rerolling with what _you_ think is an appropriate level of
> explanation (either or both in log and in-code) and see what happens
> would probably be the best way to proceed, I think, at this
> point. Either you hear "It still is wrong and too sketchy", "Yeah,
> thinking about it again, this is sufficient" from others. Or a
> silent, which I am inclined to take as much closer to the latter
> after all the discussion.
For future reference, sometimes when I am silent it does not mean
agreement but means "I am fed up and don't consider it to be worth the
drain on my energy to deal with this mess." Which is pretty close to
"let's move on; this is sufficient", yes.
Thanks,
Jonathan
prev parent reply other threads:[~2013-04-16 0:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 0:07 [PATCH 0/2] transport-helper: general fixes Felipe Contreras
2013-04-11 0:07 ` [PATCH 1/2] transport-helper: improve push messages Felipe Contreras
2013-04-11 3:41 ` Jeff King
2013-04-11 0:07 ` [PATCH 2/2] transport-helper: update remote helper namespace Felipe Contreras
2013-04-11 4:33 ` Jeff King
2013-04-11 4:53 ` Felipe Contreras
2013-04-11 5:05 ` Jeff King
2013-04-11 5:18 ` Felipe Contreras
2013-04-13 6:00 ` Felipe Contreras
2013-04-14 5:13 ` Junio C Hamano
2013-04-14 15:42 ` Felipe Contreras
2013-04-14 18:45 ` Junio C Hamano
2013-04-14 19:00 ` Jeff King
2013-04-16 0:56 ` Jonathan Nieder [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=20130416005658.GA3262@elie.Belkin \
--to=jrnieder@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=srabbelier@gmail.com \
/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).