11.07.2015 Views

Version Control with Subversion - Login

Version Control with Subversion - Login

Version Control with Subversion - Login

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Repository AdministrationOne exception to these rules about subcommands is the svnlook youngest subcommand,which takes no options and simply prints out the repository's youngest revision number:$ svnlook youngest /var/svn/repos19$Keep in mind that the only transactions you can browse are uncommittedones. Most repositories will have no such transactions because transactionsare usually either committed (in which case, you should access them as revision<strong>with</strong> the --revision (-r) option) or aborted and removed.Output from svnlook is designed to be both human- and machine-parsable. Take, as anexample, the output of the svnlook info subcommand:$ svnlook info /var/svn/repossally2002-11-04 09:29:13 -0600 (Mon, 04 Nov 2002)27Added the usualGreek tree.$The output of svnlook info consists of the following, in the order given:1. The author, followed by a newline2. The date, followed by a newline3. The number of characters in the log message, followed by a newline4. The log message itself, followed by a newlineThis output is human-readable, meaning items such as the datestamp are displayed usinga textual representation instead of something more obscure (such as the number of nanosecondssince the Tastee Freez guy drove by). But the output is also machine-parsable—becausethe log message can contain multiple lines and be unbounded in length,svnlook provides the length of that message before the message itself. This allows scriptsand other wrappers around this command to make intelligent decisions about the log message,such as how much memory to allocate for the message, or at least how many bytesto skip in the event that this output is not the last bit of data in the stream.svnlook can perform a variety of other queries: displaying subsets of bits of informationwe've mentioned previously, recursively listing versioned directory trees, reporting whichpaths were modified in a given revision or transaction, showing textual and property differencesmade to files and directories, and so on. See the section called “svnlook” for a fullreference of svnlook's features.svndumpfilterWhile it won't be the most commonly used tool at the administrator's disposal, svndumpfilterprovides a very particular brand of useful functionality—the ability to quickly and easilymodify streams of <strong>Subversion</strong> repository history data by acting as a path-based filter.The syntax of svndumpfilter is as follows:133

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!