Re: Planning Wicket Next Generation

[Sebastiaan van Erk]

And other than that, I seriously doubt it's the VCS that's the issue, but rather it's supporting 3 (or more) different branches, testing that the patches work accross all branches, making different patches for those that don't etc. With a relatively small team of *volunteers* it's a choice where you spend your resources...

Regards,
Sebastiaan

Gerolf Seitz wrote:

And I personally think a centralized VCS is much better for projects with a small core team anyway.

and don't even get me started on the talk you mentioned...

to make this clear:
the talk is held by Linus Torvalds and most of the time he's bitching about
how bad CVS is and how stupid the SVN guys are (with SVN devs sitting
in the audience) for trying to fix something which is inherently broken
(meaning centralized vcs) and how great he is, because he hacked it
together in probably only an afternoon (don't remember the exact timespan).

sry, but i just can't stand such attitude, which is why i've never taken a
closer
look at git after watching the talk.

  Gerolf

  Gerolf


On Fri, Mar 21, 2008 at 11:33 AM, Antony Stubbs <[EMAIL PROTECTED]>
wrote:

Switch your vcs to  http://git.or.cz/ git  (
http://www.youtube.com/watch?v=4XpnKHJAok8 intro ), then merging won't
be a
problem.

Johan Compagner wrote:

But doing a 1.4 release so quickly with only generics means for me
merging of 3 branches.

--
View this message in context:
http://www.nabble.com/Planning-Wicket-Next-Generation-tp16046194p16196479.html
Sent from the Wicket - Dev mailing list archive at Nabble.com.

smime.p7s
Description: S/MIME Cryptographic Signature