unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: doco on bitwise logicals
Date: Mon, 05 May 2003 20:23:52 -0500	[thread overview]
Message-ID: <87issozx3r.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <873cjtt1gu.fsf@zip.com.au> (Kevin Ryde's message of "Tue, 06 May 2003 09:31:29 +1000")

Kevin Ryde <user42@zip.com.au> writes:

> Also sneaking in here (in the patch but not stated) is a fix for
> lognot to say ones-complement, where it says twos-complement now.
> This would be a fix for the 1.6 branch as well as the mainline I
> think.

Yes.  Any fixes that are really documentation or bug fixes that you
have the time to commit to 1.6, please do.

Also, if you haven't dealt with two branches yet, I've found it
helpful to just keep two trees checked out, one on 1.6 via "cvs update
-r branch_release_1-6 -Pd", and the other on the unstable branch
(i.e. HEAD)...

(here's hoping we can move to subversion one of these days...)

Thanks very much for the work.

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, 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-05-06  1:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-04  0:56 doco on bitwise logicals Kevin Ryde
2003-05-04  5:35 ` Rob Browning
2003-05-05 23:35   ` Kevin Ryde
2003-05-10  1:10     ` Kevin Ryde
2003-05-10  3:58       ` Kevin Ryde
2003-05-05 23:31 ` Kevin Ryde
2003-05-06  1:23   ` Rob Browning [this message]
2003-05-06  2:02     ` Kevin Ryde
2003-05-08  1:07     ` Kevin Ryde
2003-05-09 23:12       ` Rob Browning

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=87issozx3r.fsf@raven.i.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=guile-devel@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).