On Jul 26, 2006, at 12:33, Talden wrote:
> It might be nice lthough to be able to mark files for inclusion in a
> commit-set or allow commit to accept a file (or stdin) of paths/files
> to commit so that deeply distant files and large checkins don't mean
> unbelievably large commandlines - or have I overlooked something there
> too.
Yes, we have that too! :-) Check out the --targets option:
$ echo some/path/to/file1.txt > targets.txt
$ echo a/path/to/another/file2.txt >> targets.txt
$ svn ci --targets targets.txt -m "Committing those two files"
$ rm targets.txt
$ svn help ci
commit (ci): Send changes from your working copy to the repository.
usage: commit [PATH...]
A log message must be provided, but it can be empty. If it is not
given by a --message or --file option, an editor will be started.
If any targets are (or contain) locked items, those will be
unlocked after a successful commit.
Valid options:
-q [--quiet] : print as little as possible
-N [--non-recursive] : operate on single directory only
--targets arg : pass contents of file ARG as additional
args
--no-unlock : don't unlock the targets
-m [--message] arg : specify commit message ARG
-F [--file] arg : read data from file ARG
--force-log : force validity of log message source
--editor-cmd arg : use ARG as external editor
--encoding arg : treat value as being in charset
encoding ARG
--username arg : specify a username ARG
--password arg : specify a password ARG
--no-auth-cache : do not cache authentication tokens
--non-interactive : do no interactive prompting
--config-dir arg : read user configuration files from
directory ARG
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jul 26 13:25:41 2006