From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: revision control of `configure'
Date: Sun, 13 Jan 2008 20:57:43 +0100 [thread overview]
Message-ID: <200801132057.43222.okuji@enbug.org> (raw)
In-Reply-To: <87bq7pha7e.fsf@xs4all.nl>
On Sunday 13 January 2008 19:06, Marco Gerards wrote:
> Pavel Roskin <proski@gnu.org> writes:
> > On Tue, 2008-01-08 at 12:57 +0100, Robert Millan wrote:
> >> http://cvs.savannah.gnu.org/viewvc/grub2/configure?root=grub&view=log
> >>
> >> Does it make sense to keep `configure' under revision control? Almost
> >> every commit for unrelated things tends to change the whole thing.
> >
> > I suggested it in the days of GRUB 1 but my suggestion didn't get any
> > support.
>
> Personally, I do not care much. It's annoying to make sure unwanted
> changed slip in. I have no strong opinion, but would prefer it is not
> under revision control.
We should keep it. The concept is that the user should be able to build and
test the trunk without installing too many development tools.
Nowadays, we don't use any cutting-edge features, so this might be not that
important. But when we used Automake in GRUB Legacy, we had to deploy some
features present only in newer versions of Automake, so the version
requirement was very severe. This made the lives of testers uncomfortable.
Okuji
prev parent reply other threads:[~2008-01-13 19:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 11:57 revision control of `configure' Robert Millan
2008-01-09 21:59 ` Pavel Roskin
2008-01-13 18:06 ` Marco Gerards
2008-01-13 19:57 ` Yoshinori K. Okuji [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=200801132057.43222.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.