hg bookmarks are a lot closer to what we were looking at in terms of something that can be used for long-term feature development, without being permanent. So something like vgifts, or the new update page, or say a complete redesign of the CSS (note we're not doing this last one, but as something that would affect a *lot* of pages and wouldn't be able to be done in one-shot, but that is sufficiently large in scope that we wouldn't be able to roll it out one page at a time).
A question from me: would this be suitable for small changes, or would that be overkill? Hrrrm, so maybe a branch or bookmark or whatever for major feature development, and smaller patches get pulled into a dev branch?
Also a question: Afuna> hrrrrm. I do wonder if if maybe it's the bookmarks we should be looking at Afuna> rather than getting caught up in branches exor674> are bookmarks local or global? exor674> because I know I read something with hg exor674> that said that it had a chance of having gc eat the commits like tasty candy
no subject
A question from me: would this be suitable for small changes, or would that be overkill? Hrrrm, so maybe a branch or bookmark or whatever for major feature development, and smaller patches get pulled into a dev branch?
Also a question:
Afuna> hrrrrm. I do wonder if if maybe it's the bookmarks we should be looking at
Afuna> rather than getting caught up in branches
exor674> are bookmarks local or global?
exor674> because I know I read something with hg
exor674> that said that it had a chance of having gc eat the commits like tasty candy