unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Ken Raeburn <raeburn@raeburn.org>
Subject: Re: [PATCH] Improved `scm_from_locale_symbol ()' + `scm_take_locale_symbol ()'
Date: Tue, 24 Jan 2006 18:27:42 -0500	[thread overview]
Message-ID: <BA5E0BC0-7317-4ABC-86A3-47EB29F301C1@raeburn.org> (raw)
In-Reply-To: <dr64sf$ijm$1@sea.gmane.org>

On Jan 24, 2006, at 16:06, Han-Wen Nienhuys wrote:
> In article <87y815frpf.fsf@laas.fr>,
> Ludovic Courtès <ludovic.courtes@laas.fr> wrote:
>> hanwen@byrd.xs4all.nl (Han-Wen Nienhuys) writes:
>>
>>> Yes,  -- FWIW,  I warmly recommend darcs, which is much easier to  
>>> use.
>>
>> I don't think there's such a huge difference, especially when  
>> looking at
>> [0].  Additionally, most of the commands shown there now have
>> "easy-looking" counterparts taken from Bazaar, e.g., `branch',  
>> `switch',
>> etc.  Both Arch and Darcs are easy to administrate and deploy.
>>
>> Anyway, if we were to choose a DRCS for Guile, I think it'd make  
>> sense
>> to favor the GNU implementation.
>
> This is offtopic, but I think that this is kind of politically
> motivated reasoning is not in GUILE's best interests.

The FSF is now running an arch server at savannah, see http:// 
arch.sv.gnu.org for info.

As for the politics, you may have noticed that GNU is a somewhat  
politically motivated project... :-)  But I have no idea if the  
choice of arch is official, or just what some volunteers were willing  
to support; ask RMS if you want to know the official position.   
(Personally, my preference would be svn, which I'm using at work, and  
svk for associated distributed work, but whatever....)

Ken

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2006-01-24 23:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-19 17:23 [PATCH] Improved `scm_from_locale_symbol ()' + `scm_take_locale_symbol ()' Ludovic Courtès
2006-01-11  8:39 ` Ludovic Courtès
2006-01-24  8:14 ` Ludovic Courtès
2006-01-24 11:02   ` Han-Wen Nienhuys
2006-01-24 14:17     ` Ludovic Courtès
2006-01-24 16:18       ` Han-Wen Nienhuys
2006-01-24 17:42         ` Ludovic Courtès
2006-01-24 21:06           ` Han-Wen Nienhuys
2006-01-24 23:27             ` Ken Raeburn [this message]
2006-01-25  9:45               ` Ludovic Courtès
2006-01-25 11:18                 ` Ken Raeburn
2006-01-25 13:29                   ` Distributed revision control, etc Ludovic Courtès
2006-01-25 18:04                     ` Ken Raeburn
2006-01-24 11:11 ` [PATCH] Improved `scm_from_locale_symbol ()' + `scm_take_locale_symbol ()' Han-Wen Nienhuys
2006-01-24 14:22   ` Ludovic Courtès

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/guile/

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

  git send-email \
    --in-reply-to=BA5E0BC0-7317-4ABC-86A3-47EB29F301C1@raeburn.org \
    --to=raeburn@raeburn.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 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).