punch extension

[dhruva]

Hi,
 I am trying to push hard for mercurial usage at McAfee (where I
work). The single main concern that I could not defend comes from the
"clone" cloning the complete repository. For old repos with lot of
changes, this becomes a huge overhead.
 I wanted to know more about the "punch" extension and the reason for
keeping it out of main mercurial distribution. Are there any serious
plans to implement history trimming.
 I was looking for some configurable parameter ".hgrc" which can
expose a trimmed set of revs for cloning. Internally, it could still
keep the complete history (as we would not want to lose it from the
top most parent). All clones from that repo will have trimmed
histories. Each repo could further trim, so that cloning from them
will result in leaner repos.
 By the way, a year back I had made some noise on having mercurial
ported to VMS. I heard from the maintainer of Python port on VMS that
he has ported mercurial to VMS!

with best regards,
dhruva

-- 
Dhruva Krishnamurthy
Contents reflect my personal views only!