Moderators: Nexuiz Moderators, Moderators
[-z-] wrote:tundramagi wrote:parasti wrote:Realise that this is just a suggestion not a demand (at least from my side), and the only way switching to Git makes any sense whatsoever is if you personally want to switch. Flaming somebody is always fun, but you could have avoided all that if you just said "SVN is fine, no thanks".
Anyway...
Saying "svn is fine, no thanks" is never enough. It was allready said and still people pushed for useless bueracratic change... it's almost like they are "pointy haired bosses": 'if we randomly change things and waste more and more overhead things might be better for whatever we are aiming for!'. Thusly a more .... explained opinion is needed (and then you react to it anyway).
Also git won't get your patch in faster: the patches still have to be tested, looked over, so worshiping git hoping for change is to put faith in a false god. Looking over patches will always take time, such is required because in the past bad patches have broken svn features for months.
Did you even read the thread? It's not a useless change and it was merely a suggestion with support about the benefits. divVerent took it as "omg people are trying to ruin the project again" when in reality, pyschf was just trying to make life easier for everyone with this suggestion.
If you read www.whygitisbetterthanx.com you'd be more informed about some of the benefits. SVN is a decent versioning system but it is by no means perfect. You can't honestly tell me you've never wasted time fixing things you borked with SVN. I've found git to be much more forgiving than SVN ever was.
Pulling this "bueracratic change" propaganda bullshit, I'm getting the feeling you're more in support of getting a kick out of watching people argue than you are interested in the benefits changing the versioning system can have on the project.
As far as I'm concerned, this is an open discussion about the benefits and downfalls of git vs. svn. Yes, some scripts would need some minor changes to get things on the right track but it's a small price to pay if it means we can fork, merge and have less conflicts overall in the versioning.
You can't deny that mods like nexball or nexuiz team fortress couldn't benefit from local branching
tundramagi wrote:The detractions were: it will mess up everyone's work flow, you'll be forcing the rewriting of scripts (are you going to rewrite them?), it will take a long time for people to readjust... and just when they've done that another buerecratic idea will be ramed through everyone's skulls and hearts... and they'll have to relearn some new thing rather than doing work on the project itself.[/qoute]
What scripts exactly? The auto build from SVN for windows and Linux? The code is basically the same in these except the checkout process would differ slightly.
Is there something I'm missing here?tundramagi wrote:Nexball and nexuiz team fortress should be in svn (nexball is iirc) once the code is fairly stable.
Point is, it's easier to maintain a local branch with git.Get someone with commit access who has time to do such to commit them. So should the new gib code. Or, have pyschf ask for commit access himself.
well, even with non-local branches, one possibly looses the single commits when merging in svn, whilst in git, you always have the single commits when merging. I saw some projects already loosing the ability to revert single changes cause they lost single commits on merges.With git, developers can add locally and push when it's stable... this would alleviate the problem of checking out incomplete ideas.
[-z-] wrote:Oh, so we're giving up on weighing the pros and cons of versioning systems and making personal attacks on me now?
Projects aren't just about code, and just because I haven't done QuakeC, doesn't mean I don't write code otherwise. Theory, organization, branding and marketing are all very important in order for a project to be successful.
But this thread isn't about bureaucracy, enough though you keep trying to bring it to that point. Can we get back to the point at hand now? Discussing the benefits and downfalls between the versioning systems? Thanks.
divVerent took it as "omg people are trying to ruin the project again" when in reality, pyschf was just trying to make life easier for everyone with this suggestion.
You haven't committed or attempted to commit a drop of code or media to the project,
You've only showed us screenshots of the autopackager even... no release.
[-z-] wrote:You haven't committed or attempted to commit a drop of code or media to the project,
I'm not sure where you think the new menu theme or logo came from. I'm pretty sure the websites count as media as well.
You've only showed us screenshots of the autopackager even... no release.
Actually there's a screencast on youtube and an updated version here. You would have known this if you spent less time trolling and more time reading.
No please stop derailing this thread, you can bitch to me in pm or on IRC.
Return to Nexuiz - Development
Users browsing this forum: No registered users and 1 guest