We're using it at songkick and it's going fine - thanks for your
efforts Jeremy, especially to get the commit messages in there. Now we
know who to blame, which is the main thing ;)
I guess my only negative feedback is that some support for submodules
(automatically doing git submodule init / update after pulling) would
be nice, but we're happy doing that manually as and when required.
On 9 Oct 2008, at 23:12, Jeremy Lightsmith wrote:
if you do try trunk, please let us know how it goes, because we are
relying on user feedback to get what's on trunk stable enough for a
new release!
Jeremy
On Thu, Oct 9, 2008 at 3:05 PM, Alexey Verkhovsky <[EMAIL PROTECTED]
> wrote:
On Thu, Oct 9, 2008 at 2:57 PM, Kevin Willock <[EMAIL PROTECTED]>
wrote:
> Thanks Alexey, do we know when the next release is slated for?
Not really. It can be anywhere between a couple of weeks and a
couple of months.
> I tried those directions initially, but the same problems occurred
That's unfortunate. People are using Ben's branch on projects, as far
as I know, so maybe someone else on the list may help you there.
Jeremy Lightsmith told me a couple of days ago that he is using CC.rb
trunk on a project with Git, after some changes (that he has checked
in already), and it works for them. So, if Ben's branch doesn't work
for you, perhaps you can try the trunk instead.
Sorry for not being very helpful.
-- Alex
_______________________________________________
Cruisecontrolrb-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
_______________________________________________
Cruisecontrolrb-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
_______________________________________________
Cruisecontrolrb-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
