It's not guaranteed that changes would never conflict though. darcs is nice in that it allows spontaneous branching in the way you propose, but it doesn't guarantee that such spontaneous branches will never conflict. -- Robin
2009/11/11 Nicolas Pouillard <[email protected]> > > Excerpts from Corey O'Connor's message of Wed Nov 11 21:46:35 +0100 2009: > > > > I've started working on VTY 4.1 which, as implied by the version > > number, has some API changes. These API changes can effect yi. Which > > development process would other yi developers prefer: > > > > 0. I keep the main yi branch up to date with respect to the > > tip-of-trunk VTY. This requires other yi developers that use the VTY > > UI to keep up to date wrt VTY. > > 1. I keep a separate yi branch up to date with respect to tip-of-trunk > > VTY and the main yi branch. This means that other yi developers who > > use tip-of-trunk VTY have to also pull from this repository. > > > > Any preference? I'd prefer option #0 since that would be easiest for > > me ;-) But if it's easier on other developers to do something > > different then I'll go for that option. > > Another option would be to go for #0 but clearly mark patches that follow > these changes and ensure we can skip them when pulling. > > -- > Nicolas Pouillard > http://nicolaspouillard.fr > > > > --~--~---------~--~----~------------~-------~--~----~ Yi development mailing list [email protected] http://groups.google.com/group/yi-devel -~----------~----~----~----~------~----~------~--~---
