From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: pushing out a new xfsprogs release, was Re: [PATCH] xfsprogs: fix unaligned access in libxfs
Date: Sun, 30 Aug 2009 10:44:03 +0200 [thread overview]
Message-ID: <200908301044.03807@zmi.at> (raw)
In-Reply-To: <4A99D43D.5050208@sandeen.net>
On Sonntag 30 August 2009 Eric Sandeen wrote:
> Afraid I haven't fixed that one yet, sorry. If you could open a bug
> on xfs.org's bugzilla it'd be much better for tracking ...
OK, looked there, but there are only 2 links: to kernel.org or
oss.sgi.com bugzillas. Which one should I use?
BTW, wouldn't it be better to declare on the Wiki which bugzilla to use?
> I did find that building xfsprogs w/o debug ASSERTs turned on, I
> could get a clean fs after 2 runs, just to get you going again...
What would I need to take out exactly? Sorry, I don't know what "debug
ASSERTs" are. I've seen from patches sent here those are commands, but
which ones are for debug?
mfg zmi
--
// Michael Monnerie, Ing.BSc ----- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net Key-ID: 1C1209B4
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-08-30 8:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 15:37 [PATCH] xfsprogs: fix unaligned access in libxfs Christoph Hellwig
2009-08-28 17:15 ` Eric Sandeen
2009-08-28 18:24 ` pushing out a new xfsprogs release, was " Christoph Hellwig
2009-08-28 21:20 ` Felix Blyakher
2009-08-29 22:17 ` Michael Monnerie
2009-08-30 1:22 ` Eric Sandeen
2009-08-30 8:44 ` Michael Monnerie [this message]
2009-08-28 21:39 ` Alex Elder
2009-08-28 22:15 ` Christoph Hellwig
2009-08-28 22:38 ` Alex Elder
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=200908301044.03807@zmi.at \
--to=michael.monnerie@is.it-management.at \
--cc=xfs@oss.sgi.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