Dan Nicholson wrote:
> On Sat, Nov 20, 2010 at 8:48 AM, Julien Cristau
> wrote:
>> On Sat, Nov 20, 2010 at 08:16:23 -0800, Dan Nicholson wrote:
>>
>>> xserver master has this wrapped in a $cross_compiling test. What
>>> branch is this patch against?
>>>
>> It's against xfs, not xserver.
>
> If on
On Wed, Nov 24, 2010 at 02:56:32PM -0700, Matt Dew wrote:
> > But you also might want to consider that i was at a hardware vendor two
> > weeks ago, and i had to listen to their main engineer calling
> > contributing directly to X a waste of time, and that they rather fix
> > the versions their cus
On Thu, Nov 25, 2010 at 08:42:40AM +0100, Luc Verhaegen wrote:
> On Wed, Nov 24, 2010 at 08:34:21PM -0600, Pat Kane wrote:
> > > .. we can go forward with development & releases
> >
> > I agree. Since Adam and Daniel did the right thing and admitted to the
> > prank[1]
> > we can go forward wi
On Wed, Nov 24, 2010 at 08:34:21PM -0600, Pat Kane wrote:
> > .. we can go forward with development & releases
>
> I agree. Since Adam and Daniel did the right thing and admitted to the
> prank[1]
> we can go forward with a release.
>
> Pat
> ---
>
> [1] admitting to making a blunder is hard
On 11/24/2010 12:22 PM, Matt Turner wrote:
On Wed, Nov 24, 2010 at 1:18 PM, Pat Kane wrote:
What the deal with the "!!" operator? I read it as a double logical negation.
A NOOP, does it have some useful side effect?
It converts to bool, basically. I think it's kind of dirty.
It's the regula
On Thu, Nov 25, 2010 at 02:48:15PM +1000, Peter Hutterer wrote:
> The pad has an abswheel too, normalizing this into the rotation range
> screws the coordinates.
>
> Signed-off-by: Peter Hutterer
> ---
sorry, wrong list, this is a wacom patch.
Cheers,
Peter
> src/wcmCommon.c |8 ++--
On Wed, Nov 24, 2010 at 08:23:45PM -0600, Pat Kane wrote:
> Okay, with that info and if you could make the macro something like this:
>
> #define BitIsOn(ptr, bit) (!!(((BYTE *) (ptr))[(bit)>>3] & (1 <<
> ((bit) & 7 /* !! converts to boolean */
tbh, I'd rather not explain C constructs in co
The pad has an abswheel too, normalizing this into the rotation range
screws the coordinates.
Signed-off-by: Peter Hutterer
---
src/wcmCommon.c |8 ++--
src/wcmUSB.c|9 ++---
2 files changed, 8 insertions(+), 9 deletions(-)
diff --git a/src/wcmCommon.c b/src/wcmCommon.c
inde
On Wed, Nov 24, 2010 at 9:57 PM, Peter Hutterer
wrote:
> Signed-off-by: Peter Hutterer
> ---
> src/void.c | 8
> 1 files changed, 0 insertions(+), 8 deletions(-)
>
> diff --git a/src/void.c b/src/void.c
> index c741d87..2ed0082 100644
> --- a/src/void.c
> +++ b/src/void.c
> @@ -29,10
While I only recently discovered the -l option to build.sh, I find it
immensly helpful in building a set of protos and libraries for various
architectures/processors in a build root. The alternative is near
verbose a setup as building and installing every library and proto
from git manually, which
Require an xserver 1.9.99.1 or higher and put an ifdef in for ABI 12.
Signed-off-by: Peter Hutterer
---
configure.ac |2 +-
src/void.c | 36 ++--
2 files changed, 7 insertions(+), 31 deletions(-)
diff --git a/configure.ac b/configure.ac
index 855bbae..3a0
Signed-off-by: Peter Hutterer
---
src/void.c |6 --
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/src/void.c b/src/void.c
index e655d92..6b3bcaa 100644
--- a/src/void.c
+++ b/src/void.c
@@ -142,14 +142,16 @@ xf86VoidControlProc(DeviceIntPtr device, int what)
Signed-off-by: Peter Hutterer
---
src/void.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/src/void.c b/src/void.c
index 5764111..e655d92 100644
--- a/src/void.c
+++ b/src/void.c
@@ -238,7 +238,6 @@ _X_EXPORT InputDriverRec VOID = {
xf86VoidInit, /* pr
Not that it matters for this driver, but the axes are set up as absolute, so
label them accordingly.
Signed-off-by: Peter Hutterer
---
src/void.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/void.c b/src/void.c
index 74058d6..5764111 100644
--- a/src/void.c
+++
Signed-off-by: Peter Hutterer
---
configure.ac |2 +-
src/void.c | 101 +-
2 files changed, 2 insertions(+), 101 deletions(-)
diff --git a/configure.ac b/configure.ac
index 74e3f8b..855bbae 100644
--- a/configure.ac
+++ b/configure.a
Signed-off-by: Peter Hutterer
---
src/void.c |8
1 files changed, 0 insertions(+), 8 deletions(-)
diff --git a/src/void.c b/src/void.c
index c741d87..2ed0082 100644
--- a/src/void.c
+++ b/src/void.c
@@ -29,10 +29,6 @@
#include "config.h"
#endif
-#ifndef XFree86LOADER
-#include
> .. we can go forward with development & releases
I agree. Since Adam and Daniel did the right thing and admitted to the prank[1]
we can go forward with a release.
Pat
---
[1] admitting to making a blunder is hard to do, I know from personal
experience, so I
think both Adam and Daniel h
Okay, with that info and if you could make the macro something like this:
#define BitIsOn(ptr, bit) (!!(((BYTE *) (ptr))[(bit)>>3] & (1 <<
((bit) & 7 /* !! converts to boolean */
then:
Reviewed: Pat Kane
Pat
P.S. I love C, it is my favorite assembly code. -- PEK
On Wed, Nov 24,
The first (and last) time I tried to used build-from-tarballs script,
it did not work. My solution
was to just use the build.sh script and fix minor problems.
Reviewed: Pat Kane
On Wed, Nov 24, 2010 at 4:45 PM, Gaetan Nadon wrote:
> On Wed, 2010-11-24 at 15:43 -0500, Trevor Woerner wrote:
>
>
On Wed, 2010-11-24 at 17:42 -0800, Dan Nicholson wrote:
> On Wed, Nov 24, 2010 at 3:23 PM, Mark Kettenis
> wrote:
> >> From: Gaetan Nadon
> >> Date: Tue, 23 Nov 2010 09:34:29 -0500
> >>
> >> So far no one has claimed adding fPic is the correct way of creating a
> >> shared lib or
> >> that it i
On Wed, Nov 24, 2010 at 3:23 PM, Mark Kettenis wrote:
>> From: Gaetan Nadon
>> Date: Tue, 23 Nov 2010 09:34:29 -0500
>>
>> So far no one has claimed adding fPic is the correct way of creating a
>> shared lib or
>> that it is a necessary workaround to a situation libtool cannot handle
>> and that
Nothing requires the use of a C preprocessor
Using standard file exentions (.man) means no need for .gitignore
Use standard directory and makefile
Fix man page whitespace issues
Reviewed-by: Matt Dew
Signed-off-by: Gaetan Nadon
---
Second edition fixes 18 whitespace issues.
configure.
> From: Gaetan Nadon
> Date: Tue, 23 Nov 2010 09:34:29 -0500
>
> So far no one has claimed adding fPic is the correct way of creating a
> shared lib or
> that it is a necessary workaround to a situation libtool cannot handle
> and that it will
> work on all supported platforms.
There certainly a
Le 24/11/2010 23:41, Mark Kettenis a écrit :
> No. On OpenBSD, zlib is part of the base system and therefore there
> is no .pc file.
Xorg can't build without pkg-config. Can't you make the base system
install zlib's .pc file? We have good tools, let's use them.
Not that we can't do what Dan sugg
Mark Kettenis wrote:
>> Date: Sun, 21 Nov 2010 23:59:20 +0100
>> From: =?ISO-8859-1?Q?R=E9mi_Cardona?=
>>
>> Le 20/11/2010 07:04, Alan Coopersmith a �crit :
>>> # zlib
>>> -
>>> -AC_CHECK_LIB(z, gzclose)
>>> +AC_CHECK_HEADER([zlib.h], [],
>>> +AC_MSG_FAILURE([zlib.h is required t
On Wed, 2010-11-24 at 15:43 -0500, Trevor Woerner wrote:
> From: Trevor Woerner
>
> The build.sh script is able to perform builds from tarballs.
>
> Signed-off-by: Trevor Woerner
> ---
>
> It is my understanding that the build-from-tarballs script doesn't
> work.
> Personally I don't know sin
> Date: Sun, 21 Nov 2010 23:59:20 +0100
> From: =?ISO-8859-1?Q?R=E9mi_Cardona?=
>
> Le 20/11/2010 07:04, Alan Coopersmith a écrit :
> > # zlib
> > -
> > -AC_CHECK_LIB(z, gzclose)
> > +AC_CHECK_HEADER([zlib.h], [],
> > +AC_MSG_FAILURE([zlib.h is required to compile libfontenc]))
drago01 wrote:
> You pointed out the issue, we found out who did it, they apologized
> for doing so and revoked their root access.
>
> So what other actions do you want to be taken now?
If I may step in I suggest investing some time and developing some sort
of (formal) security concept. It's not
On Wed, Nov 24, 2010 at 5:32 PM, Peter Hutterer
wrote:
> assuming build.sh works with tarballs as you said (I haven't tried)
To clarify, I haven't tried either, I'm relying on reports from
others. But I will test this out and familiarize myself with the
process.
> Reviewed-by: Peter Hutterer
T
On Wed, Nov 24, 2010 at 03:43:51PM -0500, Trevor Woerner wrote:
> From: Trevor Woerner
>
> The build.sh script is able to perform builds from tarballs.
>
> Signed-off-by: Trevor Woerner
> ---
>
> It is my understanding that the build-from-tarballs script doesn't work.
> Personally I don't know
On Wed, Nov 24, 2010 at 12:18:16PM -0600, Pat Kane wrote:
> What the deal with the "!!" operator? I read it as a double logical negation.
> A NOOP, does it have some useful side effect?
http://stackoverflow.com/questions/1406604/what-does-the-operator-double-exclamation-point-mean-in-javascript
Simply returning the mask bit breaks checks like
BitIsOn(mask, 0) != BitIsOn(mask, 1);
as used in 048e93593e3f7a99a7d2a219e1ce2bdc9d407807.
The naming of this macro suggests that it should return boolean values
anyway. This patch also adds a few simple tests for these macros to make
sure they
> But you also might want to consider that i was at a hardware vendor two
> weeks ago, and i had to listen to their main engineer calling
> contributing directly to X a waste of time, and that they rather fix
> the versions their customers ship, and hand the patches to their
> customers directly, n
Gaetan Nadon wrote:
> Use "auto" rather than "try" for consistency with other modules.
> Update help string to mention default value.
> Unchanged: if configured --with-selinux and -lselinux is misisng,
> abort the configuration.
>
> Change HAVE_SELINUX to USE_SELINUX to be consistent with
> USE_PA
Gaetan Nadon wrote:
> Following a similar pattern to PAM and SELinux checks.
> Unchanged: if a user has requested the use of a random device
> and none can be found, the configuration aborts.
>
> Signed-off-by: Gaetan Nadon
> ---
> configure.ac | 43 +--
Gaetan Nadon wrote:
> Use "auto" rather than "try" for consistency with other modules.
> Update help string to mention default value.
> Unchanged: if configured --with-pam and -lpam is misisng,
> abort the configuration.
>
> Continue with USE_PAM rather than HAVE_PAM_OPEN_SESSION
> as we are check
So, wearing my X11R7.6 Release Manager hat, I am willing to accept
that the git repositories are not known to be compromised by an
outside actor, and that we can go forward with development & releases
as normal.
I had been quietly holding off on doing any more releases until the
issue was investig
From: Trevor Woerner
The build.sh script is able to perform builds from tarballs.
Signed-off-by: Trevor Woerner
---
It is my understanding that the build-from-tarballs script doesn't work.
Personally I don't know since I've never used it. The build.sh script has
been patched (thanks to the con
On Wed, Nov 24, 2010 at 1:18 PM, Pat Kane wrote:
> What the deal with the "!!" operator? I read it as a double logical negation.
> A NOOP, does it have some useful side effect?
It converts to bool, basically. I think it's kind of dirty.
___
xorg-devel
On Sun, 21 Nov 2010 14:27:51 -0500, Gaetan Nadon wrote:
> Gaetan Nadon (7):
> doc: HTML file generation: use the installed copy of xorg.css
> xmlrules.in: remove unrequired "@rm -f $@" from doc targets
> xmlrules.in: no need to setup xmlto flags when configuring
> --without-xmlto
> xm
On Wed, 24 Nov 2010 09:06:40 +1000, Peter Hutterer
wrote:
> Adam Jackson (1):
> linux: Fix CPU usage bug in console fd flushing
>
> Chase Douglas (2):
> Fix GPE Y axis scaling
> Fix transformAbsolute
>
> Dan Horák (1):
> XF86CONFIGDIR is undefined when built with --disa
On Mon, 15 Nov 2010 11:25:13 +1000, Peter Hutterer
wrote:
> + if (!scrp->monitor->maxPixClock && !specified) {
> +type = "default ";
> +scrp->monitor->maxPixClock = 65000.0;
> +}
Can you explain this part? Seems like this goes beyond changing the
default mode
> From: Thierry Vignaud
> Date: Tue, 16 Nov 2010 00:09:09 +0100
> On 15 November 2010 15:10, Dan Nicholson wrote:
> >> This patch selects nouveau by default for NVIDIA GPUs
> >> Also, don't treat DRI setup failure as an error for nouveau.
> >
> > Can you please split this patch in two parts since
On Fri, 5 Nov 2010 11:25:00 +0200, Pauli Nieminen
wrote:
> Pauli Nieminen (5):
> DRI2: Avoid call to NULL pointer
> DRI2: Add error message when working around driver bug
> DRI2: Add ReuseBufferNotify hook
> DRI2: Expose API to set drawable swap limit.
> DRI2: Allow
On Nov 23, 10 22:56:52 +, Alan Cox wrote:
> > It's on a separate branch, not master. (Doesn't mean it's right, just
> > that it's not actually going to cripple anything or waste time for anyone
> > who doesn't ask for it.)
>
> And how many other un-noticed commits did this person make ? Unti
What the deal with the "!!" operator? I read it as a double logical negation.
A NOOP, does it have some useful side effect?
On Wed, Nov 24, 2010 at 10:30 AM, walter harms wrote:
>
>
> Am 24.11.2010 07:25, schrieb Keith Packard:
>> On Wed, 24 Nov 2010 14:40:11 +1000, Peter Hutterer
>> wrote:
>
From: Luc Verhaegen
This change makes Xv support slightly less nice, but should, in itself,
not deteriorate things too much, as most drivers function acceptably
without reputimage.
Signed-off-by: Luc Verhaegen
---
configure.ac| 18 ++
src/apm_video.c |4
2 files
This patch is necessary for the patchset at:
http://lists.x.org/archives/xorg-devel/2010-November/014856.html
The reputimage hook is disabled when the updated API is used.
This course of action seems acceptable, as many drivers function
to some extent without a working reputimage hook.
Patch will
On Wed, Nov 24, 2010 at 5:12 PM, Luc Verhaegen wrote:
> On Wed, Nov 24, 2010 at 11:08:18AM -0500, Matt Turner wrote:
>>
>> >From the Phoronix forums, you say
>>
>> > Yeah, this was most definitely not a simple prank, as some people like to
>> > claim.
>>
>> What are you suggesting it was?
>
> Do
On Tue, Nov 02, 2010 at 08:05:46PM +0200, ville.syrj...@nokia.com wrote:
> Second installment of Xv reput changes.
>
> Patches 09-13 are new. Patch 14 was modified. The rest should be the
> same as before.
>
> ReputImage clipping should now match the behaviour of a regular
> XPutImage or a non-ov
Am 24.11.2010 07:25, schrieb Keith Packard:
> On Wed, 24 Nov 2010 14:40:11 +1000, Peter Hutterer
> wrote:
>
>> -#define BitIsOn(ptr, bit) (((BYTE *) (ptr))[(bit)>>3] & (1 << ((bit) & 7)))
>> +#define BitIsOn(ptr, bit) !!(((BYTE *) (ptr))[(bit)>>3] & (1 << ((bit) &
>> 7)))
>
bit is checked t
On Wed, Nov 24, 2010 at 11:08:18AM -0500, Matt Turner wrote:
>
> >From the Phoronix forums, you say
>
> > Yeah, this was most definitely not a simple prank, as some people like to
> > claim.
>
> What are you suggesting it was?
Do you really find this a simple prank? Or do you find this a flagra
On Wed, Nov 24, 2010 at 6:58 AM, Luc Verhaegen wrote:
> On Wed, Nov 24, 2010 at 08:27:12PM +1000, Peter Hutterer wrote:
>> On 24/11/10 19:38 , Luc Verhaegen wrote:
>>>
>>> Conspiracy theories?
>>
>> I did not imply that you were the one starting with the conspiracy
>> theories, and I think strictl
Eirik Byrkjeflot Anonsen wrote:
> 2. What systems do we have in place that enables us to detect "evil
>commits" once they actually make their way into the repository? What
>is the probability that they will be noticed? Can we do anything to
>increase this probability?
Distributed ver
On Wed, Nov 24, 2010 at 08:27:12PM +1000, Peter Hutterer wrote:
> On 24/11/10 19:38 , Luc Verhaegen wrote:
>>
>> Conspiracy theories?
>
> I did not imply that you were the one starting with the conspiracy
> theories, and I think strictly speaking there was no name-calling in
> that thread eithe
On Wed, Nov 24, 2010 at 11:18:20AM +, Alan Cox wrote:
>
> He ensured the problem was noticed, and that it got out to people who
> depend upon the repository being secure and properly managed. In this
> case that turns out to have ensured the offender admitted to something
> silly but if it had
> > See, this was exactly the problem here. It _was_ a freedesktop admin.
> > And it was pretty clear that it was that from the onset too. Mailing
> > fd.o admins, even if i could've dug up an email address in the split
> > second that i wrote the email (heck, i even mistyped repository), was
> > n
Hi,
I've been mostly offline whilst moving, so have only read this through
web archives. As mentioned on IRC earlier, it was my account used.
My apologies: as ajax said, it's indefensible, and am not really sure
what else to say. I've suspended my root accounts as well.
That being said:
On Wed
Luc,
I completely agree with you.
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: http://lists.x.org/mailman/listinfo/xorg-devel
On 24/11/10 19:38 , Luc Verhaegen wrote:
On Wed, Nov 24, 2010 at 06:33:19PM +1000, Peter Hutterer wrote:
On 24/11/10 18:00 , Eirik Byrkjeflot Anonsen wrote:
1. What systems do we have in place that enables us to detect when a
"trusted admin" acts in "bad judgement" or with "evil intent"?
On Wed, Nov 24, 2010 at 11:03 AM, Tim Beaulen wrote:
> Luc,
>
> I completely agree with you.
> ___
> x...@lists.freedesktop.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: http://lists.freedesktop.org/mailman/listinfo/xo
On Wed, Nov 24, 2010 at 06:33:19PM +1000, Peter Hutterer wrote:
> On 24/11/10 18:00 , Eirik Byrkjeflot Anonsen wrote:
>> 1. What systems do we have in place that enables us to detect when a
>> "trusted admin" acts in "bad judgement" or with "evil intent"? What
>> is the probability that su
>
> As far as I can see, all you've managed to do is to create a lot of
> noise about what is, in itself, a fairly minor incident. Yes, it is
> serious that a "trusted admin" abuses his powers. However, that happens
> and will continue to happen. Humans are like that. We often show a
> remarkab
On 24/11/10 18:00 , Eirik Byrkjeflot Anonsen wrote:
1. What systems do we have in place that enables us to detect when a
"trusted admin" acts in "bad judgement" or with "evil intent"? What
is the probability that such actions will be noticed? Can we do
anything to increase this prob
Luc Verhaegen writes:
> On Wed, Nov 24, 2010 at 04:36:17PM +1000, Dave Airlie wrote:
>> On Wed, Nov 24, 2010 at 4:31 PM, Luc Verhaegen wrote:
>> >
>> > See, this was exactly the problem here. It _was_ a freedesktop admin.
>> > And it was pretty clear that it was that from the onset too. Mailing
On Wed, Nov 24, 2010 at 06:01:19PM +1000, Dave Airlie wrote:
> On Wed, Nov 24, 2010 at 4:48 PM, Luc Verhaegen wrote:
> > On Wed, Nov 24, 2010 at 04:36:17PM +1000, Dave Airlie wrote:
> >> On Wed, Nov 24, 2010 at 4:31 PM, Luc Verhaegen wrote:
> >> >
> >> > See, this was exactly the problem here. It
On Wed, Nov 24, 2010 at 4:48 PM, Luc Verhaegen wrote:
> On Wed, Nov 24, 2010 at 04:36:17PM +1000, Dave Airlie wrote:
>> On Wed, Nov 24, 2010 at 4:31 PM, Luc Verhaegen wrote:
>> >
>> > See, this was exactly the problem here. It _was_ a freedesktop admin.
>> > And it was pretty clear that it was th
67 matches
Mail list logo
