unstable, testing, experimental, volatile, should all get the point across. I have a hard time believing someone would complain about the unstable branch lacking stability.
- Tom On 30-Mar-09, at 3:09 PM, björn wrote: > > 2009/3/30 Tom McNulty: >>>> Why not create a branch in your git repo? That'll way it'll be a >>>> bit >>>> easier for us to follow your changes. >>> >>> I could do that, but I rebase that branch all the time -- would this >>> not cause problems? >> >> It may upset contributers, but otherwise forcing a push on your side >> will simply result in (automatic) forced pulls for us. I take it >> you're rebasing these patches against the mainline? > > Yes, I rebase it against my master branch which is the one I push to > the public repo. So, I guess this won't be an issue since I'm not > really expecting many people to be contributing to my experimental > branches (such as Core Text). If anybody ever does then I guess they > will have to take care. > > I guess I should be able to name all experimental branches > "experimental/branchname" or something and then note down somewhere > that such branches get rebased onto master regularly. Hmmm...now how > do I do that...does "git branch experimental/name" work...have to take > a look. Maybe there is a more succinct standard name for this kind of > stuff..."topic/name" perhaps? Anybody with a clue? > > Björn > > > --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_mac" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
