From: Linus Torvalds <torvalds@osdl.org>
To: Tom Lord <lord@emf.net>
Cc: git@vger.kernel.org
Subject: Re: on when to checksum
Date: Wed, 20 Apr 2005 16:07:11 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0504201601130.6467@ppc970.osdl.org> (raw)
In-Reply-To: <200504202252.PAA16837@emf.net>
On Wed, 20 Apr 2005, Tom Lord wrote:
>
> How many times per day do you invoke `write-tree' and why?
Every single commit does a write-tree, so when I merge with Andrew, it's
usually a series of 100-250 of them in a row.
(Actually, _usualyl_ it's smaller series, but it's the big series that can
be painful enough to matter).
> It takes a large multiple of `0.3s' to get me to take you seriously
> on this point.
The thing is, I don't "trickle" things in. That would be horribly
inefficient for me. So I go over the patches, make a mbox, and do them all
in one go. And then they need to happen _fast_. If it takes 20 minutes, I
go away for coffee or something, and then if something didn't apply
half-way through, I will have lost my "context".
That's why I want things instant. Not because I have huge daily throughput
issues, but I have huge _latency_ issues.
I considered doing a "two-level" thing, where I first did the stuff in a
light-weigth patch manager, and then batched things up in the background
for the real thing. But the fact is, I don't think it's needed. Not the
way git performs now. If I can apply a hundred patches in a minute or two,
I have not "lost the context" if it turns out that there is some silly
glitch with one of them.
Linus
next prev parent reply other threads:[~2005-04-20 23:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-20 22:25 on when to checksum Tom Lord
2005-04-20 22:41 ` Linus Torvalds
2005-04-20 22:52 ` Tom Lord
2005-04-20 23:07 ` Linus Torvalds [this message]
2005-04-20 23:39 ` Tom Lord
2005-05-02 19:21 ` Tom Lord
2005-05-02 19:57 ` Linus Torvalds
2005-04-21 16:53 ` Andrew Timberlake-Newell
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=Pine.LNX.4.58.0504201601130.6467@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=lord@emf.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).