On 2012-04-27, at 7:13 AM, Dave Chinner wrote:
> Have a look at fs/xfs/xfs_dinode.h. There's a bunch of flags defined
> at the bottom of the file.
>
> Stuff like the "nodefrag", "nodump", and "prealloc" bits seem fairly
> generic - they are for indicating that files are to be avoided for
> defrag
On 2012-04-26, at 7:06 PM, Dave Chinner wrote:
> On Thu, Apr 19, 2012 at 03:05:58PM +0100, David Howells wrote:
>>
>> Implement a pair of new system calls to provide extended and further
>> extensible stat functions.
>>
>> The second of the associated patches is the main patch that provides thes
On Fri, Apr 27, 2012 at 11:13:06PM +1000, Dave Chinner wrote:
> Right now it is, but there's ben patches in the past to introduce
> project quotas to ext4. That didn't go far because it was done in a
> way that was semantically different to XFS (for no reason that I
> could understand) and nobody w
On Fri, Apr 27, 2012 at 10:39:05AM +0100, David Howells wrote:
> Dave Chinner wrote:
>
> > If we are adding per-inode flags, then what do we do with filesystem
> > specific
> > flags? e.g. XFS has quite a number of per-inode flags that don't align with
> > any other filesystem (e.g. filestream a
Dave Chinner wrote:
> If we are adding per-inode flags, then what do we do with filesystem specific
> flags? e.g. XFS has quite a number of per-inode flags that don't align with
> any other filesystem (e.g. filestream allocator, real time file, behaviour
> inheritence flags, etc), but may be usef
Andreas Dilger wrote:
> > However, since there is a remote file ID, we could add an
> > XSTAT_INFO_FILE_ID flag to indicate there's a standard xattr holding this.
>
> It is a bit strange that the kernel would return a flag that was not
> requested, but not fatal.
On the other hand, if it costs
On Fri, Apr 27, 2012 at 1:35 PM, Lucas Zawacki wrote:
> When I first started to learn about wine development I stumbled across
> some examples exactly like these in the wine wiki. A quick search
> reveals them (the first 3)
> http://wiki.winehq.org/DeveloperExamples?action=fullsearch&context=180&v
When I first started to learn about wine development I stumbled across
some examples exactly like these in the wine wiki. A quick search
reveals them (the first 3)
http://wiki.winehq.org/DeveloperExamples?action=fullsearch&context=180&value=debugging
I myself like this aproach, it's a very useful
I'm bringing a new intern up to speed, and while I was
showing him how to diagnose one particular wine bug,
I recorded the session on a web page,
http://kegel.com/wine/bug30486.html
It occurred to me that recorded sessions like that
might be useful to other beginners (above and
beyond the more str
On Sat, Apr 14, 2012 at 21:57, Bruno Jesus <00cp...@gmail.com> wrote:
> Based on original patch from Christian Lupien from bug 8226.
>
> Tests required to later fix http://bugs.winehq.org/show_bug.cgi?id=8226
Is there anything else I could provide in helping to get this patch accepted?
http://sou
Am 26.04.2012 22:22 schrieb "Józef Kucia" :
> MSDN says that dwPitchOrLinearSize is DWORD in the DDS_HEADER. Also,
> the same definition is used in a D3D sample. On the other hand, we can
> define it as LONG to be safe.
Nah, no need in that case. But I recommend to write tests for invalid
pitches
11 matches
Mail list logo
