On Sat, Aug 06, 2005 at 09:03:33AM +0100, Phil Brooke wrote: > --- David Roundy <[EMAIL PROTECTED]> wrote: > > > - Once a binary file, always a binary file. I.e., if there are any > > > binary patches for a file, it's binary. > > Wrong. A file can go back and forth between being binary and text. > > Ah, okay. > > Does that apply to files that with names matching a regexp in > _darcs/prefs/binaries?
Yeah, you can always modify _darcs/prefs/binaries... and a coworker may have a different _darcs/prefs/binaries, which doesn't list the file as binary. > Is there a simple way to determine if a file is binary for a particular > operation (e.g., record)? Is it simply the presence of hex 00 or hex > 1a in the working directory or _darcs/current? The easiest way would be to run darcs whatsnew, assuming the file has been modified. (i.e. darcs whatsnew | grep binary) If a file hasn't been modified then its state on a record isn't really defined, since no patches are being generated. -- David Roundy http://www.darcs.net _______________________________________________ darcs-users mailing list [email protected] http://www.abridgegame.org/mailman/listinfo/darcs-users
