From: nalaginrut <nalaginrut@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: redoing SCM representation in 2.2
Date: Thu, 12 May 2011 19:12:33 +0800 [thread overview]
Message-ID: <1305198753.2392.5.camel@Renee-desktop> (raw)
In-Reply-To: <m3fwok2pez.fsf@unquote.localdomain>
So we'll see a 48-bits solution in 2.2?
Sorry I can't say I'm clear since it's a long article.
--
GNU Powered it
GPL Protected it
GOD Blessed it
HFG - NalaGinrut
--hacker key--
v4sw7CUSMhw6ln6pr8OSFck4ma9u8MLSOFw3WDXGm7g/l8Li6e7t4TNGSb8AGORTDLMen6g6RASZOGCHPa28s1MIr4p-x hackerkey.com
---end key---
next prev parent reply other threads:[~2011-05-12 11:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 10:17 redoing SCM representation in 2.2 Andy Wingo
2011-05-12 11:12 ` nalaginrut [this message]
2011-05-12 12:50 ` Stefan Israelsson Tampe
2011-05-13 22:08 ` Mark H Weaver
2011-05-14 9:47 ` Andy Wingo
2011-05-15 9:02 ` Ken Raeburn
2011-05-15 15:35 ` Andy Wingo
2011-05-15 9:00 ` Ken Raeburn
2011-05-15 15:47 ` Andy Wingo
2011-05-15 20:43 ` Ken Raeburn
2011-05-16 9:40 ` Andy Wingo
2011-05-17 18:59 ` Mark H Weaver
2011-05-19 7:58 ` Ken Raeburn
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=1305198753.2392.5.camel@Renee-desktop \
--to=nalaginrut@gmail.com \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.com \
/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).