unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Andreas Rottmann <a.rottmann@gmx.at>
Cc: guile-user@gnu.org
Subject: guile-core in Arch archive [was: Patches from ttn's tree to Guile CVS]
Date: Sat, 06 Mar 2004 18:17:18 +0100	[thread overview]
Message-ID: <87brn9gajl.fsf@ivanova.rotty.yi.org> (raw)
In-Reply-To: 200403032038.07053.clinton@unknownlamer.org


First, I'm happy to announce the availibility of an Arch "mirror" of
the Guile CVS. It's located at:

http://people.debian.org/~rotty/arch/rotty@debian.org/guile-2004/

In the category guile-core, there is a cvs-trunk branch, which will
follow CVS HEAD. I might one day start auto-building Debian packages
for experimental from that (and maybe other branches).

Clinton Ebadi <clinton@unknownlamer.org> writes:

> http://unknownlamer.org/files/code/scheme/patches/guile-cvs will now
> contain all of the patches against Guile CVS HEAD which add features
> from ttn's tree.  I am making each change a separate patch (cleaner
> that way).
>
I've merged those into a new --ttn-features branch:

guile-core--ttn-features--0.1
    base-0 .. patch-3

      base-0
         tag of rotty@debian.org--guile-2004/guile-core--cvs-trunk--0--base-0

      patch-1
         Sync with cvs-trunk

      patch-2
         Applied extended -e patch by Clinton Ebadi

      patch-3
         Applied getopt-long patch by Clinton Ebadi

You might consider branching off that and I'll star-merge your changes
back in, which lowers effort for both off us (just make sure you
commit clean changesets, as you've done now).

> Is there any chance of these ever being merged?
>
Well, into the Archive: your chances are near 100% ;-). As for CVS:
dunno.

Cheers, Andy
-- 
Andreas Rottmann         | Rotty@ICQ      | 118634484@ICQ | a.rottmann@gmx.at
http://yi.org/rotty      | GnuPG Key: http://yi.org/rotty/gpg.asc
Fingerprint              | DFB4 4EB4 78A4 5EEE 6219  F228 F92F CFC5 01FD 5B62

Any technology not indistinguishable from magic is insufficiently advanced.
   -- Terry Pratchett



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


  parent reply	other threads:[~2004-03-06 17:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-04  1:37 Patches from ttn's tree to Guile CVS Clinton Ebadi
2004-03-06 15:57 ` Neil Jerram
2004-03-10 23:46   ` Marius Vollmer
2004-03-14 10:44     ` Andreas Rottmann
2004-03-21  2:11       ` Marius Vollmer
2004-03-06 17:17 ` Andreas Rottmann [this message]
2004-03-10 22:34   ` guile-core in Arch archive [was: Patches from ttn's tree to Guile CVS] Clinton Ebadi
2004-03-12  9:31     ` guile-core in Arch archive Andreas Rottmann
2004-03-10 23:32   ` guile-core in Arch archive [was: Patches from ttn's tree to Guile CVS] Tom Lord
2004-03-07 11:04 ` Patches from ttn's tree to Guile CVS Marius Vollmer
2004-03-09 20:35 ` Marius Vollmer
2004-03-09 20:36 ` Marius Vollmer
2004-03-09 20:42 ` Marius Vollmer

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=87brn9gajl.fsf@ivanova.rotty.yi.org \
    --to=a.rottmann@gmx.at \
    --cc=guile-user@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.
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).