Submitting patches

Submitting patches

Discuss the source code and development of Spring Engine in general from a technical point of view. Patches go here too.

Moderator: Moderators

Post Reply
zenzike
Posts: 77
Joined: 12 Apr 2008, 13:19

Submitting patches

Post by zenzike »

I've submitted a couple very minor patches via Mantis.

I'm wondering what the submit protocol is here: of course, it would be better if I had SVN write access, rather than creating patches all the time, what's the consensus on new becoming a new dev? Should I continue to submit patches via mantis?
Tobi
Spring Developer
Posts: 4598
Joined: 01 Jun 2005, 11:36

Re: Submitting patches

Post by Tobi »

Usually you start by submitting patches, and then if they are good enough and I get lazy I give you commit access :P

(That's sort of the "protocol" ;-))
User avatar
koshi
Lobby Developer
Posts: 1059
Joined: 14 Aug 2007, 16:15

Re: Submitting patches

Post by koshi »

now that that's cleared up: whatever happened to the plans to move to a distributed scm like git?

if the repo hosting was an issue, take a look at gitosis:
http://scie.nti.st/2007/11/14/hosting-g ... secure-way
Tobi
Spring Developer
Posts: 4598
Joined: 01 Jun 2005, 11:36

Re: Submitting patches

Post by Tobi »

Hosting isn't the issue, the issue is that when switching to new VCS (read: git, didn't look into anything else), I don't want to drag in all the pretty much unrelated crap.

IOW, I want an import of /rts, /game, /installer, /tools/unitsync and some other stuff, but I do not want e.g. /tools/MapDesigner (>50M useless binaries), /Site (unrelated to engine), /tools/upspring, etc.

This because people used to complain about the fact that they need to check out lots of unnecessary stuff with SVN, and that even while with SVN, you can check out subfolders. So I don't think it would be a good idea to make a git repo weigh in at >100M (with all the crap in it).

But I did not yet figure out a good way to import the right stuff and filter out the bloat. (still need to play a bit more with git-filter-branch tho..., it might be doable with that...)
zenzike
Posts: 77
Joined: 12 Apr 2008, 13:19

Re: Submitting patches

Post by zenzike »

Tobi wrote:Usually you start by submitting patches, and then if they are good enough and I get lazy I give you commit access :P

(That's sort of the "protocol" ;-))
Right, then I'll keep submitting patches until you give in :)
Tobi
Spring Developer
Posts: 4598
Joined: 01 Jun 2005, 11:36

Re: Submitting patches

Post by Tobi »

Btw, maybe you could prefix patches with [patch] in mantis? I usually filter on that when I'm looking for patches to apply ;-)

(I'll fix the earlier ones myself, don't think normal users can change title.)
zenzike
Posts: 77
Joined: 12 Apr 2008, 13:19

Re: Submitting patches

Post by zenzike »

Yep sure, no problem. I noticed that that's what I ought to be doing after I submitted, sorry! :$
imbaczek
Posts: 3629
Joined: 22 Aug 2006, 16:19

Re: Submitting patches

Post by imbaczek »

at the very least we can spend some time with rebase --interactive to weed out unneeded commits. (i think you can easily list commits touching only certain paths, so this process doesn't have to be tedious.)
User avatar
hoijui
Former Engine Dev
Posts: 4344
Joined: 22 Sep 2007, 09:51

Re: Submitting patches

Post by hoijui »

Tobi wrote:Btw, maybe you could prefix patches with [patch] in mantis?
(I'll fix the earlier ones myself, don't think normal users can change title.)
no we can not change titles, and i did the same like zenzike; noticing that [patch] should be prefixed after submitting. my patch 0000655 is such one btw. very small, very minor, wiating since a long time already ;-)
Post Reply

Return to “Engine”