Re: CVS HEAD out of date

On Sat, Oct 08, 2005 at 01:30:21PM +0200, Andreas Metzler wrote: > Hello, > It looks like most recent changes to findutils have been made to > branch rel-4-2-fixes, with CVS HEAD being completely out of date > (especially with respect to documentation). Should patches be made > against the branch?

Plans for findutils 4.3.x

Hello all, As you will have noticed, findutils 4.2.26 was recently released and was mainly a bugfix release. For some time now I have been trying to stabilise the 4.2.x releases, prioritising bugfixes and avoiding large changes. However, a large change has been waiting in the wings for quite a w

[bug #14842] Incorrect "Cannot allocate memory" error in some cases.

Follow-up Comment #2, bug #14842 (project findutils): James, please update lib/savedir.c (and lib/getcwd.c as well) from gnulib. ___ Reply to this item at: _

[bug #14556] find.1 manpage still refers to "-perm +mode" instead of "-perm /mode"

Follow-up Comment #4, bug #14556 (project findutils): Done; in fact there were some other cases too (in find.1, locate.1 and xargs.1) which I took care of. ___ Reply to this item at:

[bug #11668] [wishlist] FreeBSD extensions for time specification.

Follow-up Comment #2, bug #11668 (project findutils): I added getdate.[chy] from the coreutils to the lib directory and came up with the patch attached. It should implement my own suggestion. ___ Additional Item Attachment: File name: adat

[bug #14921] find -fstype broken when bind-mounts are used

Follow-up Comment #4, bug #14921 (project findutils): jay wrote in comment #3 > Is this affected by the fix to bug #14922 ? Nope, this still applies to 4.2.26. argenau:/usr/share/doc/findutils# /tmp/findutils-4.2.26/find/find -printf '%F\n' | sort -u ext3 argenau:/usr/share/doc/findutils# mount

[bug #14556] find.1 manpage still refers to "-perm +mode" instead of "-perm /mode"

Follow-up Comment #3, bug #14556 (project findutils): Hej, could you throw in the dash-escaping, as per comment#2? s_-4000_\-4000_ thanks, cu andreas ___ Reply to this item at: