From: Will Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] Pull request for branch x11r75patches
Date: Tue, 09 Mar 2010 23:01:19 +0000 [thread overview]
Message-ID: <4B96D33F.9010107@carallon.com> (raw)
In-Reply-To: <0D753D10438DA54287A00B027084269763682CDFC9@AUSP01VMBX24.collaborationhost.net>
On 09/03/2010 22:58, H Hartley Sweeten wrote:
> On Tuesday, March 09, 2010 3:50 PM, Will Wagner wrote:
>
>> I have setup a repository with my x11r7.5 changes merged into Paulius's
>> changes that have already been commited.
>>
>> Most just bump things to newer version, but also have converted mesa3d
>> to autotools and added more option support when building xserver.
>>
> Hello,
>
> Just an observation...
>
> Is it really necessary for the x11r7 packages to have the version information
> in the Config.in? I don't think any of the other packages show this in the
> help and it just adds more work when the versions get bumped. If a user
> "really" needs to know what the version is they can look at the associated
> *.mk file.
>
>
I would agree completely, updating all the Confin.in files was a real
time waster when updating x11. Guess I could generate new patches that
remove it if people are interested.
next prev parent reply other threads:[~2010-03-09 23:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 22:50 [Buildroot] Pull request for branch x11r75patches Will Wagner
2010-03-09 22:58 ` H Hartley Sweeten
2010-03-09 23:01 ` Will Wagner [this message]
2010-03-10 19:41 ` Thomas Petazzoni
2010-03-13 19:33 ` Paulius Zaleckas
2010-03-13 22:19 ` Will Wagner
2010-03-14 15:52 ` Paulius Zaleckas
2010-03-14 22:26 ` Will Wagner
2010-03-15 9:41 ` Paulius Zaleckas
2010-03-22 19:37 ` William Wagner
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=4B96D33F.9010107@carallon.com \
--to=will_wagner@carallon.com \
--cc=buildroot@busybox.net \
/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