From: David Masover <ninja@slaphack.com>
To: "Markus Törnqvist" <mjt@nysv.org>
Cc: reiserfs-list@namesys.com
Subject: Re: can't compile with reiser4
Date: Sat, 01 May 2004 13:59:12 -0500 [thread overview]
Message-ID: <4093F380.7040502@slaphack.com> (raw)
In-Reply-To: <20040501184545.GP29226@nysv.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
But the fix isn't in any snapshot. When is the next snapshot, or where
can I find the latest code?
Markus Törnqvist wrote:
| On Fri, Apr 30, 2004 at 06:10:09PM -0500, David Masover wrote:
|
|>glibc) on my system now either fail to install, continue trying to
|>install forever (make caught in an infinite loop), or install but don't
|
|
| This has been fixed.
|
| I have a copy of the patch here:
| http://mjt.nysv.org/reiser/tail.c.diff
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iQIVAwUBQJPzfngHNmZLgCUhAQKRlw//QNlUXloT9v4pjCr/+DNQhbZb0t3K4eod
h7fM1bs3RSlBgOZb8nNj8ajZCizsTrsQeNyxu93WrSIW/41q7MLRt/Ze5qVdDTtA
v46WzL0Xd4j6PoQqJIgUm9Gf32HWqFrppxeql4UNAehk2w9+SB/VeAoC6OpU4Q7F
DMe36+ANjmqD70lkaU13EMD0b0B+tA4S5KclICupP7jMZBEuzlPDCCXE/Dy17BUH
CEQOS3Apqt2PVqYhdRvZSeVcTcHi12z1JM0vVofc5FG9JRrHKGNuVirkebMCK7af
FLuHgTjbXXEkLwFIiaBJqT1whF7csGKyjce5VUA1PITGjafFLlElLoV1YPgvDm/D
AEmxiindJnubOobMHhdncRsCnjS28KWc5dpQ6qyX/u/zZVuvT2NQxdA3kuFLNtHW
fLrqZuWkFGT+RgCoq1HY1pRfj1zypykd/iOpsJuSvdMgVFSju67aoKtlqG2Nup+S
iF2U72BaEL+gIx2kMXJd2zPGXwMaWSbtvrwh0k607A8QZ/KEtyLaFP13lc7BRUS4
ThxNT6UYO2Xq6qRsky/25P+bHccUAz6r9TZNcKcINH5GwqFoXHqpv6GTaATqRTTQ
jPoW3d2t6/7Pd5CUtyPkppww2A3/eterdjyKY7Z9fpYt9WLQocL9HVRURaP2KICt
DVfJUzNqvgQ=
=VPsT
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-05-01 18:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-30 23:10 can't compile with reiser4 David Masover
2004-04-30 23:15 ` David Masover
2004-05-01 18:45 ` mjt
2004-05-01 18:59 ` David Masover [this message]
2004-05-01 19:09 ` mjt
2004-05-02 19:17 ` Hans Reiser
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4093F380.7040502@slaphack.com \
--to=ninja@slaphack.com \
--cc=mjt@nysv.org \
--cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.