<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div>Personally, I hate 'git'. My old brain has a far easier time making the correct mental model for CVS or SVN than 'git'. But that's me.<div><br></div><div>If you do decide to move to 'git', or anything else for that matter, then I STRONGLY suggest you do it in a fashion whereby you do NOT lose the history of the files. There's a lot of valuable info in the commit messages and the version trees. Just taking the top of trunk from CVS and making a 'git' repo from it is not acceptable in my opinion.</div><div><br></div><div>Michael McDonald</div><div><a href="mailto:mikemac@mikemac.com">mikemac@mikemac.com</a></div><div> </div><div><div><div>On Oct 31, 2012, at 2:19 PM, John Morrison wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi;<div><br></div><div>I also would like to see a single official repository, whether git/github or otherwise, with continued incorporation of patches/improvements. (Some time ago I submitted patches for the scigraph portion of mcclim which I would have liked to seen included.) Has there been any movement on this, especially as regards quicklisp?</div>
<div><br></div><div>If there is anything I can do to help, I would certainly be happy to do so. Please advise.</div><div><br></div><div>Thanks!</div><div><br></div><div>-jm<br><br><div class="gmail_quote">On Fri, Aug 24, 2012 at 6:58 AM, Manuel Giraud <span dir="ltr"><<a href="mailto:manuel@ledu-giraud.fr" target="_blank">manuel@ledu-giraud.fr</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">Rudolf Schlatte <<a href="mailto:rudi@constantly.at">rudi@constantly.at</a>> writes:<br>
<br>
> On Aug 24, 2012, at 10:40, Timothy Moore <<a href="mailto:moore@bricoworks.com">moore@bricoworks.com</a>> wrote:<br>
><br>
>> I was going to save this mail until my current round of mcclim hacking is finished, but here<br>
>> goes. I'm not particularly interested in continuing to work with CVS. Are people agreeable<br>
>> with moving to git? I'm not invested (at all) in having my github repo become the "official"<br>
>> repo, but a site like github has a lot of advantages as a host.<br>
><br>
> I'm very much in favor of moving to git. git-svn works well enough<br>
> for upstream svn archives, but syncing back and forth with cvs is<br>
> always uncomfortable for me.<br>
><br>
> But could we leave the "official" git archive on <a href="http://common-lisp.net/" target="_blank">common-lisp.net</a>? I<br>
> like github, but when I'm checking out a project that I'm unfamiliar<br>
> with, I hate having to decide between downloading (for the sake of<br>
> example) onixie/mcclim, slyrus/mcclim, mmontone/mcclim and<br>
> timoore/mcclim.<br>
<br>
</div>Same here. I'm too in favor to switch to git (which is clearly easier<br>
than CVS) but keeping the official mcclim repository where the project<br>
is seems better to me. github is cool, fun, social and whatnot but I<br>
find it hard to get an official software out of it.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Manuel Giraud<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
mcclim-devel mailing list<br>
<a href="mailto:mcclim-devel@common-lisp.net">mcclim-devel@common-lisp.net</a><br>
<a href="http://lists.common-lisp.net/cgi-bin/mailman/listinfo/mcclim-devel" target="_blank">http://lists.common-lisp.net/cgi-bin/mailman/listinfo/mcclim-devel</a><br>
</div></div></blockquote></div><br></div>
_______________________________________________<br>mcclim-devel mailing list<br><a href="mailto:mcclim-devel@common-lisp.net">mcclim-devel@common-lisp.net</a><br>http://lists.common-lisp.net/cgi-bin/mailman/listinfo/mcclim-devel<br></blockquote></div><div apple-content-edited="true"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Times New Roman'; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div><br></div></span><br class="Apple-interchange-newline">
</div>
<br></div></body></html>