Whiteboard area

[Justin Mclean <ju...@classsoftware.com>]

> It doesn't have to go under the committer's name.
> 
> I could easily create a folder named 'McClean' and your code could go in
> there, while I still have my own folder.

That's good to know. 

Any idea how version control comments and commits could be preserved?  For instance if I take a copy of the SDK make a lot of changes/commits locally (in git) how would that be preserved when I  handed it back to committer to check in for me? Again not a big issue (and I'm guessing there's no easy way) I'm just trying to work out what the best workflow is here.

Thanks,
Justin

Re: Whiteboard area

[Omar Gonzalez <om...@gmail.com>]

If you want a GUI for git svn commands the Tower app has support. Also, git
svn commands should come with a standard Git installation, at least I
didn't have to install that separately.

-omar

Re: Whiteboard area

[Justin Mclean <ju...@classsoftware.com>]

> I would look at the git svn commands and manage my work from there if I
> wasn't a committer. I believe it'll even let you create patches from your
> Git branch for SVN.

Yep that works but it don't preserve checkins or commits (to git). So when your code gets checked in to SVN it will a miss a large amount of important info. I've (so far) not been able to work out a way around that.

For those you don't know git and svn can work fairly well together but sadly the standard version of git in OSX and the standard github client don't come with SVN support and you need to install git-svn.

There's a nice write up on how to install and use git-svn on OSX (what I happen to currently use) here:
http://intridea.com/posts/going-rogue-with-git-svn-on-os-x

It assumes you have MacPorts installed (you can also use Brew) which requires Xcode which is probably overkill for just wanting to use git svn, but being a developer you should already have it installed right? :-)

The initial check out of the flex SDK from SVN to Git will take some time and I'm guessing even more time when we get the "real" flex SDK with the full version history. On my machine with a decent (by Australian standards) internet connection it took over 2 hours.

Justin

Re: Whiteboard area

[Omar Gonzalez <om...@gmail.com>]

On Wednesday, January 25, 2012, Justin Mclean <ju...@classsoftware.com>
wrote:
>
>> It doesn't have to go under the committer's name.
>>
>> I could easily create a folder named 'McClean' and your code could go in
>> there, while I still have my own folder.
>
> That's good to know.
>
> Any idea how version control comments and commits could be preserved?
 For instance if I take a copy of the SDK make a lot of changes/commits
locally (in git) how would that be preserved when I  handed it back to
committer to check in for me? Again not a big issue (and I'm guessing
there's no easy way) I'm just trying to work out what the best workflow is
here.
>
> Thanks,
> Justin
>
I would look at the git svn commands and manage my work from there if I
wasn't a committer. I believe it'll even let you create patches from your
Git branch for SVN.

-omar