All of 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: Sun, 13 Nov 2005 22:16:03 +0100	[thread overview]
Message-ID: <87zmo8fdv0.fsf@student.han.nl> (raw)
In-Reply-To: <200511132106.37668.T.E.Baldwin99@members.leeds.ac.uk> (Timothy Baldwin's message of "Sun, 13 Nov 2005 21:06:31 +0000")

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

> Since having to edit 4 rmk files every time a system independent change is made
> is a bit silly, here is a patch to allow the common rules to be split off to
> a shared file.  I will submit a patch to do so later.
>
> Also I add ".DELETE_ON_ERROR:" to make make delete targets if there is an
> error building them.

Damn, we were talking about adding such feature today on IRC.  It's
nice to see that you did more than talking. :-)

It's just that I know very little about the build system, so I wait a
bit so people can comment on your patch.  It would be nice if you can
send in the patch that actually splits up the rmk files so I can see
why you made some changes in this patch.

Thanks,
Marco




  reply	other threads:[~2005-11-13 21:18 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 [this message]
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

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=87zmo8fdv0.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 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.