[issue1116] Can encode/decode filters operate on actual files?

James Walker mercurial-bugs at selenic.com
Wed May 14 01:33:01 CDT 2008

New submission from James Walker <jamesw at frameforge3d.com>:

There seem to be two kinds of encode/decode filters, one that uses pipes and one 
that uses temporary files.  Couldn't the encode filter take the actual file in 
the working directory as input, rather than a temporary copy of it?  And 
couldn't the decode filter write the actual file?

The reason I ask is that I was wondering if the filter mechanism could handle 
the two-forked files that are sometimes used in the Mac OS's native file system.  
It looks like that can't work the way things are now, because the resource fork 
has been stripped off before the encode filter sees it.

messages: 6027
nosy: jwwalker
priority: feature
status: unread
title: Can encode/decode filters operate on actual files?

Mercurial issue tracker <mercurial-bugs at selenic.com>

More information about the Mercurial-devel mailing list