All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Zhi Li <lizhi1215@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: early days before git's invention
Date: Sun, 08 Nov 2009 05:29:01 -0800 (PST)	[thread overview]
Message-ID: <m3ws21rvrd.fsf@localhost.localdomain> (raw)
In-Reply-To: <2986b3940911080423p4ccfe279ia00c995e1ea23fb9@mail.gmail.com>

Zhi Li <lizhi1215@gmail.com> writes:

> I have a question maybe not suitable to be put on this list. I'm just
> curious on git and Linux history. As what was said on wiki, Linux
> kernel was maintained by BitKeeper, then for some reason, BitKeeper
> can not be used, so git was invented. My question is what was used
> before BitKeeper, CVS? I don't think so. Then, just using file to
> manage?

For why BitKeeper could not be used, see:
  http://en.wikipedia.org/wiki/Git_(software)#Early_history
  http://git.or.cz/gitwiki/GitHistory
  http://kerneltrap.org/node/4982
  http://www.pcworld.idg.com.au/article/129776/after_controversy_torvalds_begins_work_git?fp=16&fpid=0

  http://better-scm.berlios.de/bk/demise-of-gratis-bitkeeper.html
  http://better-scm.berlios.de/bk/what-bitmover-got-wrong.html
  http://better-scm.berlios.de/bk/the-bitkeeper-ghost.html

Before BitKeeper Linux used tarballs (for releases) plus patches (for
changes); patches were send by email (on LKML).  Some maintainers used
tools like Quilt (or custom scripts) for patch management.


P.S. FreeBSD (IIRC) used / uses CVS for version control, but it has
quite different development model than Linux.

-- 
Jakub Narebski
Poland

  parent reply	other threads:[~2009-11-08 13:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-08 12:23 early days before git's invention Zhi Li
2009-11-08 13:10 ` Alejandro Riveira
2009-11-08 13:12 ` Johannes Schindelin
2009-11-08 13:29 ` Jakub Narebski [this message]
2009-11-09  3:39   ` Zhi Li

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=m3ws21rvrd.fsf@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=lizhi1215@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.