search for: pullabl

Displaying 8 results from an estimated 8 matches for "pullabl".

Did you mean: pullable
2014 Aug 27
1
[PATCH 0/6] chain.c32 patches
...t;> with Ady - backport missing patches from 6.x to 5.x and 4.x so all >> versions >> have up to date chain version. > > So any yes/no regarding those patches or maybe aim at some different > approach ? > If you want to backport, it would be best if you could provide a pullable git tree with the backport. I simply don't have any time to spend on the older branches anymore. -hpa
2008 Dec 12
4
[PATCH 1/1] COM32: lua - enable (parts of) liolib
Hi again, the attached patch (re-)enables parts of lua's liolib.c, especially io.write() for formatted output (similar to printf() ): Example: -- define printf() function printf = function(s,...) return io.write(s:format(...)) end -- function printf("Hallo, this is hex %04x\n", 64321) Bye, Marcel -------------- next part -------------- A non-text
2014 Aug 27
0
[PATCH 0/6] chain.c32 patches
On 2014-06-29 21:41, Michal Soltys wrote: > This small set fixes few bugs, improves gpt handling (under buggy conditions) > and implements strict flag with more fine grained control which should fix > issues with sanity checks against disk sizes. > > If this set is allright I'd want to do what I mentioned in older discussion > with Ady - backport missing patches from 6.x to
2005 May 13
4
Asterisk - fax - spandsp
Dear all I have a Asterisk server (version 1.0.7) running with a TE110P card on a 3Ghz P4 machine (running nothing else but asterisk) So far so good. Today I was trying to receive faxes using spandsp fax client. I used spandsp v0.0.2pre18 (which compiled against libtiff 3.5.7) It compiled fine, installed fine, run fine. But when sending a fax (from a Brother fax machine) the image received
2008 Mar 17
0
[PATCH] Attempt to rewrite the description of the filter parameters in rsyncd.conf.yo.
...avoid misleading people to think that they can't have different parameters for different modules. --- I'm hoping everything I wrote here is complete and correct and I didn't lose any information compared to the previous version, but this could use some serious review. The change is pullable from branch "wip" of my repository at: http://mattmccutchen.net/rsync/rsync.git/ Matt rsyncd.conf.yo | 85 +++++++++++++++++++++++++------------------------------ 1 files changed, 39 insertions(+), 46 deletions(-) diff --git a/rsyncd.conf.yo b/rsyncd.conf.yo index f17e3d5..9e36f79...
2012 Oct 25
46
[RFC] New attempt to a better "btrfs fi df"
...ow btrfs was using the disks. A my first attempt was to develop a new command which shows how the disks are divided in chunks. However it still was no clear. Then I realised that I need to merge the two output. Below the results. It shows how the disks is used by the different chunks. The code is pullable from http://cassiopea.homelinux.net/git/btrfs-progs-unstable.git branch info-cmd I don''t publish the patched because aren''t in a good shape. However I really like the output. The example is a filesystem based on three disks of 3GB. It is clear that: - - RAID0 us...
2014 Jun 29
10
[PATCH 0/6] chain.c32 patches
This small set fixes few bugs, improves gpt handling (under buggy conditions) and implements strict flag with more fine grained control which should fix issues with sanity checks against disk sizes. If this set is allright I'd want to do what I mentioned in older discussion with Ady - backport missing patches from 6.x to 5.x and 4.x so all versions have up to date chain version. Michal
2012 Feb 13
10
[RFB] add LZ4 compression method to btrfs
...57760 -> 131060567 61.8% lzo 2.06 1x_1 = 639305 us ( 331 MB/s) 470840 us ( 450 MB/s) 211957760 -> 100576151 47.5% * snappy 1.0.4 svn r58 * snappy-c as Andi sent it to mailinglist * lzo 2.0.6 1x_1 variant * lz4 r55 (r54 + bugfix in the hash table entry type) * compiled by gcc 4.7, -O2 pullable from: git://repo.or.cz/linux-2.6/btrfs-unstable.git dev/compression-squad david -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html