From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: FAQ Q: another version control system?
Date: Wed, 02 May 2007 10:35:20 +0200 [thread overview]
Message-ID: <f19ig9$473$1@sea.gmane.org> (raw)
In-Reply-To: 9e7886190705020013k5721480aj767c1c8643fc8d23@mail.gmail.com
[Cc: Peter <petervanbohning@gmail.com>, git@vger.kernel.org]
Peter wrote:
> Do we really need another version control system? As I understand it,
> this is like a distributed, central-server-less, CVS, sorry, SVN
> server.
There is large difference between centralized and distributed SCMs.
Besides, thats like asking why we have so many Linux distributions, or why
we have KDE, GNOME, XFCE, etc.
> But why isn't such a feature set added into SVN?
There is SVK which is distributed SCM built on top of Subversion.
But there are some things that cannot be done because it uses SVN
as engine. Performance is one of them.
> Why do I have to
> download another version control system just so that I can "git"
> libxcb and X11 so that I can compile gtk so that I can compile xchat
> so that I can go onto the IRC server for madwifi so that I can ask
> someone there why their wifi drivers don't create a /dev/wifi0 on my
> system so that I can get my wireless working????
You don't need to install git to download and install programs; there are
tarballs and packages. You don't even need git to work on program and send
corrections, although it is recommended.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2007-05-02 8:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9e7886190705020012n72070874nae5a74b6d1387e3@mail.gmail.com>
2007-05-02 7:13 ` FAQ Q: another version control system? Peter
2007-05-02 8:35 ` Jakub Narebski [this message]
2007-05-02 9:25 ` Andy Parkins
2007-05-02 10:08 ` Johannes Schindelin
2007-05-02 22:04 ` Martin Langhoff
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='f19ig9$473$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.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 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.