Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

svk::command::log(3) [osx man page]

SVK::Command::Log(3)					User Contributed Perl Documentation				      SVK::Command::Log(3)

NAME

       SVK::Command::Log - Show log messages for revisions

SYNOPSIS

	log DEPOTPATH
	log PATH
	log -r N[:M] [DEPOT]PATH

OPTIONS

	-r [--revision] ARG	 : ARG (some commands also take ARG1:ARG2 range)

				 A revision argument can be one of:

				 "HEAD"       latest in repository
				 {DATE}       revision at start of the date
				 NUMBER       revision number
				 NUMBER@      interpret as remote revision number
				 NUM1:NUM2    revision range

				 Unlike other commands,  negative NUMBER has no
				 meaning.

	-l [--limit] REV       : stop after displaying REV revisions
	-q [--quiet]	       : Don't display the actual log message itself
	-x [--cross]	       : track revisions copied from elsewhere
	-v [--verbose]	       : print extra information
	   --xml	       : display the log messages in XML format
	   --filter FILTER     : select revisions based on FILTER
	   --output FILTER     : display logs using the given FILTER

DESCRIPTION

       Display the log messages and other meta-data associated with revisions.

       SVK provides a flexible system allowing log messages and other revision properties to be displayed and processed in many ways.  This
       flexibility comes through the use of "log filters."  Log filters are of two types: selection and output.  Selection filters determine which
       revisions are included in the output, while output filters determine how the information about those revisions is displayed.  Here's a
       simple example.	These two invocations produce equivalent output:

	   svk log -l 5 //local/project
	   svk log --filter "head 5" --output std //local/project

       The "head" filter chooses only the first revisions that it encounters, in this case, the first 5 revisions.  The "std" filter displays the
       revisions using SVK's default output format.

       Selection filters can be connected together into pipelines.  For example, to see the first 3 revisions with log messages containing the
       string 'needle', we might do this

	   svk log --filter "grep needle | head 3" //local/project

       That example introduced the "grep" filter.  The argument for the grep filter is a valid Perl pattern (with any '|' characters as '|' and
       '' as '\').  A revision is allowed to continue to the next stage of the pipeline if the revision's log message matches the pattern.  If
       we wanted to search only the first 10 revisions for 'needle' we could use either of the following commands

	   svk log --filter "head 10 | grep needle" //local/project
	   svk log -l 10 --filter "grep needle" //local/project

       You may change SVK's default output filter by setting the SVKLOGOUTPUT environment.  See svk help environment for details.

       Standard Filters

       The following log filters are included with the standard SVK distribution:

	   Selection : grep, head, author
	   Output    : std, xml

       For detailed documentation about any of these filters, try "perldoc SVK::Log::Filter::Name" where "Name" is "Grep", "Head", "XML", etc..
       Other log filters are available from CPAN <http://search.cpan.org> by searching for "SVK::Log::Filter".	For details on writing log
       filters, see the documentation for the SVK::Log::Filter module.

perl v5.10.0							    2008-08-04						      SVK::Command::Log(3)

Check Out this Related Man Page

SVK::Command::Info(3)					User Contributed Perl Documentation				     SVK::Command::Info(3)

NAME

       SVK::Command::Info - Display information about a file or directory

SYNOPSIS

	info [PATH | DEPOTPATH]...

OPTIONS

	-R [--recursive]       : descend recursively

DESCRIPTION

       For example, here's the way to display the info of a checkout path:

	% svk info ~/dev/svk
	Checkout Path: /Users/gugod/dev/svk
	Depot Path: //svk/local
	Revision: 447
	Last Changed Rev.: 447
	Last Changed Date: 2006-11-28
	Copied From: /svk/trunk, Rev. 434
	Merged From: /svk/trunk, Rev. 445

       You can see the result has some basic information: the actual depot path, and current revision. Next are advanced information about copy
       and merge source for this depot path.

       The result of "svk info //svk/local" is almost the same as above, except for the "Checkout Path:" line is not there, because you are not
       referring to a checkout path.

       Note that the revision numbers on "Copied From:" and "Merged From:" lines are for the source path (//svk/trunk), not the target path
       (//svk/local).  The example above state that, //svk/local is copied from the revision 434 of //svk/trunk, and //svk/local was merged from
       the revision 445 of //svk/trunk.  Hence if you do a "svk log -r 434 //svk/local", svk would tell you that //svk/local does not exist at
       revision 434.

       So far there is no easy way to tell the actual revision number of //svk/local right after a copy or merge.

       If the target is a depot path, or the corresponding depot path of the target checkout path is actually a mirroring path, the output of this
       command will look like this:

	% svk info //svk/trunk
	Depot Path: //svk/trunk
	Revision: 447
	Last Changed Rev.: 445
	Mirrored From: svn://svn.clkao.org/svk, Rev. 1744

       So you can see this depot path is mirrored from a remote repository, and so far mirrored up to revision 1744.

perl v5.10.0							    2008-08-04						     SVK::Command::Info(3)
Man Page