On Fri, Jul 18, 2014 at 06:30:05AM +0200, Achim Gratz wrote:
>Christopher Faylor writes:
>> git isn't ready yet unfortunately. Can't you just download a recent
>> snapshot? That should be good enough.
>
>I can download and install snapshots just fine. I'm running snapshots
>for quite some time a
Greetings, Achim Gratz!
>> git isn't ready yet unfortunately. Can't you just download a recent
>> snapshot? That should be good enough.
> I can download and install snapshots just fine. I'm running snapshots
> for quite some time already so there'd be nothing new on that front.
>> FWIW, CVS i
Christopher Faylor writes:
> git isn't ready yet unfortunately. Can't you just download a recent
> snapshot? That should be good enough.
I can download and install snapshots just fine. I'm running snapshots
for quite some time already so there'd be nothing new on that front.
> FWIW, CVS is blo
On Thu, Jul 17, 2014 at 09:43:40PM +0200, Achim Gratz wrote:
>Corinna Vinschen writes:
>> Netapp inode numbers are not reliable and thus the number of links isn't
>> either. There's a check in Cygwin which is the result of the early
>> Cygwin 1.7 development. It does not report the number of hard
Corinna Vinschen writes:
> Netapp inode numbers are not reliable and thus the number of links isn't
> either. There's a check in Cygwin which is the result of the early
> Cygwin 1.7 development. It does not report the number of hardlinks
> and it fakes the inode numbers on netapp filesystems.
Ah
On Jul 17 20:09, Achim Gratz wrote:
>
> I have come across an interesting problem with the link count on a
> NetApp volume(*). While hardlinks can be created just fine and work as
> you'd expect (changing one file changes all the linked files), the link
> count that gets reported for each of the
6 matches
Mail list logo