From: Ryan Anderson <ryan@michonline.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: Last mile to 1.0?
Date: Sat, 23 Jul 2005 04:50:31 -0400 [thread overview]
Message-ID: <20050723085031.GD3255@mythryan2.michonline.com> (raw)
In-Reply-To: <7vwtnqhcfb.fsf@assigned-by-dhcp.cox.net>
On Sat, Jul 16, 2005 at 10:46:00AM -0700, Junio C Hamano wrote:
> - Publicity. I would be very happy to see somebody with good
> writing and summarizing skills to prepare an article to be
> published on LWN.NET to coincide with the 1.0 release. An
> update to GIT traffic would also be nice.
How is this for a start?
Source Code Management with Git
Git, sometimes called "global information tracker", is a "directory
content manager". Git has been designed to handle absolutely massive
projects with speed and efficiency, and the release of the 2.6.12 and
(soon) the 2.6.13 version of the Linux kernel would indicate that it
does this task well.
Git falls into the category of distributed source code management tools,
similar to Arch or Darcs (or, in the commercial world, BitKeeper). This
means that every working directory is a full-fledged repository with
full revision tracking capabilities.
Git uses the SHA1 hash algorithm to provide a content-addressable pseudo
filesystem, complete with its own version of fsck.
o Speed of use, both for the project maintainer, and the end-users, is
a key development principle.
o The history is stored as a directed acyclic graph, making long-lived
branches and repeated merging simple.
o A collection of related projects are building on the core Git
project, either to provide an easier to use interface on top (Darcs,
Mercurial, StGit, Cogito), or to take some of the underlying concepts
and reimplement them directly into another system (Arch 2.0).
o Two, interchangeable, on-disk formats are used:
o An efficient, packed format that saves spaced and network
bandwidth.
o An unpacked format, optimized for fast writes and incremental
work.
Git results from the inspiration and frustration of Linus Torvalds, and
the enthusiastic help of over 300 participants on the development
mailing list.[1]
1 - Generated with the following, in a maildir folder:
find . -type f | xargs grep -h "^From:" | perl -ne \
'tr#A-Z#a-z#; m#<(.*)># && print $1,"\n";' | sort -u | wc -l
--
Ryan Anderson
sometimes Pug Majere
next prev parent reply other threads:[~2005-07-23 8:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-16 17:46 Last mile to 1.0? Junio C Hamano
2005-07-16 18:36 ` Eric W. Biederman
2005-07-17 0:49 ` Junio C Hamano
2005-07-17 1:18 ` David Lang
2005-07-18 5:44 ` Junio C Hamano
2005-07-18 4:53 ` Alexey Nezhdanov
2005-07-18 5:35 ` Junio C Hamano
2005-07-18 6:48 ` Alexey Nezhdanov
2005-07-18 7:38 ` Junio C Hamano
2005-07-23 8:15 ` Ryan Anderson
2005-07-23 12:56 ` Gene Heskett
2005-07-24 0:53 ` [PATCH 0/6] A bit better dumb server support Junio C Hamano
2005-07-23 8:50 ` Ryan Anderson [this message]
2005-07-23 13:14 ` Last mile to 1.0? Gene Heskett
2005-07-23 14:47 ` Kevin Smith
2005-07-23 17:09 ` Junio C Hamano
2005-07-24 3:12 ` Alexey Nezhdanov
2005-07-29 22:41 ` Petr Baudis
2005-07-30 2:11 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2005-07-30 5:40 barkalow
2005-07-30 8:07 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050723085031.GD3255@mythryan2.michonline.com \
--to=ryan@michonline.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).