From: "Felipe Contreras" <felipe.contreras@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
"Craig L. Ching" <cching@mqsoftware.com>,
sverre@rabbelier.nl, "Git Mailinglist" <git@vger.kernel.org>
Subject: Re: Git vs Monotone
Date: Sat, 23 Aug 2008 22:23:06 +0300 [thread overview]
Message-ID: <94a0d4530808231223g5940b691r41072b1432e9c6ab@mail.gmail.com> (raw)
In-Reply-To: <7vmyjxyf7a.fsf@gitster.siamese.dyndns.org>
On Thu, Jul 31, 2008 at 11:24 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Linus Torvalds <torvalds@linux-foundation.org> writes:
>
>> ... And since the original pack-file is marked as a 'keep' file,
>> that original pack-file won't even be broken apart.
>
> Oops, isn't that something we fixed recently as a "bug"?
>
>> So completely ignoring the fact that you could do a single database with
>> git, and completely ignoring the fact that with git you'd probably use
>> branches for at least some of those 11 repos anyway, he'd _still_ have had
>> less disk space used by git unless he would do something intentionally odd
>> (like clone all the repositories over the network separately).
>
> Well, people are not perfect and they are free to express their opinions
> based on faulty understanding of reality on their blogs. The right things
> to do are (1) ignore them on the list and not waste many people's time,
> and/or (2) educate them, but in private or in a circle where many other
> similar ignorants benefit from such education. That is not here but
> perhaps on #monotone channel?
Hm, joined late to the discussion.
I had a lengthy discussion on pidgin's mailing list regarding my
analysis of monotone [1]. I didn't go very well. I don't think they
want to be educated about git.
It turns out they evaluated git as an option in the 1.0 days and they
disregarded it mainly because of the size of the repo; they didn't run
'git gc'. I fail to understand why they didn't drop in #git or asked
in the mailing list. That should tell you enough about their informed
decisions.
Anyway, that blog post was probably a way to justify their choice
after the discussion. With the added note now there's nothing that
makes git a bad choice for them, but surely they will find another
equally flawed reason.
Best regards.
[1] http://pidgin.im/pipermail/devel/2008-July/006308.html
--
Felipe Contreras
next prev parent reply other threads:[~2008-08-23 19:24 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 18:13 Git vs Monotone Sverre Rabbelier
2008-07-31 18:33 ` Stephen R. van den Berg
2008-07-31 18:52 ` Petr Baudis
2008-07-31 19:02 ` Jeff King
2008-07-31 19:11 ` Craig L. Ching
2008-07-31 19:19 ` Sverre Rabbelier
2008-07-31 20:32 ` Jeff King
2008-07-31 19:17 ` Linus Torvalds
2008-07-31 19:28 ` Craig L. Ching
2008-07-31 19:52 ` Linus Torvalds
2008-07-31 20:24 ` Junio C Hamano
2008-07-31 20:30 ` Linus Torvalds
2008-08-23 19:23 ` Felipe Contreras [this message]
2008-07-31 20:42 ` Blum, Robert
2008-08-10 22:15 ` Robin Rosenberg
2008-08-01 9:57 ` David Kastrup
2008-07-31 19:48 ` Monotone workflow compared to Git workflow ( was RE: Git vs Monotone) Craig L. Ching
2008-07-31 20:09 ` Linus Torvalds
2008-07-31 20:18 ` Shawn O. Pearce
2008-07-31 20:37 ` Craig L. Ching
2008-07-31 20:54 ` Björn Steinbrink
2008-07-31 21:10 ` Avery Pennarun
2008-07-31 21:13 ` Linus Torvalds
2008-07-31 21:43 ` Martin Langhoff
2008-07-31 21:40 ` Linus Torvalds
2008-08-01 2:50 ` Dmitry Torokhov
2008-08-01 3:02 ` Linus Torvalds
2008-08-01 3:59 ` Linus Torvalds
2008-07-31 20:57 ` Sean Estabrooks
2008-07-31 21:22 ` Theodore Tso
2008-07-31 19:24 ` Git vs Monotone Theodore Tso
2008-08-01 7:23 ` Sverre Rabbelier
2008-08-01 18:00 ` Daniel Barkalow
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=94a0d4530808231223g5940b691r41072b1432e9c6ab@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=cching@mqsoftware.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sverre@rabbelier.nl \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).