On 7/13/2011 12:33 PM, Brian Cottingham wrote:
> Yep, that does the trick. I'd seen the update command but didn't realise this
> was its purpose.
Well, its purpose is to switch the current checkout/rev to any other revision,
so switching between branches is just a special case of that. With the common
case of
f pull ; f update
to bring external changes on the current branch into the current workspace.
% f help update
Usage: fossil update ?VERSION? ?FILES...?
Change the version of the current checkout to VERSION. Any uncommitted
changes are retained and applied to the new checkout.
[...]
>
> Should fossil close/open behave differently from fossil update? Is this a bug
> in Fossil, or is it deliberate?
That question will have to be answered by Richard, I believe.
>
>
> On Wed, Jul 13, 2011 at 3:20 PM, Andreas Kupries <andre...@activestate.com
> <mailto:andre...@activestate.com>> wrote:
>
> On 7/13/2011 12:14 PM, Tomek Kott wrote:
> > I think the issue is that "fossil close" doesn't clear out the
> directory, and
> > "fossil open" I only overwrites files from the opened checkout, but
> does not
> > delete any files. So if you were to issue "fossil extras" my guess is
> file2
> > would be in that list.
>
> To change branches it is not necessary to 'close' the workspace.
> Just do
>
> fossil update <branchname>
>
> That will properly remove/add/update the files in the workspace.
>
> >
> > Tomek
> >
> > On Wed, Jul 13, 2011 at 2:55 PM, Brian Cottingham <spiffyt...@gmail.com
> <mailto:spiffyt...@gmail.com>
> > <mailto:spiffyt...@gmail.com <mailto:spiffyt...@gmail.com>>> wrote:
--
Andreas Kupries
Senior Tcl Developer
ActiveState, The Dynamic Language Experts
P: 778.786.1122
F: 778.786.1133
andre...@activestate.com
http://www.activestate.com
Get insights on Open Source and Dynamic Languages at www.activestate.com/blog
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
