From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Remove conf/*.mk from svn
Date: Sun, 27 Jul 2008 03:17:26 -0400 [thread overview]
Message-ID: <1217143046.16601.43.camel@ct> (raw)
In-Reply-To: <488A1E3C.7030108@t-online.de>
On Fri, 2008-07-25 at 20:41 +0200, Christian Franke wrote:
> I agree, the files generated by ./autogen.sh should be included in
> tarball, but not in the repo.
> Additional prerequisites (autoconf, ruby) for builds from svn are IMO OK.
I agree.
At least we should put a message into *.mk files that would make it
clear that they are generated.
> BTW: autogen.sh should "touch stamp-h.in" to be consistent with the
> Makefile rule for config.h.in.
What difference would it make?
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-07-27 7:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 5:17 Linking Viswesh S
2008-07-25 5:35 ` Linking Pavel Roskin
2008-07-25 15:18 ` Remove conf/*.mk from svn (was: Re: Linking) Colin D Bennett
2008-07-25 18:41 ` Remove conf/*.mk from svn Christian Franke
2008-07-27 7:17 ` Pavel Roskin [this message]
2008-07-27 22:28 ` Christian Franke
2008-07-28 22:43 ` Pavel Roskin
2008-08-05 10:38 ` Marco Gerards
2008-07-25 20:43 ` Remove conf/*.mk from svn (was: Re: Linking) Robert Millan
2008-07-31 20:18 ` Yoshinori K. Okuji
2008-08-05 10:40 ` Remove conf/*.mk from svn Marco Gerards
2008-08-05 15:38 ` Vesa Jääskeläinen
2008-08-05 15:48 ` Marco Gerards
2008-08-05 12:02 ` Seeking for the start administrador02032
2008-08-05 15:55 ` Remove conf/*.mk from svn Felix Zielcke
2008-08-05 18:41 ` Javier Martín
2008-08-05 18:51 ` Colin D Bennett
-- strict thread matches above, loose matches on Subject: below --
2008-08-06 4:58 Viswesh S
2008-08-06 14:56 ` Vesa Jääskeläinen
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=1217143046.16601.43.camel@ct \
--to=proski@gnu.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.