On 06/12/2010 02:51 PM, Chani wrote: > >> This is also separate from the "personal branches" feature that lets you >> have branches for personal work in the main repository but in a specific >> namespace (including username). > > personal branches? omgwtfbbq! :)
I actually misread something... The "personal branches" feature is actually a bit different than what I originally described -- there are two ways you can do this. The first is that you can have a branch that is *only* given to you when you clone because it is stored in a private ref area. This keeps checkouts lean, because nobody sees others' personal branches, but also makes collaboration difficult. Not to mention that you wouldn't see this in cgit/redmine. The other way to do it is simply to allow people to create branches with a specific namespace -- e.g. personal/myname/mybranch -- but that are a normal ref that everyone gets. This makes the checkout size of the repo go up (although generally slightly) and means everyone sees all of them, but it also means cgit/redmine see them too. > so... personal branches for WIP that other people may be interested in; > personal clones for random experiments that may not go anywhere? :) Right, that could be a good way to do it. Personal branches are for in-development features that you expect to merge into trunk; totally wacky things (or maybe super long-term ones) can be developed in personal clones. >> However, these >> would have to be used wisely and deleted when possible to avoid an >> ever-increasing and unwieldy repository. >> > > which - branches, clones or cgit/redmine configuration? Both branches *and* clones :-) --Jeff
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Kde-scm-interest mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-scm-interest
