Name

svk log — Display commit log messages.

Synopsis

svk log DEPOTPATH
svk log PATH

Description

The default target is the path of your current directory. If no arguments are supplied, svk log shows the log messages for all files and directories inside of (and including) the current working directory of your working copy. You can refine the results by specifying a path, one or more revisions, or any combination of the two. The default revision range for a local path is BASE:1.

If you specify a DEPOTPATH alone, then it prints log messages for everything that the DEPOTPATH contains. The default revision range for a URL is HEAD:1.

With --verbose, svk log will also print all affected paths with each log message. With --quiet, svk log will not print the log message body itself (this is compatible with --verbose).

Note

Logs do not follow copy history by default. Use --cross to enable following of copy history.

Alternate Names

None

Changes

Nothing

Accesses Depot

Yes

Accesses Mirrored Repository

No

Switches

--revision (-r) REV
--limit (-l) NUM
--quiet (-q)
--cross (-x)
--verbose (-v)

Examples

You can see the log messages for all the paths that changed in your working copy by running svk log from the top:

$ svk log
----------------------------------------------------------------------
r20:  harry | 2005-07-19 10:43:54 -0700

Tweak.
----------------------------------------------------------------------
r17:  sally | 2005-07-19 10:35:41 -0700
…

Examine all log messages for a particular file in your working copy:

$ svk log foo.c
----------------------------------------------------------------------
r32:  sally | 2005-07-19 11:43:13 -0700

Added defines.
----------------------------------------------------------------------
r28:  sally | 2005-07-19 11:48:33 -0700
…

If you don't have a working copy handy, you can log a DEPOTPATH:

$ svk log //test/foo.c
----------------------------------------------------------------------
r32:  sally | 2005-07-19 11:43:13 -0700

Added defines.
----------------------------------------------------------------------
r28:  sally | 2005-07-19 11:48:33 -0700
…

Tip

If you run svk log on a specific path and provide a specific revision and get no output at all

$ svk log --revision 20 //untouched.txt
----------------------------------------------------------------------

That just means that the path was not modified in that revision. If you log from the top of the repository, or know the file that changed in that revision, you can specify it explicitly:

$ svk log --revision 20 touched.txt 
----------------------------------------------------------------------
r20:  harry | 2005-07-19 10:43:54 -0700

Tweak.
----------------------------------------------------------------------

Sometimes you might not care about the log messages themselves, but just about the meta information. To only display a one line header for each revision use the --quiet (-q) switch to svk log:

$ svk log --quiet //test/foo.c
----------------------------------------------------------------------
r32:  sally | 2005-07-19 11:43:13 -0700
----------------------------------------------------------------------
r28:  sally | 2005-07-19 11:48:33 -0700
----------------------------------------------------------------------
…