[Openmcl-devel] How about Git?
dfigrish at gmail.com
Mon Nov 30 07:53:50 PST 2015
2015-11-30 16:40 GMT+03:00 Robert P. Goldman <rpgoldman at sift.net>:
> With all due respect, this sounds nutty. If you have a patch, attach it to
> the Trac ticket. You can make a patch using diff if it's too hard for you
> to figure out svn diff. Or use git-svn so you can use Git while the
> maintainers use svn....
I would consider this as a "workaround" for myself, because, whether I like
it or not,
the Git is de-facto standard VCS today. And I just don't see any wrong to
the de-facto standard VCS, I can just say "it would be nice" :) But you may
status quo, of course.
Anyway, its matter of taste which VCS to use. But I don't know anyone who
wants to return back to SVN or CVS after the Git :)
> Sent from my iPad
> On Nov 29, 2015, at 23:12, Dmitry Igrishin <dfigrish at gmail.com> wrote:
> 2015-11-30 7:54 GMT+03:00 Masataro Asai <guicho2.71828 at gmail.com>:
>> Just to mention, I, as an inexperienced programmer, never commited myself
>> into svn and know only git, mostly just a casual user of ccl, have once had
>> made a patch for a bug in ccl but didn't know how to send it to whoever
>> developper. So I just made a bug report on Trac and discarded my patch.
> Yeah, the same issue for me in case of SVN (CCL). On the other hand, it's
> very easy to create
> a patch and/or send a pull request (in case of Github).
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Openmcl-devel