Re: Push to all repositories
- From
- Enrico Weigelt <weigelt@metux.de>
- Date
- Dec 12, 2010, 15:09 UTC
- Message-ID
- <20101212150929.GA23298@nibiru.local>
- In-Reply-To
- <1291829983410-5816069.post@n2.nabble.com>
* Kevin Sheedy <kevinsheedy@gmail.com> wrote:
Hi,
Show 7 quoted lines
> Clearcase has a great solution to this, "dynamic views". Whenever I check in > some code, the whole team magically get's my changes straight away. > Normally, they don't even notice, they're just forced to stay in sync. This > drastically reduces the number of 'code conflicts' where people make changes > to 'stale' files. This enforces the practise of "catching errors early". It > also keeps developers "honest" as they have to keep the quality of their > checkins high lest they get shouted at by the rest of the team.
Are you sure you *really* want this ? I'd strongly advise against that.
Better have some central branch (maybe on a dedicated remote) where everybody can push to, and the others fork off from there and frequently rebase or merge if they like.
My preferred workflow is to have per-issue branches (eg. per bug, per feature, etc), which frequently get rebased to the mainline and are only pushed upwards if they're finished (IOW: only one person is actively working on an small issue at a time, others may just read but dont write). Once some issue branch seems to be ready, it gets rebased to latest master and cleaned up, others might do some reviews and if it passed all tests (and only then!) it gets pushed upwards.
cu
-- ---------------------------------------------------------------------- Enrico Weigelt, metux IT service -- http://www.metux.de/ phone: +49 36207 519931 email: weigelt@metux.de mobile: +49 151 27565287 icq: 210169427 skype: nekrad666 ---------------------------------------------------------------------- Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme ----------------------------------------------------------------------