On Jun 2, 2009, at 12:34 AM, Peter Clifton wrote: > On Mon, 2009-06-01 at 17:25 -0700, Steven Michalske wrote: >> On Jun 1, 2009, at 4:26 PM, Ben Jackson wrote: > >>> You could push it to the repo as a branch so that other people still >>> only >>> had one public repo to deal with. Then after we tag and release >>> from >>> "master" you can merge it down. >>> >> >> just don't push your stacked git managed portions.... I'm fine with >> dealing with them on your repo cause I know they are there. >> >> dealing with rebased branches should not be on git.gpleda.org repo. > > Don't worry, I know how to work with public branches in GIT. That is > why > I _don't_ push my work in progress to git.gpleda.org... I like to > rebase > quite a bit during feature development. >
I didn't worry that you would, this was meant to keep folks from bugging you to push. git handles multiple remotes easily, so there is no need for you to push. :-) I heavily use rebase in my own work, it's fantastic :-) > > -- > Peter Clifton > > Electrical Engineering Division, > Engineering Department, > University of Cambridge, > 9, JJ Thomson Avenue, > Cambridge > CB3 0FA > > Tel: +44 (0)7729 980173 - (No signal in the lab!) > > > > _______________________________________________ > geda-user mailing list > geda-user@moria.seul.org > http://www.seul.org/cgi-bin/mailman/listinfo/geda-user _______________________________________________ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user