I hashed out a patch for mv which is more or less the opposite of the
--symbolic-link option for cp. Instead of creating symlinks on the
destination before the copy, it creates symlinks on the source after the
move.
Most of the code was copied from the cp.c and copy.c code. There is one
On Fri, 5 Nov 2004, Brendan Byrd/SineSwiper wrote:
Also, I have a question about how files are moved. Currently, all files
are copied to a new diskspace, and then the old diskspace is removed.
Only when the file is moving across filesystem boundaries.
Try this to see how mv usually behaves:
$
Brendan Byrd/SineSwiper [EMAIL PROTECTED] writes:
I hashed out a patch for mv which is more or less the opposite of the
--symbolic-link option for cp. Instead of creating symlinks on the
destination before the copy, it creates symlinks on the source after
the move.
Before we talk about the
hi
i think this could be a bug - could because the man-page doesn't say much
about if excluding is done before including, but have a look at this
[EMAIL PROTECTED]:# du -ksc --exclude=original* *
4 archfoto.sh
5048_backup
826156 big
76 copyright
196976 cover
136 cover.log
4
sorry - i have to post this to [EMAIL PROTECTED]
On Fri, 5 Nov 2004, karl s. eiringer wrote:
hi
i think this could be a bug - could because the man-page doesn't say much
about if excluding is done before including, but have a look at this
[EMAIL PROTECTED]:# du -ksc --exclude=original* *
4
karl s. eiringer wrote:
i think this could be a bug - could because the man-page doesn't say much
about if excluding is done before including, but have a look at this
Thank you for your report. I tried to reproduce this with the current
5.2.1 by this method.
[EMAIL PROTECTED]:~$ mkdir
hmm - sorry i passed on the whole thing to debian - cause the stable
version uses du in version 4.1 which has the bug, the unstable version
with du in version 5.2 is correct...
sorry to bother you
greetings
karl.
On Fri, 5 Nov 2004, Bob Proulx wrote:
karl s. eiringer wrote:
i think this could
karl s. eiringer [EMAIL PROTECTED] writes:
(it seems that original is excluded first, but '*' includes the
directories [original + subdirs] again)
Yes, that's right. The documentation says that --exclude applies only
when recursing; it doesn't apply to the top-level command-line
arguments.
I installed the following patch to fix some problems with GNU sort,
where it misbehaves badly with large inputs that caused integer
overflow or unchecked stack overflow.
Some of the uses of size_t aren't strictly necessary, since the
indexes are bounded above by NMERGE or by argc, but I thought
Paul Eggert wrote:
karl s. eiringer [EMAIL PROTECTED] writes:
(it seems that original is excluded first, but '*' includes the
directories [original + subdirs] again)
Yes, that's right. The documentation says that --exclude applies only
when recursing; it doesn't apply to the top-level
10 matches
Mail list logo