The other implication here is that it would be extremely handy to have
multiple branches checked out simultaneously for other reasons. git makes
branching easy, yes, but if you find yourself bouncing between branches with
changes for separate projects, and external events may require you to jump
to a different branch at a moments notice, It's a major PITA to have to
commit every little thing you are in the middle of to switch to another
branch.
This is like having to completely clean up your desk before you can work on
a new task, and then clean it up again completely before you can jump to the
next. I just don't work like that, I bounce between about 12 desktops, 40
browser tabs, multiple coding projects.
And then when someone pushes something to the remote repository, you have to
clean up the desk again, switch to the master branch, do a pull, and then
individually switch to each of your local branches and do a merge. Tedious
to say the least, and intrusive to the continuity of my work flow! I know
where everything is on my desk ... if you make me clean it up and put it all
away 10 times a day ... yeah I have a spotless desk, but I can't actually
get anything done!
Hope that didn't sound too much like a vent, still trying to figure out how
to merge the git view of the world with my own, and I'm still not entirely
happy. :-)
I'll definitely have to checkout the local checkout feature. Do we
understand the branching/merging nuances in this case? Will I need to do a
git pull in the master branch for each locally cloned repository or will the
hard links ensure that a git pull in one repository is reflected in all the
others ... no I suppose not, since the local clones are clones of the first
repository ... we'll probably need to still do individual git pulls in each
of them (from the master branch) to update them ... so still lots of branch
switching and manual fiddling to maintain these local branches. Hmmm.....
Curt.
On Tue, Jan 25, 2011 at 3:16 PM, Anders Gidenstam
<anders-...@gidenstam.org>wrote:
> On Tue, 25 Jan 2011, Curtis Olson wrote:
>
> > Once you get it all figured out, please let us know how, so we can get
> setup
> > correctly too. :-)
>
> I'm not sure this counts as figuring it all out.. :)
>
> anders@sleipner:/opt/FlightGear$ du -sk fgdata
> 7930604 fgdata
> anders@sleipner:/opt/FlightGear$ git clone -l fgdata fgdata-test
> Cloning into fgdata-test...
> done.
> anders@sleipner:/opt/FlightGear$ du -sk fgdata fgdata-test/
> 7930604 fgdata
> 4614988 fgdata-test/
>
> After checking out the 2.2.0 branch in fgdata-test:
>
> anders@sleipner:/opt/FlightGear$ du -sk fgdata fgdata-test
> 7934896 fgdata
> 691112 fgdata-test
>
> A drawback is that the second clone fetches from the first so one would
> need to keep the first uptodate to get the latest commits in the second
> clone. It might be possible to set up fetch and branch tracking to avoid
> that. I'm not sure what happens if both clones fetch new commits from
> gitorious - probably that will lead to duplicate files (fetching from the
> first to the second local repro hopefully doesn't).
>
> Both repositories need to be on the same partition since
> filesystem hardlinks are used.
>
> The use of hardlinks also open up for some confusing du results -
> depending on in which order the files are attributed to directories. :)
>
> anders@sleipner:/opt/FlightGear$ du -sk fgdata/.git fgdata-test/.git
> 3252104 fgdata/.git
> 4992 fgdata-test/.git
> anders@sleipner:/opt/FlightGear$ du -sk fgdata-test/.git fgdata/.git
> 3246288 fgdata-test/.git
> 10808 fgdata/.git
>
>
> Cheers,
>
> Anders
> --
> ---------------------------------------------------------------------------
> Anders Gidenstam
> WWW: http://www.gidenstam.org/FlightGear/
>
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better
> price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
--
Curtis Olson:
http://www.atiak.com - http://aem.umn.edu/~uav/
http://www.flightgear.org -
http://www.flightgear.org/blogs/category/curt/<http://www.flightgear.org/blogs/category/personal/curt/>
------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
