Grub Development Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Support for including *.mk files
Date: Fri, 18 Nov 2005 15:58:11 +0100	[thread overview]
Message-ID: <87hdaa3svw.fsf@student.han.nl> (raw)
In-Reply-To: <200511181414.21113.T.E.Baldwin99@members.leeds.ac.uk> (Timothy Baldwin's message of "Fri, 18 Nov 2005 14:14:11 +0000")

Timothy Baldwin <tim.lists@majoroak.f2s.com> writes:

> You forgot the first patch (genmk.diff), also Okuji's latest commit conflicts 
> with it.  So here it is all together.

Oh, I thought genmk2.diff replaced genmk.diff. :-)

Committed.

Thanks,
Marco




      reply	other threads:[~2005-11-18 14:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-13 21:06 Support for including *.mk files Timothy Baldwin
2005-11-13 21:16 ` Marco Gerards
2005-11-15 22:13   ` Timothy Baldwin
2005-11-16  6:49     ` Marco Gerards
2005-11-17 19:25       ` Timothy Baldwin
2005-11-17 19:30         ` Marco Gerards
2005-11-18 10:58           ` Yoshinori K. Okuji
2005-11-18 13:47         ` Marco Gerards
2005-11-18 14:14           ` Timothy Baldwin
2005-11-18 14:58             ` Marco Gerards [this message]

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=87hdaa3svw.fsf@student.han.nl \
    --to=metgerards@student.han.nl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox