Cary Coulter writes:
>
> MIME-Version: 1.0
> Content-Type: multipart/mixed; boundary="===80217196335194441=="
Please do not send MIME and/or HTML encrypted messages to the list.
Plain text only, PLEASE!
> I can't get the $CVSROOT/CVSROOT/cvsignore file
I can't get the $CVSROOT/CVSROOT/cvsignore file to
work correctly (what I think it should do :)). I put a single line entry
with
vssver.scc
on it to keep these files from importing (we're
migrating some projects from Visual SourceSafe), but they get
imported and/or rec
Guus Leeuw writes:
>
> How does the client ask for the server's CVSROOT/cvsignore file?
By sending a new request.
> If new clients should work with old servers, they can't ask, because
> the old server would bail out: Unknown Question or some such. It will
> behave we
[
Prescript
This is a bit long an email, but explains pretty much what I think
is the right way at the moment.
]
> From: Larry Jones [mailto:[EMAIL PROTECTED]]
> Guus Leeuw writes:
> >
> > Found sofar a good place to get the server's
> > $CVSROOT/CVSROOT
Guus Leeuw writes:
>
> Found sofar a good place to get the server's
> $CVSROOT/CVSROOT/cvsignore: start_server() in client.c right after
> we do connect_to_?server().
I'm not sure that's safe -- I suspect that it's better to do it in
ign_setup() right where it pr
support the new
> > request to get
> > CVSROOT/cvsignore, and the server still has to support the
> > Questionable
> > request for old clients.)
>
> Bad Thing (tm)
> Like your footnote said: the middle ground (backwards
> compatibility) is for sissy weasels..
to do, is to have all of the ignore
> processing
> take place on the client side (asking the server for its
> CVSROOT/cvsignore and including it at the appropriate place in the
> processing) and have the client tell the server to ignore
> nothing. In
> that case, the client
t the server might have something for him in the (!)
> $CVSROOT/CVSROOT/.cvsignore list only (!).
It's more complicated than that -- most of the individual cvs commands
also call ign_setup(), even when running in server mode.
I think the right thing to do, is to have all of the ignore pr
al only CVS... I think, right now, it cannot even
as much as care about the things ign_setup does. What it should care
about, really, is only the $CVSROOT/CVSROOT/.cvsignore.
Larry, any opinions? *grin*
Hmm, are there a lot of people using real accounts on the CVS Server
that can override the .cvsigno
> From: Larry Jones [mailto:[EMAIL PROTECTED]]
> Not quite -- the way it works locally (which is the usual
> benchmark for
> what "do it right" means) is that you start with the default ignore
> list, then you apply the repository's cvsignore (which, in c/s mode
> requires getting it from t
Guus Leeuw writes:
>
> > From: Larry Jones [mailto:[EMAIL PROTECTED]]
> >
> > Neither, just changing the existing code to do it right. I haven't
> > thought about what the consequences of doing that would be, though.
>
> Well, apparently that makes for the Server to overwrite Client non-igno
> From: Larry Jones [mailto:[EMAIL PROTECTED]]
> Guus Leeuw writes:
> >
> > Wouldn't this be something nice to have for 1.11 (If it
> comes *grin*)?
> > What would be the strategy to stuff this in? New command, or
> > option to commands? Larry, tell me :)))
>
> Neither, just changing the e
Guus Leeuw writes:
>
> Wouldn't this be something nice to have for 1.11 (If it comes *grin*)?
> What would be the strategy to stuff this in? New command, or
> option to commands? Larry, tell me :)))
Neither, just changing the existing code to do it right. I haven't
thought about what the conseq
> From: Larry Jones [mailto:[EMAIL PROTECTED]]
> $CVSROOT/CVSROOT/cvsignore doesn't work quite right in client/server
> mode. Unfortunately, there is currently no way for the client to get
> the contents of $CVSROOT/CVSROOT/cvsignore from the server, so the
> server&#x
Michel-Ange Camhi writes:
>
> We're using CVS in remote connection mode via rsh, and we'd like to
> setup an ignore list for a whole repository, using the
> $CVSROOT/CVSROOT/cvsignore file.
[...]
> But this setting is completely... ignored! *.o and *.a files, for
>
Hi all,
We're using CVS in remote connection mode via rsh, and we'd like to
setup an ignore list for a whole repository, using the
$CVSROOT/CVSROOT/cvsignore file.
Here's the contents of my file :
! RCS SCCS CVS CVS.adm RCSLOG cvslog.* tags
TAGS .make.sta
[EMAIL PROTECTED] on 04/15/2000 10:45:13 AM
>I propose:
> (A) `#' introduces a comment that
> continues to the end of the input line.
> It is prevented this special meaning when preceded by `\'.
> (B) `//' (or `/') introduces a comment.
What's the difference between (A) and (B
From: "Noel L Yap" <[EMAIL PROTECTED]>
Subject: comments in CVSROOT/cvsignore
Date: Sat, 15 Apr 2000 07:07:22 +0900 (JST)
| Is there anyway to put comments in CVSROOT/cvsignore? I tried '#' and it didn't
| work.
See the default ignore pattern `ign_defaul
Is there anyway to put comments in CVSROOT/cvsignore? I tried '#' and it didn't
work.
Thanks,
Noel
19 matches
Mail list logo
