From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: grub fails to tftp a file with more than 64K blocks
Date: Thu, 15 Apr 2004 13:37:28 +0200 [thread overview]
Message-ID: <200404151337.28895.okuji@enbug.org> (raw)
In-Reply-To: <C28780ABC637504896EB86B4FB75FFBF98C0D5@MAANDMBX1.ets.enterasys.com>
On Wednesday 14 April 2004 04:39, Guzovsky, Eduard wrote:
> Grub version 0.94 with (or without) "grub-0[1].94-diskless-1.patch"
> fails to tftp a file with more than 64K blocks. Bellow is a fix. Note
> that the bug exists in buf_fill() function.
Thanks for your contribution, but this is not the right place to send
your patch. grub-devel is used for GRUB 2 but not for GRUB legacy.
bug-grub is used for patches against GRUB legacy instead.
This time, I accept your patch here, but please use bug-grub rather than
grub-devel from now on.
Also, I'd like you to read the instructions on how to send patches in
the manual. It should say that:
1. Unified format is desirable as a diff format.
2. Reverse patches are not good.
3. You should write a ChangeLog entry for your change.
Okuji
next prev parent reply other threads:[~2004-04-15 11:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-14 2:39 grub fails to tftp a file with more than 64K blocks Guzovsky, Eduard
2004-04-15 11:37 ` Yoshinori K. Okuji [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-15 15:22 Guzovsky, Eduard
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=200404151337.28895.okuji@enbug.org \
--to=okuji@enbug.org \
--cc=grub-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 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.