From: David Woodhouse <dwmw2@infradead.org>
To: miguel@cetuc.puc-rio.br
Cc: mtd@infradead.org, Ciro Cattuto <ciro@prosa.it>
Subject: Re: GRUB on DOC: 2Mb issues
Date: Thu, 31 Aug 2000 17:20:48 +0100 [thread overview]
Message-ID: <14431.967738848@passion.cygnus.co.uk> (raw)
In-Reply-To: <151C6E876B0@mamao.cetuc.puc-rio.br>
miguel@cetuc.puc-rio.br said:
>
> Well, I will not have time to do it in the next few days anyway.
> But maybe Ciro will want to implement it.
>
I just committed it - it's working on 512-byte devices. I see no reason why
it shouldn't work on 256-byte devices if I copied Ciro's code correctly.
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2000-08-31 16:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-28 16:50 GRUB on DOC: 2Mb issues Ciro Cattuto
2000-08-28 22:24 ` Miguel Freitas
2000-08-30 8:57 ` David Woodhouse
2000-08-30 13:46 ` Miguel Freitas
2000-08-30 15:07 ` David Woodhouse
2000-08-30 14:23 ` Miguel Freitas
2000-08-31 16:20 ` David Woodhouse [this message]
2000-08-31 23:10 ` Ciro Cattuto
2000-08-30 15:47 ` Ciro Cattuto
2000-08-30 16:31 ` David Woodhouse
2000-08-30 16:39 ` David Woodhouse
2000-08-30 14:21 ` Ciro Cattuto
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=14431.967738848@passion.cygnus.co.uk \
--to=dwmw2@infradead.org \
--cc=ciro@prosa.it \
--cc=miguel@cetuc.puc-rio.br \
--cc=mtd@infradead.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