On Wednesday, February 2, 2011, Marco Martin wrote: > atm is a normal remote branch of master? not a clone?
yes; my fear of clones is that we'll end up with a dozen different clones with various branches in them and it'll be painful to keep track of them all as people come and go. unless someone has a good way of tracking a growing and shrinking set of personal clones of the main repo? i would like to see us eventually have a team clone that we can all put our topic branches in (with master on the clone becoming our always-open-for- business integration branch), but right now team clones are not supported. what i have been told is possible is this: one of us creates a personal clone, and then we can all push and pull from that as if it were a team clone since there aren't any clone/push/pull restrictions on personal clones by default. i just didn't want to make this more complex than necessary by introducing another wrinkle in it all. unless we're all comfortable with it and we want to do this right away? personally i'd like to wait until we have the kdelibs workflow irc meeting and then make some decisive moves. in the meantime we can at least practice using topic branches together. > /me still trying to wrap around my mind how things should be done ;) me too; still figuring this stuff out. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
