Hi Bjoern,
let's see if there are "accidental" new heads on the outgoing
repository. No need to have a hook for something that never happens anyway.
Best regards,
Heiner
bjoern michaelsen - Sun Microsystems - Hamburg Germany wrote:
On Tue, 27 Oct 2009 14:22:31 +0100
Jens-Heiner Rechtien <[email protected]> wrote:
Actually, I'm thinking about a hook which will prevent the creation
of new heads on the outgoing repositories. Not yet implemented,
though.
This time, unlike last time, I am against such a hook. ;-) If somebody
creates multiple heads on an outgoing repo, no harm was done to the
master. This is different than with SVN. However, it has to be clear
that such a repo will never be integrated unless all heads are merged.
Still, having such repos on outgoing might be of value for experimental
minibranches, where one is not certain if they might get integrated one
day.
When those are on outgoing repos:
- They are on backup as long as it is uncertain if they will make it to
the master.
- They can be easily merged into "real cws" for integration once they
seem fit for it.
- They can be simply deleted with the repo if they prove faulty.
Nothing of value will be lost.
If you want to make absolutely clear that a cws wont be integrated when
its repo has multiple heads, I would propose to add another "Test" to
EIS showing this nifty stopsign and scary red boxes, if the cws repo
has multiple heads.
Best Regards,
Bjoern Michaelsen
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
