[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: CVS update: subversion/subversion/client README TODO

From: Karl Fogel <kfogel_at_collab.net>
Date: 2001-04-13 19:51:21 CEST

fitz@tigris.org writes:
> Log:
> Much delayed checkin from the Apache Hackathon. Still mulling through the README, so don't think it's finished.

Yay! Thanks Fitz.

> -If you want to see the milestone 1 client in action, run "make check"
> -in this directory. That runs the tests/svn-test.sh script, which you
> -ca examine for details of piping to and from xml files.
> +If you want to see the milestone 2 client in action, run "make check"
> +in this directory. That runs the tests/svn-test.sh script, which
> +tests the basic functionality of the client (but which is also
> +woefully out of date as we have not yet decided on a test suite).

Note that Ben is writing a test suite (see
subversion/tests/clients/cmdline/) to replace the shell scripts in
client/tests/. So pretty soon, or perhaps already, even the above new
text will be obsolete.

> +* subversion will never muck up your file with conflict markers. When
> + you update a file that contains conflicts, subversion will first
> + apply all changes that are non-conflicting, then the conflicting
> + changes (just the failed hunks in patch format) will be written into
> + a reject file. You will not be able to check in the file in question
> + until you have removed the reject file (It is tracked in the entries
> + file). For example, if your file is named foo.c, the reject file
> + will be named foo.c.8734XNIS2989.rej.

Thank you for describing this here; a number of people have asked
about it.

> * .svnfiletypespecifics file. SVN will implement basic .cvswrapper
> functionality (only that related to file types determined by regular
> - expressions. This may happen in .svnfiletypespecifics or in
> + expressions). This may happen in .svnfiletypespecifics or in
> .svnrc. TODO SURVEY

I'm beginning to think we want a ~/.svn/ directory, like ~/.netscape/,
maybe?

> Fitz TODO:
>
> - Fix the ability to delete properties.
> -- Once over cmds, check args against README and get cleaning
> +- Once over cmds, check args against README and get cleaning.
> +
> +- Implement:
> + --verbose and its variations.
> + --date
> + --local-dir (non-recursive)
> + --recursive
> + --stdout
> + --dry-run
> + --no-rc (of course, we have to implement the whole reading of .svnrc) :)
> + --editor
> +
> - Document cmd structure
> - Dive into commit and checkout in libsvn_client

Looks good.

-K
Received on Sat Oct 21 14:36:28 2006

This is an archived mail posted to the Subversion Dev mailing list.