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

Re: [Issue 659] New - The copy command should allow a rev

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2002-03-30 14:45:58 CET

issues@subversion.tigris.org writes:

> + This is probably a good place to start using the "@rev" extenstion. It would be
> + nice to allow specifying a revision for the copy command. E.g.:
> +
> + svn copy http://server/repo/trunk@54 http://server/repo/branches/my-branch
> +
> + Or, if the extension isn't wanted, do:
> +
> + svn copy -r 54 http://server.repo/trunk http://server/repo/branches/my-branch

Ummmmm, Ben? 'svn copy' has always taken a -r argument. We've
already used it to tag specific revisions...?

copy (cp): Duplicate something in working copy or repos, remembering history.
usage: svn copy SRC DST.

  SRC and DST can each be either a working copy (WC) path or URL:
    WC -> WC: copy and schedule for addition (with history)
    WC -> URL: immediately commit a copy of WC to URL
    URL -> WC: check out URL into WC, schedule for addition
    URL -> URL: complete server-side copy; used to branch & tag

Valid options:
  -m [--message] arg: specify commit message "ARG"
  -F [--file] arg: read data from file ARG
  -r [--revision] arg: specify revision number ARG (or X:Y range)
  --username arg: specify a username ARG
  --password arg: specify a password ARG

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Mar 30 14:47:08 2002

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