Shankar Unni wrote:
>
> Greg A. Woods wrote:
>
> > Version control is a part of software configuration and
> > change management. I thought that (what you said) is what
> > it (change management) was all about! ;-)
>
> Argh. I don't think I'm getting my point across, am I?
>
> OK, forget I sa
::I have just read that Mailman can be used to produce a
::Majordomo type roster of users, by email request (necessary,
::as I do not have shell access to the Mailman host) -- If I can
::get that roster (a couple thousand names), I will issue a
::serialized vacation tracer to each user, and wee
> "Dror" == info-cvs-admin <[EMAIL PROTECTED]> writes:
Dror> Hi,=20 I think I need to clarify myself a little, what am I
Dror> looking for is not a Visual Studio (.NET) plugin for CVS.
Dror> My team is working on an Intranet project and using Visual
Dror> Studio .NET. While w
Reading from the CVS (info) manual [keyword substitution / using
keywords]:
To include a keyword string you simply include the relevant text
string, such as `$Id$', inside the file, and commit the file. CVS
will automatically expand the string *as part of the commit
operation*.
Is this t
Todd Denniston writes:
> This is the point where you set down, add up what it
> will cost your company to support your number of users
> by putting addons on a ''cheapskates'' version control
> system to support its use in the companies IP policy setup.
Oh, please..
Well, is it the consensus of
I cannot seem to locate loginfo.pl. According to some posts its in the
source distribtion, so I downloaded the source to CVS from www.cvshome.org,
but didn't see it.
Could somebody please send me a loginfo.pl and the line from loginfo that
calls it.
Thanks a bunch,
Brian
_
Nick Patavalis writes:
>
> Is this true? I thought that expansion occured as a part of the
> *export* (cvs checkout, cvs diff, cvs export, etc) operations.
Both are correct. The actual process of expanding keywords happens
during checkout, but committing a file containing keywords triggers an
au
"Stefan Monnier <[EMAIL PROTECTED]>" <[EMAIL PROTECTED]> wrote in
message news:<[EMAIL PROTECTED]>...
> > "Forrest" == Forrest Samuels <[EMAIL PROTECTED]> writes:
> > My company is developing a Java application that we are releasing on
> > several different platforms. We initially released it
Shankar Unni writes:
>
> I.e. is the opposition to ACLs a matter of priorities, or philosophy?
> If it is philosophy, is it the position of the maintainers that ACLs are
> so evil that they will actively oppose any attempt by anyone to insert
> such a feature into CVS, in order to protect innocent
Larry Jones wrote:
> A bit of both, I suspect.
That's good to know.
In any case, I'll take a closer look at the CVSNT stuff (I wish they
hadn't gone and reformatted all their sources so much :-/), and see
what's portable back to the main line..
Some basic features ("cvs passwd", "cvs ls",
On Mon, Oct 28, 2002 at 03:43:04PM -0800, Andy Glew wrote:
> I originally posted this to the newsgroup fa.info-cvs, but it
> appears to be oneway. Pardon if this is a repost.
[It isn't. But only the (sparsely-tagged) "HTML" was readable in
my plain-text mail client; the "text" version was all ru
[ On Tuesday, October 29, 2002 at 09:10:44 (-0800), Shankar Unni wrote: ]
> Subject: RE: Per-modules readers/writers ?
>
> Well, is it the consensus of the maintainers that they will *never*
> accept any access control feature patches for CVS?
Nobody can arrive at any consensus on this kind of thi
On Tue, Oct 29, 2002 at 10:28:25AM -0800, Shankar Unni wrote:
> In any case, I'll take a closer look at the CVSNT stuff (I wish they
> hadn't gone and reformatted all their sources so much :-/), and see
> what's portable back to the main line..
GNU wdiff might be useful. It's a diff that's word
The consensus of the maintainers has historically been to never add features
that they don't personally need, unless somneone supplies code, documentation,
and a regression suite. And then it gets integrated at their discretion.
There are already at least two major splinter groups using features
[ On Tuesday, October 29, 2002 at 10:28:25 (-0800), Shankar Unni wrote: ]
> Subject: RE: Per-modules readers/writers ?
>
> In any case, I'll take a closer look at the CVSNT stuff (I wish they
> hadn't gone and reformatted all their sources so much :-/), and see
> what's portable back to the main li
> Todd Denniston writes:
>
> > This is the point where you set down, add up what it
> > will cost your company to support your number of users
> > by putting addons on a ''cheapskates'' version control
> > system to support its use in the companies IP policy setup.
>
For rational values of "compan
I think this discussion has hit a wall, but I'll answer these points
anyway. But I'm no longer pushing for such a feature to be included,
because of the obvious reluctance of so many, so we can let this
discussion drift away..
Greg Woods wrote:
> If you're happy without real security then why don
[ On Tuesday, October 29, 2002 at 13:47:05 (-0800), Shankar Unni wrote: ]
> Subject: RE: Per-modules readers/writers ?
>
> Cost? Utility? Stability?
Good questions. What are _your_ answers?
> (And besides, is it your contention that
> Linux filesystem security is "real" security? All I have to
hi all,
i was wondering if anyone had a simple script where you could say:
script.pl modulename "message.*" TEMP_TAG
(or similar) and it would tag each file with that message -- throwing an
error if it didn't.
I know this sounds kinda specific but hopefully someone has already needed
it. I want
Hi
Is there anyway to checkout the repository such that I
can exclude some files?These files are needed for an
older release but in the current version they are not
needed.I know we can make a branch, but is there any
other method to exclude just some files from
checkout?They are in different dire
20 matches
Mail list logo
