From: Linus Torvalds <torvalds@linux-foundation.org>
To: Graeme Geldenhuys <graemeg@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Official git repository history?
Date: Tue, 30 Jun 2009 12:01:57 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.01.0906301058100.3605@localhost.localdomain> (raw)
In-Reply-To: <h2chap$i27$1@ger.gmane.org>
On Tue, 30 Jun 2009, Graeme Geldenhuys wrote:
>
> Last night I played further with the first ever commit. I managed to
> figure out the sequence in which commands had to be run. Kudos to the
> people that decided the make the commands easier in the later versions.
> :-)
Well, in all fairness, even _I_ didn't enjoy using it at that stage. It
was all very hacky, with the manual "write-tree" + "commit-tree" stuff.
But it's interesting to look at the timing:
- Start early April
- First git commit April 7
- first kernel commit April 16
- first merge: April 17 (14:47)
The time of that first merge is interesting, because it's worth
correlating the git tree with the early kernel tree there. What preceded
that first merge? Yup: the git 'merge-base' program was written a couple
of hours before.
But the really interesting thing (to me) is that while I had tools/scripts
to apply patches and to do relatively fancy tthings like merges etc
basically just a couple of weeks after starting, it's telling just how
long it took for something as simple as "git commit" to happen: May 30.
Never mind that it was actually just a totally trivial shell script,
literally just a few lines. So it wasn't about the technology, it's very
much a sign of what mattered to me.
I mean, I had a tool to create merges with conflicts back in mid-april!
But something as simple as just committing the existing tree? No tools,
you had to do that whole
git-update-index ..
commit=$(git-commit-tree $(git-write-tree) -p HEAD)
.. type in message ..
echo $commit > .git/HEAD
song-and-dance by hand.
Or use cogito, which explains the success of early wrappers - other people
had rather different priorities than I did.
Linus
next prev parent reply other threads:[~2009-06-30 19:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 14:27 Official git repository history? Graeme Geldenhuys
2009-06-30 7:46 ` Junio C Hamano
2009-06-30 8:09 ` Graeme Geldenhuys
2009-06-30 9:33 ` Andreas Ericsson
2009-06-30 9:39 ` Graeme Geldenhuys
2009-06-30 19:01 ` Linus Torvalds [this message]
2009-07-01 8:08 ` Graeme Geldenhuys
2009-06-30 23:06 ` 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=alpine.LFD.2.01.0906301058100.3605@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=graemeg@gmail.com \
/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