You are managing interaction between three places, and I'm not great on
using the best words, so listen for the themes as I explain my working metal
model for git :) . A) The remote place, B) your local git version of that,
and C) your physical file layout. Commands like fetch work between A and B,
and you will need different commands to merge from B to C. Most of the time
you are working between B and C - for example, commit. When working with
your own repository for work, you use words push and pull to move between A
and C through B. As I am not working to change my factor official code, I
can issue the pull commands which gets the source git repos into both B and
C.
So a pull is a fetch plus a check-out (populating the git compressed
database file and the working directory.
If I had made some changes to C and committed them to B, no problem. If I
have some edits in C, git will be unwilling to do anything for me, and
wisely so.
... until you commit them.
If you have a personal git host somewhere, and there are free ones, try
making two clones of the same little folder
I thought one clones only a repo.
and try moving changes back and forth through A to and from B/C and B'/C'.
You are suggesting that I clone A twice, first as B and then as B'. There
will be a separate working directory (C and C') associated with each new Git
compressed database.
This is roughly the same as interacting with a community, except that you
are completely in charge. When working with the community, you have to
submit requests for pulls rather than pushing, unless you are core.
I thought I could pull anything, but only push what has been vetted.
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
