unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman@gmail.com>
To: "Eric M. Ludlam" <eric@siege-engine.com>
Cc: cedet-devel@lists.sf.net, Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: Switching CEDET from CVS to a Distributed VCS.
Date: Thu, 25 Jun 2009 00:45:32 +0200	[thread overview]
Message-ID: <e01d8a50906241545w597121f6rd6f6f3be89f8f0a6@mail.gmail.com> (raw)
In-Reply-To: <1245882173.24086.14.camel@projectile.siege-engine.com>

Hi Eric,

I think I have said it before, but I believe it is worth saying again:
Emacs repository will be moved from CVS to Bazaar. And since CEDET is
going to be included in Emacs you will most likely be using Bazaar
after that.

Alex, as I said before I do not know much at all about version control
system. However even from my limited understanding of this I still
can't find room for arguments for using something else than Bazaar for
CEDET. Will not using something else than Bazaar put an extra burdon
on Eric? And I guess that is what we all want to avoid ... ;-)

I am CC-ing Emacs Devel because there are people who understands this
much better than I do.



On Thu, Jun 25, 2009 at 12:22 AM, Eric M. Ludlam<eric@siege-engine.com> wrote:
> Hi all,
>
>  Alex Ott has been looking into what it would take to move CEDET from
> CVS to a distributed version control system, such as GIT or Mercurial.
> (Thanks Alex)
>
>  I haven't used these systems myself, but would be happy to learn in
> order to make access to CEDET easier.  Does anyone have advice on a good
> tactic to take?  Whatever it is needs to be low maintenance for me, as
> I'd rather spend my time hacking Emacs than dealing with VCSes.
>
>  Alex's high level summary is:
>
> ------------
> Mercurial (http://sourceforge.net/apps/trac/sourceforge/wiki/Mercurial)
> we'll have:
>  + Native support for all platforms - Unix/Windows
>  + Anonymous access to repository via http
>  - Less features out of box, comparing with Git, but most of them are
>  available as extensions, installed separately
>
> For Git (http://sourceforge.net/apps/trac/sourceforge/wiki/Git) we'll
> have:
>  - Native support for Unixes only, Windows port is slightly limited
>  - Anonymous access via git protocol - this could make some problems for
>  users behind firewalls
>
> all other features seem the same.
> ------------
>
> Thanks for any input.
> Eric
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Cedet-devel mailing list
> Cedet-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/cedet-devel
>

------------------------------------------------------------------------------
_______________________________________________
Cedet-devel mailing list
Cedet-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cedet-devel

       reply	other threads:[~2009-06-24 22:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1245882173.24086.14.camel@projectile.siege-engine.com>
2009-06-24 22:45 ` Lennart Borgman [this message]
2009-06-24 23:51   ` Switching CEDET from CVS to a Distributed VCS Eric M. Ludlam
2009-06-25  2:40   ` Miles Bader
2009-06-25 13:52     ` David Bernard
2009-06-25 16:04       ` [CEDET-devel] " Davi Diaz
2009-06-26  0:09         ` Miles Bader
2009-06-25 17:48     ` Stephen J. Turnbull
2009-06-25 18:24       ` David Reitter
2009-06-28  6:17         ` Stephen J. Turnbull
2009-06-28 11:45           ` David Reitter
2009-06-28 14:04             ` Stephen J. Turnbull
2009-06-28 14:29               ` David Reitter
2009-06-29 23:19                 ` Stephen J. Turnbull
2009-06-30  0:16                   ` David Reitter
     [not found]   ` <393CA42E-4553-4F2D-92D8-F0D3CEE19223@gmail.com>
2009-06-25  8:44     ` [CEDET-devel] " Lennart Borgman
2009-06-25 12:53       ` Stefan Monnier
2009-06-25 13:19       ` David Reitter

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=e01d8a50906241545w597121f6rd6f6f3be89f8f0a6@mail.gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=cedet-devel@lists.sf.net \
    --cc=emacs-devel@gnu.org \
    --cc=eric@siege-engine.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.
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).