Darren J Moffat wrote:
Stephen Lau wrote:
- 500 changeset failsafe:
if there are over 500 incoming changesets, i.e.:
if you pulled a 'stevel' ;-), then your push will be
rejected. please contact [EMAIL PROTECTED] if you
legitimately need to do this; we'll do something
server-side for you until we get proper webapp
support for doing this
This limit makes it impossible to create clones of ON without your help.
For those of us that don't work in the same timezone as the tonic-ops
people that means we have to wait for you to do our work - thats bad.
What is the time line for the webapp support of this and what is it
likely to be ?
What I'd like to see is the ability to clone any given hg repository
that already exists, and if possible to give a tag to that clone
operation. For example if I want to create a new project repository
that is based on ON build 54 I could, but I could also just choose to
clone the current state of ON or to clone another project repository.
Aside from creation of repos with logical parents via the webapp, one
solution I think could work (and have mentioned to Steve in passing)
would look like:
o If the new tip is a merge, only notify on that one delta.
(I don't know whether we can work out which specific deltas to ignore
based on the parents of that delta, and/or whether we could do
similar for merges other than the new tip, but if we could do so,
that would be preferred obviously).
o Don't notify or only notify most basically on initial imports (where
the previous tip was rev 0), which I think was suggested previously
and disagreed with, but I can't seem to find it.
I think these two would facilitate "new import without a logical
parent" without the current issue, and these and/or the webapp changes
to support an initial clone would remove the problems in the "new repo
with logical parent" case.
-- Rich
_______________________________________________
tools-discuss mailing list
[email protected]
