[EMAIL PROTECTED] said:
> Wouldn't it be cool to have an extended attribute for files called
> "Copy on Write", so then you could hardlink all duplicate files
> together, but when a file is modified a copy is transparently created.
> The only problem I see with this is that you wouldn't have eno
Jeremy Jackson wrote:
> Padraig Brady wrote:
>
>> Hmm.. useful until you actually want to modify a linked file,
>> but then your modifying the file in all "merged" trees.
>> Wouldn't it be cool to have an extended attribute
>> for files called "Copy on Write", so then you could
>> hardlink all d
On Mon, Mar 05, 2001 at 07:17:18PM +, Padraig Brady wrote:
> Hmm.. useful until you actually want to modify a linked file,
> but then your modifying the file in all "merged" trees.
Use emacs, because you can configure it to do something
appropriate with linked files. But for those of us addi
Padraig Brady wrote:
> Hmm.. useful until you actually want to modify a linked file,
> but then your modifying the file in all "merged" trees.
> Wouldn't it be cool to have an extended attribute
> for files called "Copy on Write", so then you could
> hardlink all duplicate files together, but whe
Hmm.. useful until you actually want to modify a linked file,
but then your modifying the file in all "merged" trees.
Wouldn't it be cool to have an extended attribute
for files called "Copy on Write", so then you could
hardlink all duplicate files together, but when a file is
modified a copy is t
Good day, all,
Sorry for the offtopic post; I sincerely believe this will be
useful to developers with multiple copies of, say, the linux kernel tree
on their drives. I'll be brief. Please followup to private mail -
thanks.
Freedups scans the directories you give it for identical
6 matches
Mail list logo
