I have a .def file and a deploy.factor file remaining, uncommitted. I'm not
sure what to do with these two. The .def file can always be re-sourced from
the downloaded zip file. The deploy.factor is auto-generated during
deployment of the Tetris demo. I don't see why I should commit it. I don't
want to revert changes. So I'll just leave them in Unstaged Changes
forever.
I'm looking for a way to add the work directory to the repo, which seems
unaware of the changes that have occurred there.
I can check-out the origin code from the clean-branch deltas or do the
update using factor.cmd (as was done to build the first time). Are these
equivalent operations except for the building of Factor?
What is the difference between checking-out, fetching, and updating?
Because fetching doesn't touch the repo working directory, I assume that
checking-out and updating are very similar (both copy code to the working
directory.)
The GUI seems to say that you use fetches only to synchronize this clone
with the original clone, and check-outs to place actual code from previously
fetched code (a compressed code file I guess) into the working directory.
Is this correct?
Shaping
------------------------------------------------------------------------------
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
_______________________________________________
Factor-talk mailing list
Factor-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/factor-talk
