From: Petr Baudis <pasky@suse.cz>
To: Junio C Hamano <junkio@cox.net>
Cc: Linus Torvalds <torvalds@osdl.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Make "git clone" less of a deathly quiet experience
Date: Sat, 11 Feb 2006 14:33:40 +0100 [thread overview]
Message-ID: <20060211133340.GS31278@pasky.or.cz> (raw)
In-Reply-To: <7vwtg2o37c.fsf@assigned-by-dhcp.cox.net>
BTW, some historical (from the very channel beginning) logs of #git for
fun, profit and late night reading are available at
http://pasky.or.cz/~pasky/cp/%23git/, e.g. the 2006-02-10 early morning
features the King Penguin explaining the deepness and intricacies of
pack files construction! Don't miss the opportunity!
New files won't be world-readable by default, but I hope to get some
irclogger with cutesy web interface set up for #git.
Dear diary, on Sat, Feb 11, 2006 at 06:48:55AM CET, I got a letter
where Junio C Hamano <junkio@cox.net> said that...
> Linus Torvalds <torvalds@osdl.org> writes:
>
> > Anyway, _something_ like this is definitely needed. It could certainly be
> > better (if it showed the same kind of thing that git-unpack-objects did,
> > that would be much nicer, but would require parsing the object stream as
> > it comes in). But this is big step forward, I think.
> >
> > Signed-off-by: Linus Torvalds <torvalds@osdl.org>
> > ---
> >
> > Comments? Hate-mail? Improvements?
>
> It probably should default to quiet if (!isatty(1)).
isatty(2) or something, 1 is in practice always a ref generator. Perhaps
it would be better not to clutter stderr, though; what about directly
opening /dev/tty? Does Cygwin support that?
> The real improvement, independent of this client-side patch,
> would be to reuse recently generated packs, but that needs
> writable cache directory on the server side. Another thing that
> I stumbled upon last time I tried it was that it did not look
> totally trivial to modify the csum-file interface so that I can
> splice the output from it into two different destinations (one
> to cachefile, the other to the consumer).
Yes, I said that on IRC yesterday as well. I don't think even a cache is
needed; just look at the repository and say:
* while there are packs containing only objects we are going to
send, pick the largest one and send it as-is.
* if there is a pack with more than a 75% (totally arbitrary)
overlap with the objects we are going to send, send it as-is.
* pack the loose objects.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Of the 3 great composers Mozart tells us what it's like to be human,
Beethoven tells us what it's like to be Beethoven and Bach tells us
what it's like to be the universe. -- Douglas Adams
next prev parent reply other threads:[~2006-02-11 13:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-11 4:31 Make "git clone" less of a deathly quiet experience Linus Torvalds
2006-02-11 4:37 ` Linus Torvalds
2006-02-11 5:50 ` Junio C Hamano
2006-02-11 17:39 ` Linus Torvalds
2006-02-11 5:48 ` Junio C Hamano
2006-02-11 7:35 ` Craig Schlenter
2006-02-11 8:44 ` Radoslaw Szkodzinski
2006-02-11 13:05 ` Petr Baudis
2006-02-11 13:15 ` Radoslaw Szkodzinski
2006-02-11 13:33 ` Petr Baudis [this message]
2006-02-11 13:41 ` Petr Baudis
2006-02-11 17:24 ` Alex Riesen
2006-02-11 17:45 ` Linus Torvalds
2006-02-11 19:10 ` Keith Packard
2006-02-12 3:43 ` Andreas Ericsson
2006-02-12 4:11 ` Keith Packard
2006-02-12 11:02 ` Andreas Ericsson
2006-02-12 21:04 ` Keith Packard
2006-02-16 6:56 ` Eric W. Biederman
2006-02-16 7:33 ` Junio C Hamano
2006-02-13 2:06 ` Martin Langhoff
2006-02-13 3:36 ` Junio C Hamano
2006-02-11 18:39 ` Alex Riesen
2006-02-11 19:04 ` Linus Torvalds
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=20060211133340.GS31278@pasky.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=torvalds@osdl.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).