From: phcoder <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Removing autogenerated files from svn
Date: Sun, 12 Apr 2009 13:47:49 +0200 [thread overview]
Message-ID: <49E1D4E5.5030908@gmail.com> (raw)
Hello, we all know how annoying are these autogenerated files. We could
remove it. The main argument against it is that people will not be able
to compile without installing a lot of developement tools. It changes
nothing for the users wanting to modify the code. So I propose to remove
these files but in compensation setup a nightly build server. I'm ready
to supply all necessary scripts to create a source tar.gz with
autogenerated files, binary tar.gz and rescue iso for all platforms
where applicable.
--
Regards
Vladimir 'phcoder' Serbinenko
next reply other threads:[~2009-04-12 11:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-12 11:47 phcoder [this message]
2009-04-12 18:29 ` Removing autogenerated files from svn Colin D Bennett
2009-04-12 20:54 ` Pavel Roskin
2009-04-13 14:30 ` Robert Millan
2009-04-14 15:35 ` Yoshinori K. Okuji
2009-04-14 16:12 ` Felix Zielcke
2009-04-14 13:50 ` Jordi Mallach
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=49E1D4E5.5030908@gmail.com \
--to=phcoder@gmail.com \
--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.