Hi, > We (tools-discuss), don't have the slightest thing to do with Java. > > I understand this is something of a generic question, but do keep in > mind that what java choose to do is entirely their own business, maybe > what works for us doesn't work for them.
Understood, I am not pushing anyone to use particular tool.
> There's been some talk (both here, and on the mercurial lists) about
> partial bringovers, from memory, the general viewpoint is that it's
> possible but non-trivial for mercurial to support, and there's various
> corner cases nobody is entirely sure of. I have no idea if anyone is
> actually working on doing this, maybe one of the Mercurial people will
> chime in.
Ok.
> > * Branching/merging. I talked about possibilities of mercurial in full
> > width, and it scared them. Branching locally is a good thing, but on
> > server it may not be always wanted. For example if you have the
> > 'official devel line' someone might branch it and later merge in wrong
> > direction and thus inactivating the official branch. Not that this would
> > be fatal. After some talk, we agreed that it would be helpful to be able
> > to disable the possibility of branching of some specific branches. Is
> > the hook system strong enough to say "branch 'devel' may not be branched
> > more, unless you are user xx or yy ?"
>
> I'm assuming you mean branches within a single workspace, rather than
> a teamware-like "use separate workspaces for each line" approach to
> this?
Yes.
> For what it's worth, I would do (and do do) the multi-gate method, and
> don't like the other branching at all.
And can you limit new branches creation, or is it process which forbids
(or does not encourage to) to create local branches and push them to
server ?
Thank you Rich
--
Vlad
pgpGrvNK4EyCM.pgp
Description: PGP signature
_______________________________________________ tools-discuss mailing list tools-discuss@opensolaris.org
