On Fri, 25 Jan 2013 14:14:20 +0100, Gilles
<[email protected]> wrote:
>What about switching to another branch (eg. going from trunk to
>experimental), and simply running "fossil ls"? Will that list the
>revisions without touching the files in my work directory?
I notice that "fossil update experimental -n" doesn't say which work
files will be replaced by what's in the "experimental" branch in the
repo ("1 file modified."):
===========
UPDATE dummy.c
-------------------------------------------------------------------------------
updated-to: 80ebe786997e4fc943bbc2d9564f8bb727e81675 2013-01-11
16:36:56 UTC
tags: experimental
comment: Testing branches (user: Fred)
changes: 1 file modified.
===========
Generally speaking, I find running "update" followed by commands to
list which files/revisions are available and their contents (ls,
timeline, finfo, etc.) a bit dangerous. It'd be coold if there were a
simple way to list files/revisions in a branch without actually
checking out anything into the work directory.
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
