gEDA-dev: glist-dev without screen coordinate caching
Peter Clifton
pcjc2 at cam.ac.uk
Tue Nov 28 13:48:36 EST 2006
[snip]
> > > Also, I would rather not create a branch from a branch. Let's branch
> > > the no_screen coords branch from HEAD once the glist_dev branch has
> > > been merged to HEAD. Sound good? Comments? Thanks,
> >
> > I think that all sounds sensible. Perhaps we don't even need to branch
> > no_screen coords, but could instead continue from the glist_dev branch.
> > (Or is that a bad idea?)
>
> If you mean continue from the glist_dev branch without merging it to
> HEAD, then I don't like that. They are different features which
> shouldn't be mixed.
> I'd make a no_screen branch after the glist_dev branch is merged to
> HEAD.
I simply meant once glist_dev had been merged into head, and would
otherwise be unused. If active development on glist_dev is still likely,
then indeed, a different branch is better.
Perhaps it is cleanest to make a different branch anyway, that way the
name of the branch can reflect the development direction.
Peter
More information about the geda-dev
mailing list