bug#5913: [PATCH] maint: ftruncate is always available, even without gnulib

2010-04-09 Thread Jim Meyering
FYI, I'll push this later today. In case you don't read the URL thread, note that for more than 3 years, anyone who builds coreutils on a system without ftruncate would get this message along with a failed configure: Your system lacks the ftruncate function. Please report this, along with

bug#5914: feature request and non-bug patches submit policy

2010-04-09 Thread jeff.liu
Hi Jim, I'd like to know if I should still submit new feature patches to here or coreut...@gnu.org. A few months ago, I found the heads up for the new coreut...@gnu.org mail list, and it mentioned only the bugs report/fix should be send to this list. Otherwise, for the general discussion and

bug#5914: feature request and non-bug patches submit policy

2010-04-09 Thread Pádraig Brady
On 09/04/10 10:28, jeff.liu wrote: > Hi Jim, > > I'd like to know if I should still submit new feature patches to here or > coreut...@gnu.org. > > A few months ago, I found the heads up for the new coreut...@gnu.org mail > list, and it mentioned > only the bugs report/fix should be send to this

bug#5912: [PATCH] dircolors: add rxvt-256color & rxvt-unicode256

2010-04-09 Thread Jim Meyering
Mike Frysinger wrote: > diff --git a/src/dircolors.hin b/src/dircolors.hin > index 6a4b1e3..511fb16 100644 > --- a/src/dircolors.hin > +++ b/src/dircolors.hin > @@ -38,9 +38,11 @@ TERM mach-color > TERM mlterm > TERM putty > TERM rxvt > +TERM rxvt-256color > TERM rxvt-cygwin > TERM rxvt-cygwin

bug#5914: feature request and non-bug patches submit policy

2010-04-09 Thread jeff.liu
Pádraig Brady wrote: > On 09/04/10 10:28, jeff.liu wrote: >> Hi Jim, >> >> I'd like to know if I should still submit new feature patches to here or >> coreut...@gnu.org. >> >> A few months ago, I found the heads up for the new coreut...@gnu.org mail >> list, and it mentioned >> only the bugs repo

bug#5914: feature request and non-bug patches submit policy

2010-04-09 Thread Sunil Mushran
jeff.liu wrote: Over the last few weeks I've been working on other projects (pretty must time dedicated to getting grep back into shape), so coreutils has languished. Sorry for not giving more feedback, but I have been watching. In fact, seeing the use of HAVE_FTRUNCATE that is moved by your pa

bug#5914: feature request and non-bug patches submit policy

2010-04-09 Thread Joel Becker
On Sat, Apr 10, 2010 at 12:00:10AM +0800, jeff.liu wrote: > one thing I need to point is, for OCFS2 reflink ioctl(2), it also has an > attributes preserve option could be specified explictly. > > I can implement it only when cp(1) invoked with '-p' option without conflict > to current `cp` > pres

bug#5775: [PATCH] doc: fix info to say cp -a does _not_ diagnose xattr failures

2010-04-09 Thread Pádraig Brady
On 26/03/10 11:53, Pádraig Brady wrote: > I was surprised that `cp --preserve=all file.xattr /dev/shm` produced no > warnings > In any case, this makes the docs match the behaviour. Actually some warnings could be output in this case so my patch is incorrect. The xattr/selinux diagnostics from cp

bug#5917: [PATCH] doc: mention Linux capabilities are maintained by cp/mv

2010-04-09 Thread Pádraig Brady
commit d047ee7da7f1b9a36ea34c7d064334900b15aac6 Author: Pádraig Brady Date: Sat Apr 10 01:05:39 2010 +0100 doc: mention Linux capabilities are maintained by cp/mv * doc/coreutils.texi (cp invocation): Mention that "Capabilities" are maintained when implemented using extended at