Hi all,

There've been enough bug fixes and other changes that I'm going to try
to push 0.4 out the door over the next few days. I'll try and give a
report of what features are in and which are still percolating in next.

I realize now that I've been using Git wrong---I've been maintaining
features as branches off of next, which has the effect that I can't
easily merge a "topic" over to master without also merging in everything
else that happened to be merged into next at an earlier point. So this
might be a little messy. (But I've learned my lesson!)

The upshot is that, if you submit a patches, it should typically be cut
against master, not against next. (I'll update the wiki to reflect
this.) Then I can merge topics into next just as before, but there's no
false dependence between features introduced by Git.

-- 
William <[EMAIL PROTECTED]>
_______________________________________________
sup-talk mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/sup-talk

Reply via email to