The git repo on gitorious doesn't have all the history from svn, which makes it
somewhat painful to retrace old changes. My local git-svn repo was way better
in that regard. Is there a way to redo the repo from svn, doctor the transition
from old to new svn (berlios to gna) to give continuous histo
#2294: Units turn to green color wreck
+--
Reporter: |Type: bug
j0shdrunk0nwar|Priority: minor
Status: new | Component: Engine: Graphics
Milest
On Nov 3, 2010, at 12:33 PM, Christian Ohm wrote:
> he git repo on gitorious doesn't have all the history from svn, which makes it
> somewhat painful to retrace old changes. My local git-svn repo was way better
> in that regard. Is there a way to redo the repo from svn, doctor the
> transition
>
On Wednesday, 3 November 2010 at 12:46, dak180 wrote:
> This is git, (so in keeping with git=MacGyver) there is a way (perhaps even
> more than one); the real question is what is the cost of doing so and is the
> outcome worth that cost?
If it's possible, I'll do the doctoring, so the cost is mos
How much lost history are we talking about here?
- Per
___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev
On Wednesday, 3 November 2010 at 18:22, Per Inge Mathisen wrote:
> How much lost history are we talking about here?
Almost everything in the svn tags, i.e. the stuff we actually released, and its
branch points. I only see 2.3.2, 2.3.3, 2.3.4, 2.3.5, 3.0-beta1 in git,
everything else is missing (e
On 11/3/10, Christian Ohm wrote:
> On Wednesday, 3 November 2010 at 18:22, Per Inge Mathisen wrote:
>> How much lost history are we talking about here?
>
> Almost everything in the svn tags, i.e. the stuff we actually released, and
> its
> branch points. I only see 2.3.2, 2.3.3, 2.3.4, 2.3.5, 3.0-