+[ Bill Fumerola ]-
| On Thu, 25 Nov 1999, Forrest W. Christian wrote:
|
| > What I'd propose is one additional "track".
|
| "Branch" is the typical name for these things.
|
| I'll just offer that bitrot is a serious reason why we don't need
| ano
On Thu, 25 Nov 1999, Forrest W. Christian wrote:
> What I'd propose is one additional "track".
"Branch" is the typical name for these things.
I'll just offer that bitrot is a serious reason why we don't need
another branch.
As for 'missioncritical', we simply call it 'errata'.
--
- bill fume
Hmm, this brings up another interesting question. First, to put this in
context:
Jordan K. Hubbard wrote:
> Actually, the -missioncritical branch is sort of provided for
> now as a function of -previousstable. There are plenty of people still
> running 2.2.x, for example, and you even still occ
Jordan K. Hubbard wrote:
>
> > -current (all the latest greatest experimental).
> > -stable (all the latest gretest "Stable" stuff).
> > -missioncritical (conservative release, once a year or so - only bug
> > fixes after release).
>
> Actually, the -missioncritical branch is sort of provided
On 26-Nov-99 Gregory Bond wrote:
> "readonly". Oddly, both claim to be CVS 1.10 `Halibut' (the others were all
> too flat.)
Well actually..
cvs -R update means assume a read only repo..
cvs update -R means recurse :)
(Well update recurses by default, but you get the idea)
---
Daniel O'Con
"Chris D. Faulhaber" <[EMAIL PROTECTED]> wrote:
> >From cvs(1):
> -R Turns on read-only repository mode.
Well aren't I a complete goose.
I originally looked in the cvs man page on our Solaris system, for which -R is
"recurse", rather than the FreeBSD system, where (as Chris pointed out)
On Fri, 26 Nov 1999, Gregory Bond wrote:
> Is there some simple way of getting around this? A quick peruse of the CVS man
> didn 't suggest any way of turning off the RCS locking. The cvsup man page
> didn't seem to have a flag to say "ignore directory modes". Do I just give
> up and do it as
I maintain /usr/ncvs via cvsup. By default, the directories in /usr/ncvs are
root.wheel, mode 755. This means you need to be root to do a "cvs get"
because RCS needs to create lock files in the cvs repository.
I often check out various bits of the -CURRENT source so I can compare with
what's
I believe maybe this went by a couple of months back, but...
Whenever I CVSup 2.2-STABLE, a file (/var/db/pgk/.mkversion) gets
installed on my machine. This, in turn, causes pkg_info to
complain:
chad> pkg_info -Ia > /dev/null
pkg_info: can't change directory to '/var/db/pkg/.mkversion'
In article <[EMAIL PROTECTED]> you write:
>> -current (all the latest greatest experimental).
>> -stable (all the latest gretest "Stable" stuff).
>> -missioncritical (conservative release, once a year or so - only bug
>> fixes after release).
>
>Actually, the -missioncritical branch is sort of
Doug White wrote:
>
> On Tue, 23 Nov 1999, jack wrote:
>
> > Today Jordan K. Hubbard wrote:
> >
> > > > Our release QA is horrible. Look at what Apple does -- they sit on the
> > > > release candidate for a *month*, with *no changes at all*, before putting
> > >
> > > The problem is that Appl
Jordan K. Hubbard writes:
;->> -current (all the latest greatest experimental).
;->> -stable (all the latest gretest "Stable" stuff).
;->> -missioncritical (conservative release, once a year or so - only bug
;->> fixes after release).
;->Actually, the -missioncritical branch is sort of provided
12 matches
Mail list logo
