From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] hgfs
Date: Thu, 22 May 2014 18:20:08 +0200 [thread overview]
Message-ID: <1ff569ca5808e0b9a00799bbf594fcc8@proxima.alt.za> (raw)
In-Reply-To: <1a387abb8b40a66c414b0110c8072f06@ladd.quanstro.net>
> in any event, back to the subject at hand. this in-depth discussion of various
> revision control systems seems to assume that revision control is the key issue.
Much as I agree with you that clear objectives are essential to any
type of success (a tautology if ever there was one - what do you
measure success against, if the objectives aren't clear?), it was the
code review bit that I perceived as an obstacle.
But you're right, and your objectives make a fine starting point.
They ought to attract discussion, though, as they seem to me a little
too specialised (?). I want a little time to ponder over them,
anyway, as it takes me a while to grasp all the ramifications.
L.
next prev parent reply other threads:[~2014-05-22 16:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 6:52 Skip Tavakkolian
2014-05-22 7:36 ` lucio
2014-05-22 9:54 ` Aram Hăvărneanu
2014-05-22 10:30 ` lucio
2014-05-22 10:41 ` Aram Hăvărneanu
2014-05-22 15:35 ` Skip Tavakkolian
2014-05-22 15:56 ` erik quanstrom
2014-05-22 16:17 ` ron minnich
2014-05-22 16:21 ` Kurt H Maier
2014-05-22 16:31 ` Aram Hăvărneanu
2014-05-22 18:37 ` ron minnich
2014-05-22 18:45 ` Kurt H Maier
2014-05-22 18:51 ` Aram Hăvărneanu
2014-05-22 19:02 ` Latchesar Ionkov
2014-05-22 19:13 ` Kurt H Maier
2014-05-22 19:16 ` erik quanstrom
2014-05-22 19:23 ` Latchesar Ionkov
2014-05-23 3:45 ` hiro
2014-05-22 19:11 ` Skip Tavakkolian
2014-05-22 19:23 ` Bakul Shah
2014-05-22 19:47 ` Skip Tavakkolian
2014-05-22 16:20 ` lucio [this message]
2014-05-22 19:46 ` Bakul Shah
-- strict thread matches above, loose matches on Subject: below --
2011-06-27 5:43 cinap_lenrek
2011-06-27 13:15 ` hiro
2011-06-27 5:09 cinap_lenrek
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=1ff569ca5808e0b9a00799bbf594fcc8@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@9fans.net \
/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).