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 <wmorgan-sup at masanjin.net>
Reformatted excerpts from William Morgan''s message of 2008-01-22:> 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.Everything that was applied to next is now in master. 0.4 release imminent!> 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.I''ve updated the wiki with better Git instructions. -- William <wmorgan-sup at masanjin.net>
Excerpts from William Morgan''s message of Wed Jan 23 17:42:15 +1100 2008:> Reformatted excerpts from William Morgan''s message of 2008-01-22: > > 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. > > Everything that was applied to next is now in master. 0.4 release > imminent!And the release notes ... :-) By the way I''ve just started using sup. Lovin'' it! rgh> > 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. > > I''ve updated the wiki with better Git instructions. >-- You''re worried criminals will continue to penetrate into cyberspace, and I''m worried complexity, poor design and mismanagement will be there to meet them - Marcus Ranum
Reformatted excerpts from Richard Heycock''s message of 2008-01-22:> And the release notes ...In the announcement, in History.txt, and on the website now.> By the way I''ve just started using sup. Lovin'' it!Great to hear! -- William <wmorgan-sup at masanjin.net>