unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Cc: hanwen@cs.uu.nl, guile-devel@gnu.org, mvo@zagadka.de
Subject: Re: Cygwin patch for 1.6.4
Date: Wed, 01 Oct 2003 17:28:16 -0500	[thread overview]
Message-ID: <87d6dgbnjz.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <87u16s7mt4.fsf@peder.flower> (Jan Nieuwenhuizen's message of "Wed, 01 Oct 2003 21:57:59 +0200")

Jan Nieuwenhuizen <janneke@gnu.org> writes:

> Attached.  The biggest part is the libtool diff, you'll want to skip
> that and just look at the small upstream/ltdl*diff instead.
>
> Also note that most of this is in HEAD and some of it has already been
> modified again a few months ago.

OK, so just to make sure I follow, this is a patch against 1.6.4, and
it would be appropriate for the upcoming 1.6.5.  Further, if I'm going
ot apply it to 1.6 before 1.6.5, I should ignore the libool bits.  Did
I get that right?

Thanks much.
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592  F9A0 25C8 D377 8C7E 73A4


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


  reply	other threads:[~2003-10-01 22:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <16225.62509.832674.84224@localhost.localdomain>
2003-10-01 19:57 ` Cygwin patch for 1.6.4 [WAS: When is 1.8 going to be released] Jan Nieuwenhuizen
2003-10-01 22:28   ` Rob Browning [this message]
2003-10-02  7:21     ` Cygwin patch for 1.6.4 Jan Nieuwenhuizen
2003-10-02 16:18       ` Rob Browning
2003-10-02 17:31         ` Jan Nieuwenhuizen
2003-10-02 17:34           ` Jan Nieuwenhuizen
2003-10-12 18:50           ` Rob Browning
2003-10-02  1:33   ` Kevin Ryde

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=87d6dgbnjz.fsf@raven.i.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=guile-devel@gnu.org \
    --cc=hanwen@cs.uu.nl \
    --cc=mvo@zagadka.de \
    /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).