Re: Optional text base design discussion?

[Brandon Ehle]
> Has there ever been a design discussion on how to implement optional
> text base working copies?

So here's what I think would need to happen:

- Eliminate any assumptions about when a text-base file should always
  exist. And don't assume that, for example, a file must be newly
  added if it doesn't have a text-base. I have no idea if the latter
  assumption exists anywhere.

- If a text-base file is needed and does not exist, I guess create it
  using svn_ra.

- Check for two text-base filenames, with and without .gz, and if
  *.text-base.gz is found, stream it through zlib.

- Commands like 'merge' and 'rm' need to move the old copy of the file
  to a text-base if it doesn't already exist.

And the UI:

- New flag for 'svn co', 'svn ci' and 'svn up' to indicate desire for
  missing or compressed text-bases.

- New svn subcommand to add a text-base to an unmodified file, in
  anticipation of modifying the file. Of course, thanks to eol-style
  and keywords, this may be more than a simple file copy.

> Single .svn directory (database?) for the entire working copy
> * Could be combined with compressed or missing text bases

That issue has little or nothing to do with missing/compressed
text-bases.