From: "Philip Oakley" <philipoakley@iee.org>
To: "Felipe Contreras" <felipe.contreras@gmail.com>,
"Alex Davidson" <descenterace@hotmail.com>, <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Apr 2014, #08; Fri, 25)
Date: Sat, 26 Apr 2014 10:39:02 +0100 [thread overview]
Message-ID: <27645ABF2E944872BB3F944B17E9490B@PhilipOakley> (raw)
In-Reply-To: 535b4c5a3c91c_3d63109d2f00@nysa.notmuch
From: "Felipe Contreras" <felipe.contreras@gmail.com>
>
> My conclusion is based on logic and reason,
you forget "And repeatable measurement / evidence" ....
> which
> are the bedstone of science.
> You can make sensible decisions based on that alone, and in fact
> that's how
> most good decisions are made.
>
> --
> Felipe Contreras
> --
At the moment we are missing the repeatable measurements, which can't
happened until the @{publish}, and others, have been released and used
for a while[1], otherwise we [prematurely] are back to one size fits all
solutions.
I suspect your solution may become the lead candidate for @{p}, but as
they say, "making predictions is hard, especially about the future".
regards
Philip
[1] we don't have a good measurement technique for existing usage
frequencies (as typed by real users in real life, weighted by user type,
...) either!
next prev parent reply other threads:[~2014-04-26 9:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 22:50 What's cooking in git.git (Apr 2014, #08; Fri, 25) Junio C Hamano
2014-04-25 23:19 ` Jeff King
2014-04-26 1:36 ` Felipe Contreras
2014-04-26 2:43 ` Alex Davidson
2014-04-26 6:04 ` Felipe Contreras
2014-04-26 9:39 ` Philip Oakley [this message]
2014-04-26 19:35 ` Felipe Contreras
2014-04-26 4:25 ` Jeff King
2014-04-28 17:48 ` Junio C Hamano
2014-04-28 18:01 ` Jeff King
2014-05-09 16:53 ` Michael Haggerty
2014-05-09 17:07 ` Felipe Contreras
2014-05-09 17:51 ` Philip Oakley
2014-05-12 21:05 ` Jeff King
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=27645ABF2E944872BB3F944B17E9490B@PhilipOakley \
--to=philipoakley@iee.org \
--cc=descenterace@hotmail.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
/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