Re: [Flightgear-devel] git clone -l question and observations

2011-02-06 Thread Curtis Olson
Ok, I think I figured this out. The clue was in the error message I posted. I had the branch in question checked out in my main repository clone, so the system couldn't push changes from my --local clone of the branch back into that branch in the primary clone. I guess that makes some sort of se

Re: [Flightgear-devel] git clone -l question and observations

2011-02-06 Thread Curtis Olson
No one has answered yet which makes me guess (a) I didn't ask very well or (b) no one knows the answer, so let me try again here. I created a local clone of my fgdata repository using the --local option which builds hard links to the master original repository and saves lots of space. The clone r

[Flightgear-devel] git clone -l question and observations

2011-02-05 Thread Curtis Olson
Here locally I made a local clone of the fgdata repository using "git clone -l fgdata fgdata-wip". That seemed to work as advertised. I noticed that the only branch available in the new local clone "fgdata-wip" is the branch that is active in fgdata at the time the clone is made that's good