[PATCH] Replace spaces with tab on tests/Makefile.am

2011-02-19 Thread Gilles Espinasse
Signed-off-by: Gilles Espinasse g@free.fr --- tests/Makefile.am |6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/tests/Makefile.am b/tests/Makefile.am index 8aa56cd..9603441 100644 --- a/tests/Makefile.am +++ b/tests/Makefile.am @@ -27,7 +27,7 @@ root_tests =

git-version-gen headaches

2011-02-19 Thread Mike Frysinger
the current git-version-gen script and its usage in packages such as coreutils is causing me headaches wrt distros. it currently assumes one of two states: - the current tree is a valid git repo belonging to the related project - the current tree is not a git repo (all the way

Re: git-version-gen headaches

2011-02-19 Thread Jim Meyering
Mike Frysinger wrote: the current git-version-gen script and its usage in packages such as coreutils is causing me headaches wrt distros. it currently assumes one of two states: - the current tree is a valid git repo belonging to the related project - the current tree is not a git

Re: git-version-gen headaches

2011-02-19 Thread Mike Frysinger
On Saturday, February 19, 2011 14:49:32 Jim Meyering wrote: Jim Meyering wrote: Mike Frysinger wrote: further, some of the commands used in git-version-gen require write access to the .git repo (i.e. git update-index --refresh), which our package management tools flag as a violation

Re: [PATCH] Replace spaces with tab on tests/Makefile.am

2011-02-19 Thread Pádraig Brady
Pushed. thanks, Pádraig.

bug#8001: cp (8.10) sparse handling fails on compressed btrfs (cp/fiemap-2)

2011-02-19 Thread Pádraig Brady
On 19/02/11 18:28, Mike Frysinger wrote: based on other threads (which i havent been following too closely), did we settle on this being a btrfs bug ? -mike Nope, cp 8.10 is not absolved yet. It may be btrfs not honoring FIEMAP_FLAG_SYNC, and/or it may be cp needing to handle

bug#8079: rm command problem/suggestion

2011-02-19 Thread Jim Meyering
Thanks to all who replied. I'm closing this ticket.

bug#8081: sort -z and shuf -z don't work

2011-02-19 Thread Harald Dunkel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: coreutils Version: 8.10 Hi folks, According to the man page sort -z and shuf -z are supposed to end lines with 0 byte, not newline. This doesn't work. Example: % ( echo 1; echo 2; echo 3 ) | tac | sort -z | xargs -0 -L 1 echo xxx xxx 3 2

bug#8081: sort -z and shuf -z don't work

2011-02-19 Thread Eric Blake
On 02/19/2011 12:24 AM, Harald Dunkel wrote: Package: coreutils Version: 8.10 Hi folks, According to the man page sort -z and shuf -z are supposed to end lines with 0 byte, not newline. This doesn't work. Example: Thanks for the report, however this is not a bug. sort -z implies that

bug#8081: sort -z and shuf -z don't work

2011-02-19 Thread Jim Meyering
Harald Dunkel wrote: Package: coreutils Version: 8.10 Hi folks, According to the man page sort -z and shuf -z are supposed to end lines with 0 byte, not newline. This doesn't work. Example: % ( echo 1; echo 2; echo 3 ) | tac | sort -z | xargs -0 -L 1 echo xxx xxx 3 2 1 There are 3

bug#8001: cp (8.10) sparse handling fails on compressed btrfs (cp/fiemap-2)

2011-02-19 Thread Mike Frysinger
based on other threads (which i havent been following too closely), did we settle on this being a btrfs bug ? -mike signature.asc Description: This is a digitally signed message part.

bug#8001: cp (8.10) sparse handling fails on compressed btrfs (cp/fiemap-2)

2011-02-19 Thread Pádraig Brady
On 19/02/11 23:22, Pádraig Brady wrote: On 19/02/11 18:28, Mike Frysinger wrote: based on other threads (which i havent been following too closely), did we settle on this being a btrfs bug ? -mike Nope, cp 8.10 is not absolved yet. It may be btrfs not honoring FIEMAP_FLAG_SYNC, and/or it

bug#8001: cp (8.10) sparse handling fails on compressed btrfs (cp/fiemap-2)

2011-02-19 Thread Mike Frysinger
2011/2/19 Pádraig Brady: On 19/02/11 18:28, Mike Frysinger wrote: based on other threads (which i havent been following too closely), did we settle on this being a btrfs bug ? Nope, cp 8.10 is not absolved yet. It may be btrfs not honoring FIEMAP_FLAG_SYNC, and/or it may be cp needing to