[scm-migration-dev] Mercurial issues for RPE

2008-07-29 Thread Vladimir Kotal
Richard Lowe wrote: > Mercurial doesn't have the concept of an active list, the 'hg list' > output is all cdm. We use that list in recommit, it *must* be > accurate. Ah, that was the thing I was missing. Then cdm_recommit() can still use the list acquired by 'wslist[repo].active(opts['parent'

[scm-migration-dev] Mercurial issues for RPE

2008-07-29 Thread Vladimir Kotal
Richard Lowe wrote: > The basic theory "Cache things we're explicitly told, and run faster" > holds, though with somewhat associated risk. The precise method > outlined above falls flat. It is imperative the active list as seen > by other things (think reci) is *correct*. Letting people influe

[scm-migration-dev] Mercurial issues for RPE

2008-07-29 Thread Vladimir Kotal
James Carlson wrote: > It's not *that* bad when the cache is reasonably warm: > > % time hg status -mardn usr/src > usr/src/uts/common/io/bridge/bridge.c > 4.50u 2.03s 0:07.52 86.8% > % Is this file system cache or some kind of Mercurial cache ? If the former then the limit of its helpfulnes

[scm-migration-dev] Mercurial issues for RPE

2008-07-29 Thread Vladimir Kotal
James Carlson wrote: > Vladimir Kotal writes: >>- 'hg edit' adds new entry > > I think that might be deferring a bit too much to SCCS. Mercurial > (like CVS and a few others) is different. You don't have to "check > out" files in order to edit them. They're writable all the time. I am very

[scm-migration-dev] Mercurial issues for RPE

2008-07-29 Thread Vladimir Kotal
Dean Roehrich wrote: > On Tue, Jul 29, 2008 at 03:57:52PM +0200, Vladimir Kotal wrote: >> By 'behave like wx' I meant the following changes to cdm.py: >>- 'hg add' hook is processed by cdm which leads to an entry being >> created in plaintext file (like 'wx/active') > > 'add' is already a bas

[scm-migration-dev] Mercurial issues for RPE

2008-07-29 Thread Richard Lowe
Vladimir Kotal writes: > Richard Lowe wrote: > > > >> Mercurial doesn't have the concept of an active list, the 'hg list' >> output is all cdm. We use that list in recommit, it *must* be >> accurate. > > Ah, that was the thing I was missing. Then cdm_recommit() can still > use the list acquired

[scm-migration-dev] Mercurial issues for RPE

2008-07-29 Thread Vladimir Kotal
Richard Lowe wrote: >>> 1. simple, just fix it I have taken care of that (CR 6726003). >>> 2. rewrite Cadmium [1] to behave like wx > > Somewhat, but not quite. I think we could possibly achieve something > similar, but "like wx" is far too strong for how similar we possibly > could be. By

[scm-migration-dev] Mercurial issues for RPE

2008-07-29 Thread Richard Lowe
Vladimir Kotal writes: > Richard Lowe wrote: > > > >> The basic theory "Cache things we're explicitly told, and run faster" >> holds, though with somewhat associated risk. The precise method >> outlined above falls flat. It is imperative the active list as seen >> by other things (think reci)

[scm-migration-dev] Mercurial issues for RPE

2008-07-29 Thread James Carlson
Vladimir Kotal writes: > James Carlson wrote: > > > > > It's not *that* bad when the cache is reasonably warm: > > > > % time hg status -mardn usr/src > > usr/src/uts/common/io/bridge/bridge.c > > 4.50u 2.03s 0:07.52 86.8% > > % > > Is this file system cache or some kind of Mercurial cache ?

[scm-migration-dev] Mercurial issues for RPE

2008-07-29 Thread Richard Lowe
Vladimir Kotal writes: > Richard Lowe wrote: > > > 1. simple, just fix it > > I have taken care of that (CR 6726003). > 2. rewrite Cadmium [1] to behave like wx >> >> Somewhat, but not quite. I think we could possibly achieve something >> similar, but "like wx" is far too strong for h

[scm-migration-dev] Mercurial issues for RPE

2008-07-29 Thread James Carlson
Vladimir Kotal writes: > James Carlson wrote: > > Vladimir Kotal writes: > >>- 'hg edit' adds new entry > > > > I think that might be deferring a bit too much to SCCS. Mercurial > > (like CVS and a few others) is different. You don't have to "check > > out" files in order to edit them. They

[scm-migration-dev] Mercurial issues for RPE

2008-07-29 Thread Dean Roehrich
On Tue, Jul 29, 2008 at 05:10:15PM +0200, Vladimir Kotal wrote: > Dean Roehrich wrote: > >Cadmium will be extended--if not with this request, then with some other > >request. Let's get a command prefix into it now, otherwise it'll be too > >painful to follow future Mercurial updates. > > While th

[scm-migration-dev] Mercurial issues for RPE

2008-07-29 Thread James Carlson
Vladimir Kotal writes: >- 'hg edit' adds new entry I think that might be deferring a bit too much to SCCS. Mercurial (like CVS and a few others) is different. You don't have to "check out" files in order to edit them. They're writable all the time. So even if we had an "hg edit" command, i

[scm-migration-dev] Mercurial issues for RPE

2008-07-29 Thread Dean Roehrich
On Tue, Jul 29, 2008 at 03:57:52PM +0200, Vladimir Kotal wrote: > By 'behave like wx' I meant the following changes to cdm.py: >- 'hg add' hook is processed by cdm which leads to an entry being > created in plaintext file (like 'wx/active') 'add' is already a base mercurial command. >- '

[scm-migration-dev] Mercurial issues for RPE

2008-07-18 Thread Vladimir Marek
Hi Richard, > >> 2. Mercurial is slow [...] > That proposal is similar to another that was made to us off list, it's > being thought about, for cdm. Is there CR to which we could subscribe to ? > Whether we can get it, and everything else, done in 2 weeks may be > another matter. That's unders

[scm-migration-dev] Mercurial issues for RPE

2008-07-17 Thread Vladimir Marek
Hi, please let me forward Vlad's comment's to scm-migration-dev, where we can find broader audience (and it's also going public). I'll attach my comments inline. On Thu, Jul 17, 2008 at 03:37:13PM +0200, Vladimir Kotal wrote: > Since the (2nd) e-mail from Mark J. Nelson I have started the conv

[scm-migration-dev] Mercurial issues for RPE

2008-07-17 Thread Richard Lowe
Vladimir Marek writes: > Hi, > > please let me forward Vlad's comment's to scm-migration-dev, where we > can find broader audience (and it's also going public). > > I'll attach my comments inline. > > > On Thu, Jul 17, 2008 at 03:37:13PM +0200, Vladimir Kotal wrote: > >> Since the (2nd) e-mail fr