I thought about using MIME type, but that adds additional issues like
storing the MIME type <-> file pattern mapping information, versioning
that, etc...
Additionally, the way Subversion currently records that a file is being
treated as binary tweaks the MIME type property. This seems completely
backwards, just set a property that says it's binary and get on with it.
Bill
> From: William Uther [mailto:will+@cs.cmu.edu]
>
> On 15/3/02 4:09 PM, "Bill Tutt" <rassilon@lyra.org> wrote:
>
> > Now we just need a spec for how you categorize input files so that
you
> > know which merge tool to run. How does the following sound for a
decent
> > start?
> >
> > The idea here is that the following checks would be performed in the
> > order listed:
> >
> > * Files based on a file pattern. (i.e. *.doc, *.xml, etc...)
> > * Text files invoking your standard text file 3-way merge resolution
UI.
>
> I'd prefer something that used the svn:mime-type property. Possibly
with
> a
> way to have the svn:mime-type automagically set (based on a file
pattern?)
> when you add a file.
>
> \x/ill :-}
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Mar 16 00:39:21 2002