Lenny Foner <[EMAIL PROTECTED]> writes:
> Date: Tue, 24 Oct 2000 14:46:13 -0400 (EDT)
> From: [EMAIL PROTECTED] (Larry Jones)
>
> Derek R. Price writes:
> >
> > I'm thinking maybe the standard test comes close to the argument length
> > limit and something about your sys
For any who are interested, I've updated my ".trunk" + ".origin" patch
vs. the current (nov 1, 2000) development version of CVS.
http://www.geocities.com/dotslashstar/branch_patch.html
Only change since last time is change to sanity.sh to account
for recent fix to "cvs add" to handle "-Q" option.
Any body know how I can unsubscribe from the list..
Had a nice time with u people..
Thanks..
Raghu K
Software Engineer
Pretzel Logic Sofware Inc.
Cupertino, California
email : [EMAIL PROTECTED]
phone: 408-366-9010 extn 338
___
Info-cvs mailing list
On Mon, Oct 30, 2000 at 10:12:31PM +, Spencer L. Swift wrote:
> I am a fairly experienced CVS user, but only recently understood the
> basic concept behind the Vendor Tag/Branch and the main trunk when you
> first import an existing set of source files. In effect, the initial
> Vendor Tag spe
I have a problem that I was trying to solve by checking in linked files
(ln -s) and wanted to know if anyone else knew of a better solution.
Problem: I am working for a company that currently has a library of
designs under CVS control. The next step is to use these designs in a
project also
Alexy Khrabrov wrote:
> I have an interesting reverse-update case: my working copies are OK, but
> the partition where the CVS repository is kept was formatted over by a
> buggy Red Hat 7.0 anakonda installer (fixed a day later:-).
Please check the email archives. I have answered this question
En réponse à Dave Sherohman <[EMAIL PROTECTED]>:
> On Fri, Oct 27, 2000 at 11:45:41PM -, Fabrice Gautier wrote:
> > How do I told cvs that these are resolved ?
> >
> > (cvs bible say commit, but i can't I'm read-only)
>
> You just answered your own question: You can't resolve the conflict
>
On Wednesday, November 01, 2000 1:43 AM, Laird Nelson
[SMTP:[EMAIL PROTECTED]] wrote:
> Shem Mazur wrote:
> > I have a CVS user who continues to checkout modules or update files
from
> > the wrong branches. Can I restrict her ability to update from
> > particular branches or main trunk?
>
> Wha
Jon Wilson wrote:
> If you don't have or don't want Perl (why? :-0) then you could probably
> monkey up a shell script using the Unix 'file' command. Have a look at
> 'man file' to see exactly how your local version works, but you should be
> able to easily tell whether a file is one of 'text', '
If you don't have or don't want Perl (why? :-0) then you could probably
monkey up a shell script using the Unix 'file' command. Have a look at
'man file' to see exactly how your local version works, but you should be
able to easily tell whether a file is one of 'text', 'executable' or
'data'.
On
"Derek R. Price" wrote:
>
> Laird Nelson wrote:
>
> > That said, if you know that your user will never try to force a commit
> > using the -r switch (don't know how you'd know this, but most users
> > don't use this flag), then you can write a commitinfo script that will
> > check the old revisi
Andrew Gilmartin wrote:
> What would be useful to us is a pre-commit check that made sure the user can
> revise a given file and given branch or mainline. For example,
>
> # user file development-line
> * #none #none
> *
Manish Koolwal wrote:
> From among a group of files, how can we find out which are Binary files?
> (This is in reference to UNIX). Also, please help me if you know any fast
> method to sagregate Binary Files.
UNIX itself rarely makes a distinction. Some applications (like diff) make
guesses b
> Can I restrict her ability to update from
> particular branches or main trunk?
We have a similar issue in that we need to restrict who can update which
files on the mainline and (sometimes branches). There was some discussion of
this recently and the general approach taken was to implement a pr
Laird Nelson wrote:
> That said, if you know that your user will never try to force a commit
> using the -r switch (don't know how you'd know this, but most users
> don't use this flag), then you can write a commitinfo script that will
> check the old revision number and reject access based on it
[EMAIL PROTECTED] on 2000.10.30 13:21:30
>> This topic has been discussed numerous times and I still haven't seen an
>> absolute need to use "cvs admin -l".
>
>Well, some people don't trust that if someone gets a conflict when
>trying to merge, that the resulting file will be OK, because of hu
I know this won't address the problem directly. Anyway, create a commitinfo
script that'll prevent her from checking her stuff into the wrong branch.
Recovery from checking out or updating from the wrong branch should be fairly
straightforward ("cvs up -A").
Noel
[EMAIL PROTECTED] on 2000.10
Shem Mazur wrote:
> I have a CVS user who continues to checkout modules or update files from
> the wrong branches. Can I restrict her ability to update from
> particular branches or main trunk?
What the various other replies were trying (somewhat unhelpfully :-)) to
tell you is no, not with CVS
Hi,
From among a group of files, how can we find out which are Binary files?
(This is in reference to UNIX). Also, please help me if you know any fast
method to sagregate Binary Files.
Thanks and Regards,
Manish Koolwal
I would like to request a feature enhancement to the cvs log command.
With the cvs log command, you can do stuff like "cvs log -d > '1 Jan 2000
12:34:56' " and get all the revision history after 1 Jan 2000 @ 12:34:56.
My request is to be able to do the same with the -r option, thus "cvs log
-r>r
Hi,
Is there some document that describes the format of the input given to the
commands specified in the "loginfo" file?
Thanks,
Shlomo
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
21 matches
Mail list logo
