[prev in list] [next in list] [prev in thread] [next in thread]
List: subversion-issues
Subject: [Issue 659] New - The copy command should allow a rev
From: issues () subversion ! tigris ! org
Date: 2002-03-30 5:36:05
[Download RAW message or body]
http://subversion.tigris.org/issues/show_bug.cgi?id=659
*** shadow/issues_15/659 Fri Mar 29 21:36:05 2002
--- shadow/issues_15/659.tmp.29243 Fri Mar 29 21:36:05 2002
***************
*** 0 ****
--- 1,27 ----
+ +============================================================================+
+ | The copy command should allow a rev |
+ +----------------------------------------------------------------------------+
+ | Issue #: 659 Component: subversion |
+ | Status: NEW Version: current |
+ | Resolution: Platform: All |
+ | Issue type: ENHANCEMENT OS/Version: All |
+ | Priority: P3 Subcomponent: src |
+ +----------------------------------------------------------------------------+
+ | Assigned To: issues@subversion.tigris.org |
+ | Reported By: benmcollins@tigris.org |
+ | CC list: Cc: |
+ +----------------------------------------------------------------------------+
+ | Milestone: TargetMilestone: --- |
+ | URL: |
+ +============================================================================+
+ | DESCRIPTION |
+ 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
+
+ The rev would have to apply to the first argument, always of course.
\ No newline at end of file
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic