May someone tell me how to checkin a binary file into my repository?
Thanks a lot..
man 1 cvs
Look for the -k options.
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
This is a weird one, and I coulda sworn this worked for me last week. I
can no longer run 'cvs log file.c' in my local repository and see a list
of the tags that file.c exists within. I was under the impression that
'cvs log' would display tags. What am I doing wrong here?
As an aside,
They are merely sequential counters of revisions stored in the RCS
files. If you need to remember any given point in the revision history
of a file, or of all the files in a module, then you really must use
tags and tags alone.
I was under the impression that the revision numbers
To the owner of this list:
I suggest that the list is closed to the subscribers only. Quite a lot
of spam is being sent there.
What do you think ?
I suggest they use ordb.org to lock out the spam from open relays. Most
of the messages I've seen here as spam in the past few months
foo.c in the top level is 1.46, but when moved and added, it gets
version 1.1 (logically). How do I preserve the history of the changes
made to this file to date, so I can do a 'cvs log' on it and get the
full changes?
You can't. The best you can do is
mv foo.c src/foo.c
cvs add
I'm in the process of making a release of a pretty popular GNU package,
and need to restructure the directories in the package itself a bit.
Basically the toplevel directory has accumulated some source files (*.c,
*.cc) and there are some other changes, but my question is this..
As I
You must only sync it in the other direction -- i.e. update the
read-only server _from_ the master!
Great, then once again, you make absolutely no sense.
If I have a copy of the master, which allows anonymous read-only
access, and that copy also accepts authenticated commits
Duh. If you're doing authentication and authorisation on a unix-based
file server then you MUST, _M_U_S_T_ use a unique system account for
ever real-world user or else you might as well not use any
authentication whatsoever. Pserver has NO accountability from the
system's point of view.
I would suggest you and your users just learn to use SSH and forget
about trying to implement any security software yourself. If you
already have real unix user-ids for every real user then you're most of
the way to making it work properly -- why not go all the way?
I'm intrigued.
There's only _EXACTLY_ one case where cvspserver is in any way more
secure than giving out real accounts, and that's when pserver is used to
give read-only anonymous access to a _copy_ of a repository.
And if the copy needs to get sync'd back to the real repository (a
definate
There have been lots of descriptions of how to do this posted to this
list in the past. I suggest you research groups.google.com and/or
www.geocrawler.com.
Descriptions, with absolutely no working solution. Do you get the
full depth of a book by reading just the 'Foreward'? I have
I've been reading up on the various methods to move files and
directories around in the repository, and I haven't yet found a workable
solution to what I'm trying to achieve with one of my public projects.
I have a repository which contains a structure similar to the following:
12 matches
Mail list logo
