On Tue, May 12, 2015 at 07:06:19PM -0400, Alan Conway wrote: > On Thu, 2015-05-07 at 15:42 -0400, Rafael Schloming wrote: > > > > 1. For developing new language bindings (and really for any development > > > > work that will involve enough new stuff to have a noisy commit history) > > > we > > > > use branches. This is already the case with the Ruby/C++/Python3 > > > bindings, > > > > as well as the SASL work. > > IMO this is a good policy. Go work is now on branch `go`. I left > bindings/go/README.md with a pointer to the new branch so people > following older discussions can find it. > > > I think I pretty much said go ahead on master, so apologies for singling > > you out. > "go" ahead. Hahaha. Just when I think we've done all those jokes, > there's always another one.
I do like this. I would love to push my Reactive changes up to a ruby-reactive branch on the core repo and let people examine it there. -- Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/
Description: PGP signature