rmuschall wrote:
Jamie Webb <[EMAIL PROTECTED]> wrote:
What's the alternative? Make Darcs encoding-aware? I suspect that
IMHO yes. I.e.
darcs add foo.c
tries to check in foo.c as ASCII if it can verify that it is ASCII,
[snip]
Changing the content-type or content-transfer-encoding would need to
be treated like a patch.
Just to make sure you're all aware (most of you probably are), darcs
does not store metadata for a file. That is, the statement 'file foo.c
is under darcs as an ASCII file' (as opposed to binary or UTF-8) is
meaningless. The only thing one can say is that after a certain set of
patches, file foo.c contains a certain sequence of bytes, which may
happen to be valid ASCII/UTF-8/ELF/etc. (And this sequence of bytes is
the same regardless whether one uses the repository on Windows or UNIX.)
However, a *patch* can currently be a textual line-based patch (where
lines end in '\n' characters), or a binary patch. Which kind of patch
is created depends on the contents of the old and new versions of a
file: if these contain 0-bytes or similar bytes that are typically not
text, then darcs generates a binary patch.
Ralf, I'm not sure what you intended above, but it seems you're talking
about file metadata. So to prevent confusion I just wanted to clarify
that that doesn't currently exist, to help the discussion.
Groetjes,
<><
Marnix
_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users
