[scm-migration-dev] hg status after nightly

2008-07-17 Thread Alan Burlison
Danek Duvall wrote: >> What I really want is: >> >> hgext.cdm=${TOOL_ROOT}/onbld/lib/python/onbld/hgext/cdm.py > > That isn't supported, but you can set HGRCPATH to a list of hgrc files. > from hg(1), it sounds like all of them are used, rather than just the first > one found, but I'd check to ma

[scm-migration-dev] hg status after nightly

2008-07-17 Thread Alan Burlison
Richard Lowe wrote: > We have a bug open to do this, it's less fun than it looks. That > .hgignore is not even *nearly* complete enough. > > .hgignore will be versioned in the gate, if and when it exists, in > whatever form it exists. OK, thanks. Another question: Is there any plan to make env

[scm-migration-dev] hg status after nightly

2008-07-17 Thread Danek Duvall
On Thu, Jul 17, 2008 at 09:43:47AM +0100, Alan Burlison wrote: > Another question: Is there any plan to make environment variables work > in .hgrc? With teamware I have a setup that detects which side of the > Atlantic I am logged in on and/or if I am on/off SWAN and switches the > tools paths

[scm-migration-dev] hg status after nightly

2008-07-17 Thread John Levon
On Wed, Jul 16, 2008 at 07:10:34PM -0400, Richard Lowe wrote: > For another, if you want a list of files with *uncommitted* changes, > 'hg st -mar' (or -mard). Possibly hgsetup should add [defaults] status -mard ?? regards john

[scm-migration-dev] hg status after nightly

2008-07-16 Thread Richard Lowe
Alan Burlison writes: > Mark J. Nelson wrote: > >> You'll want an hgignore list, something like >> >> syntax=regexp >> \#.+# >> .+\.pyc >> proto/.+ >> .+.o >> /debug32/ >> /debug64/ >> webrev/ >> \.make\.state >> >> ...and referenced in your .hgrc. > > Shouldn't hgsetup do this for you? We hav

[scm-migration-dev] hg status after nightly

2008-07-16 Thread Richard Lowe
Will Fiveash writes: > So hg status in a repository where nightly has run is displaying a lot > output like: > > ? usr/src/uts/intel/zfs/debug64/txg.o > ? usr/src/uts/intel/zfs/debug64/uberblock.o > ? usr/src/uts/intel/zfs/debug64/unique.o > . > . > . > > The teamware to hg guides I've seen say t

[scm-migration-dev] hg status after nightly

2008-07-16 Thread Will Fiveash
On Wed, Jul 16, 2008 at 04:10:35PM -0700, Bill Sommerfeld wrote: > On Wed, 2008-07-16 at 17:58 -0500, Will Fiveash wrote: > > The teamware to hg guides I've seen say that hg status is similar to > > putback -n but they do not indicate how the developer is to deal with > > the ? status lines. > > w

[scm-migration-dev] hg status after nightly

2008-07-16 Thread Will Fiveash
So hg status in a repository where nightly has run is displaying a lot output like: ? usr/src/uts/intel/zfs/debug64/txg.o ? usr/src/uts/intel/zfs/debug64/uberblock.o ? usr/src/uts/intel/zfs/debug64/unique.o . . . The teamware to hg guides I've seen say that hg status is similar to putback -n but

[scm-migration-dev] hg status after nightly

2008-07-16 Thread Bill Sommerfeld
On Wed, 2008-07-16 at 17:58 -0500, Will Fiveash wrote: > The teamware to hg guides I've seen say that hg status is similar to > putback -n but they do not indicate how the developer is to deal with > the ? status lines. what I've discovered is that: hg status -mard shows only changes to tracked