David Bustos writes:
> When I create a workspace by pulling (necessary to put the workspace in
> its own ZFS filesystem), ws emits some shell-test (you know, [ test ] )
> errors. Turns out it's because the .hg/hgrc isn't automatically
> populated with a default path. I don't know whether anythi
Mike Kupfer writes:
> Rich> usr/src/tools/scripts/nightly.sh
> [...]
> Rich> (old) 2199: Should this really go away entirely? What about the
> Rich> TeamWare case?
>
> See http://bugs.grommit.com/show_bug.cgi?id=264#c9.
Ah, ok. I think stevel and myself fixed another set of poss
"Mark J. Nelson" writes:
> SCM Migration Project Tool Usage Survey
>
> What tools have you used from the SCM Migration Project?
nightly, webrev, cdm, xref (not recently), ws, all checks implied by
cdm except rtichk.
> http://opensolaris.org/os/project/scm-migration/
>
> When was the last time y
Bill Holler writes:
> Anything else that you think the SCM team should know
> about before we integrate?
>
> Having to define CODEMGR_WS and PARENT_WS
> environment variables sucks. This will not fly in the
> mercurial world. How about being able to specify
> workspaces on the c
http://bugs.grommit.com/show_bug.cgi?id=513
roland.mainz at nrubsig.org changed:
What|Removed |Added
CC||roland.mainz at nrubsig.org
--
http://bugs.grommit.com/show_bug.cgi?id=513
Summary: ws complains when workspace has no parent.
Product: SCM Migration
Version: unspecified
Platform: All
OS/Version: Solaris 11/Nevada
Status: NEW
Severity: normal
Pr
> "Mark J. Nelson" wrote:
Did you find any issues?
>>>
>>> Yes... the ksh scripts should be "ksh93 -n " clean (which
>>> does some simple lint-like checking) - which isn't AFAIK done yet...
>>> ... which leads to a question: Is there a webrev where I can look at the
>>> changes ?
>>
>> Caveat
Richard Lowe wrote:
> Bill Holler writes:
>
>
>> Anything else that you think the SCM team should know
>> about before we integrate?
>>
>> Having to define CODEMGR_WS and PARENT_WS
>> environment variables sucks. This will not fly in the
>> mercurial world. How about being able to
>> Did you find any issues?
>
> Yes... the ksh scripts should be "ksh93 -n " clean (which
> does some simple lint-like checking) - which isn't AFAIK done yet...
> ... which leads to a question: Is there a webrev where I can look at the
> changes ?
Caveat: this webrev is PRELIMINARY. It is a cha
> SCM Migration Project Tool Usage Survey
>
> What tools have you used from the SCM Migration Project?
gypfm and webrev.. thought the tools haven't been updated in quite a
while (Jun 31 2007), so I can't say I've been completely bleeding edge..
>
> When was the last time you used them?
consta
>
> SCM Migration Project Tool Usage Survey
>
> What tools have you used from the SCM Migration Project?
>
> http://opensolaris.org/os/project/scm-migration/
>
mercurial w/ cadmium
gpyfm
> When was the last time you used them?
>
this week
> What project(s) did you use them for?
>
IPS
> Ar
> SCM Migration Project Tool Usage Survey
>
> What tools have you used from the SCM Migration Project?
Most all of 'em.
> When was the last time you used them?
Yesterday.
> What project(s) did you use them for?
SCM Migration.
> Are you a project or consolidation gatekeeper?
No, though I did
Ok, thanks.
I thought I might add a "Project gatekeepers: if you respond on behalf of
your teams, please let us know how many developers are involved" note,
too.
--Mark
On Fri, 30 May 2008, John Beck wrote:
> Date: Fri, 30 May 2008 15:34:49 -0700
> From: John Beck
> To: Mark J. Nelson
> C
SCM Migration Project Tool Usage Survey
>
> What tools have you used from the SCM Migration Project?
>
> http://opensolaris.org/os/project/scm-migration/
None.
> When was the last time you used them?
Never.
> What project(s) did you use them for?
None.
> Are you a project or consolidation
Rich> usr/src/tools/scripts/nightly.sh
[...]
Rich> (old) 2199: Should this really go away entirely? What about the
Rich> TeamWare case?
See http://bugs.grommit.com/show_bug.cgi?id=264#c9.
mike
Quoth Mark J. Nelson on Fri, May 30, 2008 at 04:52:15PM -0600:
> SCM Migration Project Tool Usage Survey
>
> What tools have you used from the SCM Migration Project?
>
> http://opensolaris.org/os/project/scm-migration/
Cadmium, ws, webrev, and hgsetup.
> When was the last time you used them?
To
Welcome feedback on audience, note, or survey, otherwise I'll send it out
in 20-30 minutes. Thanks.
--Mark
Intended audience, all bcc'd:
tonic-pteam-confidential at sun.com,
tools-discuss at opensolaris.org,
on-discuss at opensolaris.org,
testing-discuss at o
> SCM Migration Project Tool Usage Survey
>
> What tools have you used from the SCM Migration Project?
>
>
>
most of them
> When was the last time you used them?
>
september 2007
> What project(s) did you use them for?
>
scm-migration-dev :)
> Are you a project or consolidation gatekeeper
SCM Migration Project Tool Usage Survey
What tools have you used from the SCM Migration Project?
webrev
http://opensolaris.org/os/project/scm-migration/
When was the last time you used them?
Yesterday
What project(s) did you use them for?
Tesla OpenSolaris project
Are you a proj
SCM Migration Project Tool Usage Survey
What tools have you used from the SCM Migration Project?
http://opensolaris.org/os/project/scm-migration/
nightly
wx
Cadmium (nits, recommit)
webrev
When was the last time you used them?
Yesterday.
What project(s) did you use them fo
Mark> If you do not use the Burlington build servers, and have not downloaded
Mark> and used the mercurial-enabled SUNWonbld packages from the scm-
Mark> migration opensolaris project page, you may delete this note.
Rewhack the ordering on that so "Burlington" is buried further down, as I
almost t
21 matches
Mail list logo
