From: Sitaram Chamarty <sitaramc@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>,
David Lang <david@lang.hm>, Shawn Pearce <spearce@spearce.org>
Cc: Stefan Beller <sbeller@google.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: An interesting opinion on DVCS/git
Date: Fri, 06 Mar 2015 08:55:25 +0530 [thread overview]
Message-ID: <54F91E25.4050008@gmail.com> (raw)
In-Reply-To: <54F723D3.1050805@drmicha.warpmail.net>
On 03/04/2015 08:55 PM, Michael J Gruber wrote:
> Yes, that article has a few really weak lines of arguments, such as the
> tutorial count.
Here's his definition of the main draw of a DVCS:
No, the only thing that a DVCS gets you, by definition, is that
everyone gets a copy of the full offline history of the entire
repository to do with as you please.
That completely misses the point. What about committing while offline,
'git blame' months-old changes offline, or local branches that don't
have to make it to the server until they have cooked for a while, and so
on and on?
We're not all "facebooks" with multi-GB repos, and I certainly don't
care as much about disk space or bandwidth if losing those features is
the cost.
It gets worse:
Let me tell you something. Of all the time I have ever used DVCSes,
over the last twenty years if we count Smalltalk changesets and
twelve or so if you don’t, I have wanted to have the full history
while offline a grand total of maybe about six times.
I don't know how you can work on anything reasonably complex and
multi-developer without using some of those features six times in a
*week* (sometimes, six times in a *weekend*) let alone 12 years.
next prev parent reply other threads:[~2015-03-06 3:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54F2CD12.8050609@gmail.com>
2015-03-02 3:29 ` Fwd: An interesting opinion on DVCS/git Stefan Beller
2015-03-03 22:49 ` Shawn Pearce
2015-03-03 23:24 ` Junio C Hamano
2015-03-03 23:55 ` Randall S. Becker
2015-03-04 0:53 ` David Lang
2015-03-04 15:25 ` Michael J Gruber
2015-03-06 3:25 ` Sitaram Chamarty [this message]
2015-03-09 14:47 ` Philip Oakley
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54F91E25.4050008@gmail.com \
--to=sitaramc@gmail.com \
--cc=david@lang.hm \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=sbeller@google.com \
--cc=spearce@spearce.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).