From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Cc: Linus Torvalds <torvalds@osdl.org>
Subject: Last mile for 1.0 again
Date: Wed, 29 Jun 2005 00:16:10 -0700 [thread overview]
Message-ID: <7v4qbhfxad.fsf_-_@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0506282252001.14331@ppc970.osdl.org> (Linus Torvalds's message of "Tue, 28 Jun 2005 22:54:26 -0700 (PDT)")
>>>>> "LT" == Linus Torvalds <torvalds@osdl.org> writes:
LT> ..., but please don't
LT> change that, since that would be yet another incompatible pack format
LT> change, and I'd like to calm things down.
Calming things down is good. Some stuff we should be looking at
during calming down period are:
- Ask expert help to verify our use of zlib is OK; Linus asked
for this in a message tonight. I am not qualified to do this
myself.
- There is currently nothing that verifies the SHA1 sums
embedded in idx and pack files. A tool for it is needed
[*1*]. I may be doing this myself.
- Although there is a hook in sha1_file() that allows mapping a
pack file on demand (and keep track of their uses for LRU
eviction), there is currently no code to actually evict a
mapped pack file. We need to add some sort of use-reference
counting to lock down a pack file in use, if somebody is
inclined to do this. I will not be doing this myself
immediately.
- Think about what to do with the "dumb server" pull protocols
regarding packed archive files (think about http-pull). I
will not be doing this myself.
- Design "smart server" pull/push pair. This can independently
and actively be done without impacting "calming down" period,
and I am assuming Dan is already looking into this. This may
result in another "deathmatch" between Dan and Jason
Mcmullan, which would be fun to watch ;-).
Not limited to "calming down the packed GIT", but bigger picture
pre-release preparation items I think we need to look into are:
- Update "Last mile for 1.0" list. I think the only thing that
is left from the one I posted on Jun 5th is the tutorials.
Anybody interested in adding more pages to the tutorials? If
there is no taker, I may start continuing what is already
there, stealing example project outline from "Arch meets
Hello World" [*2*].
- Double check the documentation, usage strings in the code and
what the code does still match. Last time I checked, I think
some files in Documentation/ directory were not reachable
from the main GIT(1) page and were not touched by the build
process from Documentation/Makefile. I will not be doing
this myself.
- Blame/Annotate. Does anybody have a fast and correct one
[*3*]?
- Publicity. Somebody may want to start preparing materials to
have us included in http://better-scm.berlios.de/comparison/
[Footnotes]
*1* One possibility is to add that to fsck-cache when --full is
used, but I am somewhat reluctant to do it that way. It would
require you to place that "suspicious" pack under your
repository's .git/objects/pack in order to verify it, which can
spread the damage before you know it.
In general, idx file is relatively small, so we _could_ check
the SHA1 sum for idx files when we map them at runtime in
check_packed_git_idx(). However, verifying 1MB (kernel archive
case) idx file every time we run a single core GIT command may
be a price we would not want to pay, so I am not too
enthusiastic about doing it. We certainly would not want to do
this for pack files every time a pack is mapped at runtime (60MB
kernel archive case).
*2* http://regexps.srparish.net/www/tutorial/html/arch.html.
I am not talking about stealing the concepts but just talking
about stealing the sample project on which example players work
in the sample sessions. I think its section on update/replay
matches closely to merge/rebase, for example.
*3* I have what I wrote in Perl which does rename/copy/rewrite
and multiple parents correctly, but it is way too slow for
on-demand use.
next prev parent reply other threads:[~2005-06-29 7:13 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-25 4:20 kernel.org and GIT tree rebuilding David S. Miller
2005-06-25 4:40 ` Jeff Garzik
2005-06-25 5:23 ` Linus Torvalds
2005-06-25 5:48 ` Jeff Garzik
2005-06-25 6:16 ` Linus Torvalds
2005-06-26 16:41 ` Linus Torvalds
2005-06-26 18:39 ` Junio C Hamano
2005-06-26 19:19 ` Linus Torvalds
2005-06-26 19:45 ` Junio C Hamano
[not found] ` <7v1x6om6o5.fsf@assigned-by-dhcp.cox.net>
[not found] ` <Pine.LNX.4.58.0506271227160.19755@ppc970.osdl.org>
[not found] ` <7v64vzyqyw.fsf_-_@assigned-by-dhcp.cox.net>
2005-06-28 6:56 ` [PATCH] Obtain sha1_file_info() for deltified pack entry properly Junio C Hamano
2005-06-28 6:58 ` Junio C Hamano
2005-06-28 6:58 ` [PATCH 2/3] git-cat-file: use sha1_object_info() on '-t' Junio C Hamano
2005-06-28 6:59 ` [PATCH 3/3] git-cat-file: '-s' to find out object size Junio C Hamano
2005-06-26 20:52 ` kernel.org and GIT tree rebuilding Chris Mason
2005-06-26 21:03 ` Chris Mason
2005-06-26 21:40 ` Linus Torvalds
2005-06-26 22:34 ` Linus Torvalds
2005-06-28 18:06 ` Nicolas Pitre
2005-06-28 19:28 ` Linus Torvalds
2005-06-28 21:08 ` Nicolas Pitre
2005-06-28 21:27 ` Linus Torvalds
2005-06-28 21:55 ` [PATCH] Bugfix: initialize pack_base to NULL Junio C Hamano
2005-06-29 3:55 ` kernel.org and GIT tree rebuilding Nicolas Pitre
2005-06-29 5:16 ` Nicolas Pitre
2005-06-29 5:43 ` Linus Torvalds
2005-06-29 5:54 ` Linus Torvalds
2005-06-29 7:16 ` Junio C Hamano [this message]
2005-06-29 9:51 ` [PATCH] Add git-verify-pack command Junio C Hamano
2005-06-29 16:15 ` Linus Torvalds
2005-07-04 21:40 ` Last mile for 1.0 again Daniel Barkalow
2005-07-04 21:45 ` Junio C Hamano
2005-07-04 21:59 ` Linus Torvalds
2005-07-04 22:41 ` Daniel Barkalow
2005-07-04 23:06 ` Junio C Hamano
2005-07-05 1:54 ` Daniel Barkalow
2005-07-05 6:24 ` Junio C Hamano
2005-07-05 13:34 ` Marco Costalba
2005-06-25 5:04 ` kernel.org and GIT tree rebuilding Junio C Hamano
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=7v4qbhfxad.fsf_-_@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--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.
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).