From: "Neil Jerram" <neiljerram@googlemail.com>
To: "Ken Raeburn" <raeburn@raeburn.org>
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] Avoid `SCM_VALIDATE_LIST ()'
Date: Tue, 9 Sep 2008 01:11:49 +0200 [thread overview]
Message-ID: <49dd78620809081611w297b54cfic4bf36e445a1f3cd@mail.gmail.com> (raw)
In-Reply-To: <49dd78620809070824s41c1d69dyb26fd8f8d2f13866@mail.gmail.com>
2008/9/7 Neil Jerram <neiljerram@googlemail.com>:
> 2008/9/7 Ken Raeburn <raeburn@raeburn.org>:
>>
>> Still keeping it in the back of my mind, but first my attempts to use SVK to
>> mirror the Emacs repository broke (naturally, after it had looked solid
>> enough that I had switched to it for my Emacs development work), and now
>> Guile uses git, which I've never picked up, and some Emacs folks are talking
>> about changing to yet another source control system. (BTW, are people aware
>> that the www.gnu.org pages for guile list an ftp snapshot site that has in
>> fact not been updated since last September? For people not interested in
>> downloading, installing, and learning N new source control systems, daily or
>> weekly snapshots are handy.)
>
> Noted, thanks. I'll try to fix that up.
Snapshots as of now are up at
http://www.ossau.uklinux.net/guile/snapshots, and I hope they will
keep automagically appearing there.
In case anyone feels like reviewing and commenting on it, I've also
uploaded the `make-snap' script that generates these, in the same
directory.
If all seems well after a few days, I'll update the www.gnu.org pages
accordingly.
Neil
next prev parent reply other threads:[~2008-09-08 23:11 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-31 22:02 [PATCH] Avoid `SCM_VALIDATE_LIST ()' Ludovic Courtès
2008-09-01 0:12 ` Han-Wen Nienhuys
2008-09-01 20:19 ` Neil Jerram
2008-09-01 20:30 ` Ludovic Courtès
2008-09-02 2:40 ` Han-Wen Nienhuys
2008-09-06 22:23 ` Neil Jerram
2008-09-06 21:36 ` Neil Jerram
2008-09-07 4:23 ` Ken Raeburn
2008-09-07 15:24 ` Neil Jerram
2008-09-07 17:30 ` Ken Raeburn
2008-09-07 19:21 ` Neil Jerram
2008-09-08 23:11 ` Neil Jerram [this message]
2008-09-09 8:28 ` Ludovic Courtès
2008-09-10 20:43 ` Neil Jerram
2008-09-04 18:24 ` Andy Wingo
2008-09-05 0:10 ` Han-Wen Nienhuys
2008-09-05 1:06 ` Andy Wingo
2008-09-06 22:45 ` Neil Jerram
2008-09-07 2:33 ` Han-Wen Nienhuys
2008-09-07 13:38 ` Neil Jerram
2008-09-07 15:00 ` Han-Wen Nienhuys
2008-09-07 16:19 ` Neil Jerram
2008-09-07 19:25 ` Han-Wen Nienhuys
2008-09-07 14:05 ` Andy Wingo
2008-09-07 15:38 ` development goals (was: [PATCH] Avoid `SCM_VALIDATE_LIST ()') Han-Wen Nienhuys
2008-09-07 20:03 ` Neil Jerram
2008-09-08 4:28 ` development goals Han-Wen Nienhuys
2008-09-08 10:16 ` Ludovic Courtès
2008-09-08 13:57 ` Han-Wen Nienhuys
2008-09-09 7:08 ` Andy Wingo
2008-09-08 10:27 ` Ludovic Courtès
2008-09-06 22:40 ` [PATCH] Avoid `SCM_VALIDATE_LIST ()' Neil Jerram
2008-09-01 21:09 ` Neil Jerram
2008-09-01 21:47 ` Ludovic Courtès
2008-09-06 22:15 ` Neil Jerram
2008-09-08 9:40 ` Ludovic Courtès
2008-09-06 23:11 ` Mikael Djurfeldt
2008-09-07 2:43 ` Han-Wen Nienhuys
2008-09-07 15:04 ` Neil Jerram
2008-09-07 13:32 ` Neil Jerram
2008-09-02 2:44 ` Han-Wen Nienhuys
2008-09-06 22:32 ` Neil Jerram
2008-09-08 3:13 ` Han-Wen Nienhuys
2008-09-08 4:42 ` Clinton Ebadi
2008-09-08 9:47 ` 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=49dd78620809081611w297b54cfic4bf36e445a1f3cd@mail.gmail.com \
--to=neiljerram@googlemail.com \
--cc=guile-devel@gnu.org \
--cc=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).