<div class="gmail_quote">On Fri, Dec 11, 2009 at 11:13 AM, psteininger <span dir="ltr"><<a href="mailto:piotr.steininger@gmail.com">piotr.steininger@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Dan,<br>
<br>
I support the move to git. I think it will help the community contribute<br>
easier and provide the committers to have more control over what goes into<br>
the master branch. It's a lot easier to work with distributed, published<br>
repos, than with a ton of patch files.<br></blockquote><div><br>Indeed. We could cite a number of other benefits as well, such as being able to develop locally and to share prototypes w/ collaborators before having to worry about pushing upstream. There have actually been some long threads discussing all of these benefits, so I won't try to rehash it all.<br>
<br>The motion I'm suggesting at this point is, let's just cut over now. No one can build these modules anyway (unless they have seam-parent stashed away in a local Maven repo), so let's just make the leap.<br>
<br>Another reason is that the Seam repository in general is so screwy right now with a ton of restructures (just look at FishEye to see the bizarre history) that we should just break away from it. I don't mean to sound downtrodden, this should be seen as an opportunity!<br>
<br>-Dan<br></div></div><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br>
<a href="http://www.google.com/profiles/dan.j.allen">http://www.google.com/profiles/dan.j.allen</a><br>