From: Sergey Matveychuk <sem@ciam.ru>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: GRUB2: *BSD and more patch
Date: Sat, 20 Mar 2004 00:56:30 +0300 [thread overview]
Message-ID: <405B6C8E.8070108@ciam.ru> (raw)
In-Reply-To: <87ish0cy4z.fsf@marco.marco-g.com>
Marco Gerards wrote:
> If you want to fix it this way, it would be better to check for the
> existence of memalign using autoconf IMHO.
Hmm. OK :)
>
>
>>>BTW, have you signed a copyright assignment for GRUB? I'm sorry, but
>>>I don't remember well. If not, I'd like you to do that.
>>
>>A new patch with a few fixes for inherited from fsys_ffs.c bugs is
>>testing now. I publish it within a few days.
>
>
> Do you mean for GRUB 2? Please keep us up-to-date what you are doing
> to prevent people from doing double work.
No. Okuji means GRUB1 UFS2 patch I think. Okiji, am I right? :)
>
>
>>diff -ruN grub2/ChangeLog grub2.devel/ChangeLog
>
>
> Can you please make a patch using the -p argument as well? In that
> case it is visible which function was changed.
OK.
>>+ * util/i386/pc/biosdisk.c: Add *BSD stuff.
>
>
> Can you please be more clear here? It would be better to notice
> everything you changed and added.
I'll do it.
Johan Rydberg wrote:
> : + if (strncmp ("/dev/sd", path, 7) == 0 || strncmp ("/dev/hd",
path, 7) == 0 ||
> : + strncmp ("/dev/ad", path, 7) == 0 || strncmp ("/dev/wd",
path, 7) == 0)
>
> Doesn't the GCS say that lines should be broken before operators? Not
> a biggie, but anway.
>
Are you agree with it?
--
Sem.
next prev parent reply other threads:[~2004-03-19 21:59 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 8:15 GRUB2: *BSD and more patch Sergey Matveychuk
2004-03-18 12:31 ` Yoshinori K. Okuji
2004-03-19 21:24 ` Sergey Matveychuk
2004-03-19 21:34 ` Johan Rydberg
2004-03-19 21:42 ` Marco Gerards
2004-03-19 21:56 ` Sergey Matveychuk [this message]
2004-03-19 22:22 ` Marco Gerards
2004-03-19 23:24 ` Sergey Matveychuk
2004-03-19 23:55 ` Marco Gerards
2004-03-20 0:45 ` Sergey Matveychuk
2004-03-20 10:29 ` Jeroen Dekkers
2004-03-20 18:30 ` Sergey Matveychuk
2004-03-20 19:43 ` Marco Gerards
2004-03-21 1:17 ` Sergey Matveychuk
2004-03-21 1:45 ` Marco Gerards
2004-03-21 2:18 ` Sergey Matveychuk
2004-03-21 3:30 ` Marco Gerards
2004-03-21 16:11 ` Yoshinori K. Okuji
2004-03-22 8:20 ` Sergey Matveychuk
2004-03-22 13:49 ` Yoshinori K. Okuji
2004-03-22 14:26 ` Jeroen Dekkers
2004-03-22 15:23 ` Yoshinori K. Okuji
2004-03-22 21:05 ` Sergey Matveychuk
2004-03-22 22:03 ` Sergey Matveychuk
2004-03-22 22:10 ` Sergey Matveychuk
2004-09-01 22:00 ` Marco Gerards
2004-09-02 10:50 ` Yoshinori K. Okuji
2004-09-05 9:26 ` Marco Gerards
2004-09-07 10:46 ` Yoshinori K. Okuji
2004-12-29 17:27 ` Marco Gerards
2005-01-11 13:32 ` Yoshinori K. Okuji
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=405B6C8E.8070108@ciam.ru \
--to=sem@ciam.ru \
--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.