unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: What have the Romans done for us?  (Bazaar)
Date: Wed, 07 Apr 2010 22:38:10 +0200	[thread overview]
Message-ID: <87zl1fhubx.fsf@telefonica.net> (raw)
In-Reply-To: 20100405145637.GA3248@muc.de

Alan Mackenzie <acm@muc.de> writes:

[snip]

> So, yes, bzr is wonderful, because it's a DISTRIBUTED VCS, and
> distributed VCSs are Good Things.  Would somebody please remind me why?

Using Distributed Version Control Sytems (dVCSs) supports the goals of
the Free Software movement.

Free Software grants the user the right to access the source code so he
can study it. Just as producing well written source reinforces this
right, giving easy access to the VC history does likewise. Easy access
here means local access, so the user can perform whatever operation he
pleases without the constraints of a remote server.

Free Software grants the user the right to modify the source
code. Distributed VCs makes this much easier, as it is trivial to create
your personal fork (branch) and integrate changes from upstream. Compare
this with maintaining sets of patches.

Free Software means granting the user the right to re-distribute his
modified software. With a dVCS, publishing your personal branch is
almost as easy as putting a tarball for download, but with the added
advantage for your users of having an easy method for knowing exactly
how your modified source differs from the master project, and providing
the capability of easily picking specific changes and integrating them
on other forks or on the original project, which includes allowing your
users the capability of basing their changes on top of yours (i.e. by
forking your source code).

Thus dVCSs are excellent tools for administering your local changes and
sharing them with the community. This is a strong encouragement for
people who is considering start hacking on some piece of software.

Implicit conveniences:

If the master project vanishes, you can resurrect it in no-time without
missing a bit of development history.

If you wish to collaborate with others developing a fork (branch) of the
original project, dVCSs makes this trivial.

If you wish to contribute your changes to the original project, dVCSs
makes this substantially easier than previous tools.

IMO GNU should recommend using Distributed Version Control Systems to
all developers working on Free Software.





      parent reply	other threads:[~2010-04-07 20:38 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-05 14:56 What have the Romans done for us? (Bazaar) Alan Mackenzie
2010-04-05 15:32 ` Karl Fogel
2010-04-05 16:08   ` Andreas Schwab
2010-04-05 20:54     ` Karl Fogel
2010-04-05 21:11       ` Andreas Schwab
2010-04-05 21:19         ` Andreas Schwab
2010-04-05 16:40   ` Eli Zaretskii
2010-04-05 19:44     ` Stefan Monnier
2010-04-05 22:01       ` Eli Zaretskii
2010-04-05 20:56     ` Karl Fogel
2010-04-05 19:39   ` Óscar Fuentes
2010-04-06 14:31   ` Alan Mackenzie
2010-04-06 15:24     ` Andreas Schwab
2010-04-06 17:02     ` Chad Brown
2010-04-06 19:50       ` Juri Linkov
2010-04-07  6:33     ` Eli Zaretskii
2010-04-07 18:47     ` Stephen J. Turnbull
2010-04-05 15:34 ` Eli Zaretskii
2010-04-05 15:43   ` Andreas Schwab
2010-04-05 16:42     ` Eli Zaretskii
2010-04-05 19:52     ` Stefan Monnier
2010-04-06 10:43     ` Richard Stallman
2010-04-07 18:11       ` Stephen J. Turnbull
2010-04-05 16:01 ` Chad Brown
2010-04-05 19:56   ` Stefan Monnier
2010-04-05 23:06     ` chad
2010-04-06  7:14       ` Stephen J. Turnbull
2010-04-05 16:12 ` Chong Yidong
2010-04-06 10:43 ` Richard Stallman
2010-04-06 13:25   ` Alan Mackenzie
2010-04-12  5:04     ` Martin Pool
2010-04-06 14:35 ` Jason Rumney
2010-04-06 16:20   ` Alan Mackenzie
2010-04-07 18:21     ` Stephen J. Turnbull
2010-04-07 20:38 ` Óscar Fuentes [this message]

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: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zl1fhubx.fsf@telefonica.net \
    --to=ofv@wanadoo.es \
    --cc=emacs-devel@gnu.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://git.savannah.gnu.org/cgit/emacs.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).