Re: [mantisbt-dev] Preferred way of using git for developing Mantis

[John R. <jr...@le...>]

Gianluca Sforna wrote:
> On Wed, Aug 20, 2008 at 10:44 AM, Robert Munteanu
> <rob...@gm...> wrote:
>> Hi,
>>
>> Which way do you recommed to develop / submit patches to Mantis with a
>> git backend:
>>
>> 1) git-svn as described at
>> http://www.mantisbt.org/wiki/doku.php/mantisbt:git_svn
>> 2) forking http://github.com/jreese/mantisbt
> 
> The latter is surely faster, but then you will be synced to John's
> repository that could be lagging behind SVN head.

I'm planning to keep the GitHub repo up to date as much as I can, so it 
may lag behind by a day or two at most, and anyone who clones/forks it 
can easily do `git svn rebase` to pull the latest SVN info, and it 
should work seamlessly with any future pulls from GitHub too.

The only caveat is that any topic branches that I push to GitHub (not 
'master' or 'master-110'), will be rebased on a regular basis to keep 
them in line with the appropriate master branch, so be forewarned. :P

> if you are planning to contribute regularly, then method 1 is probably
> better. To save time, I think you can focus on more recent commits,
> let's say from svn revision 5400 onward.

Actually, for a contributer, either method should be perfectly 
acceptable.  My GitHub repo has branches for both the stable 1.1.x 
branch and the development 1.2.x trunk, and because it's quicker to 
clone from, should allow you to easily keep up with both lines of 
development and bug fix porting.

Cheers

-- 
John Reese
LeetCode.net