Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Subversion Wiki" for 
change notification.

The "Aachen2017" page has been changed by JulianFoad:
https://wiki.apache.org/subversion/Aachen2017?action=diff&rev1=7&rev2=8

  
  === ... ===
  
+ === SVN Client Plug-in Commands ===
+ 
+ Requirement: Upload my current changes, or shelved changes, to a code review 
system such as Rietveld.
+ 
+ Rietveld provides the 
[[https://github.com/rietveld-codereview/rietveld/wiki/upload.py-Usage|upload.py]]
 script for this, to be run in a Subversion (or other) WC. For Mercurial, there 
is the [[https://bitbucket.org/nicoe/hgreview/|hgreview plug-in]] which makes 
the command "hg review [...]".
+ 
+ We could of course release a version of Svn with an initial (experimental) 
"review" subcommand to do this, but a plug-in has advantages of (1) able to 
release independently; (2) if it is useful only for users who have a review 
server, other users don't need to see it.
+ 
+ Advantage (1) also applies to certain other feature developments including 
shelving.
+ 
+ Solution: We could pretty easily hack up plug-in top-level subcommands. 
Inspiration from hg and git. The plug-in script would have access to at least 
the command-line 'svn'. We might want to promise one or more of our bindings 
are available to it too. We might do some argument pre-processing, such as 
expanding "^/" notation, before passing to the plug-in.
+ 
  === View Specs ===
  
- Requirement (Johan): export the sparse configuration of one WC and make 
another one match it.
+ Requirement (Johan): Export the sparse configuration of one WC and make 
another one match it.
  
  Solution (Bert): We can use the WC-state 'Reporter' to find all the info we 
need -- including depth changes, switched URLs (if wanted), and mixed revisions 
(if wanted) -- and write this to a simple text format output. For a first hack, 
the output format could even be a series of "svn update --set-depth=..." lines 
which could be executed directly by a shell, avoiding the need to write any 
parse-and-execute code at all.
  

Reply via email to