| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
Approved by: peter
Obtained from: OpenBSD
|
| |
|
|
|
|
| |
which included commits to RCS files with non-trunk default branches.
|
| |
|
|\
| |
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| | |
|
| |
| |
| |
| | |
Approved by: re
|
|\ \
| |/
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| |
| |
| |
| |
| |
| |
| |
| | |
of the bugs that I know of. We've been running a slightly older version
of this on freefall/repoman, where it was afflicted by a silly merge error
on my part (fixed).
Approved by: re
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
---
Fix communication hanging in communication shutdown phase, caused by at
least older CVS clients (version < 1.11.2) and a semantically incorrect
usage of getc() by the server.
---
getc() was being used on a blocking socket/pipe.
Submitted by: rse
|
| |
| |
| |
| |
| | |
cvs vendor release and should not have been 'cvs add'ed there in
the first place.
|
| | |
|
| | |
|
|\ \
| |/
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| |
| |
| |
| | |
Obtained from: http://www.cvshome.org/
|
| |
| |
| |
| |
| |
| |
| | |
with cut/paste in the last release.
Submitted by: Makoto MATSUSHITA <matusita@jp.FreeBSD.org>
Obtained from: http://ccvs.cvshome.org/source/browse/ccvs/src/client.c.diff?r1=1.302&r2=1.303
|
| | |
|
| |
| |
| |
| | |
Remove the obsolete cvsbug.sh script
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
for the trouble that DES and I had with MFCs: when "cvs update -jfoo -jbar"
creates a new file, it sets the version to 0 ("new") but sets the timestamp
in the Entries file to the timestamp of the file that's new on the branch.
The CVS client doesn't upload files whose timestamps match with the Entries
file, so these new files don't get uploaded to the server and the server
fails when trying to check them in.
PR: bin/40227
Approved by: peter
MFC after: 2 weeks
|
| |
| |
| |
| |
| |
| |
| |
| | |
support that already exists for checkout. The -T option for cvs update
and cvs checkout may be used to cause CVS to retrieve/update the checkin
template when possible.
MFC after: 1 week
|
| |
| |
| |
| |
| |
| | |
diffs are against the head branch only).
MFC after: 1 week
|
| | |
|
| |
| |
| |
| |
| | |
the beginning of constructed log messages being passed to $EDITOR. This
is where folks start typing.
|
| |
| |
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| |
| |
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| |
| |
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| |
| |
| |
| | |
still some suspicious and/or broken stuff to fix yet.
|
|\ \
| |/
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| | |
|
| |
| |
| |
| | |
all the time, and IMHO it is long overdue.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
"-D date" command line option. There is code in the original to
handle a special case. If the date search finds revision 1.1 it
is supposed to check whether revision 1.1.1.1 has the same date
stamp, which would indicate that the file was originally brought
in with "cvs import". In that case it is supposed to return the
vendor branch version 1.1.1.1.
However, there is a bug in the code. It actually compares the date
of revision 1.1 for equality with the date given on the command
line -- clearly wrong. This commit fixes the coding bug.
There is an additional bug which is _not_ fixed in this commit.
The date comparison should not be a strict equality test. It should
allow a fudge factor of, say, 2-3 seconds. Old versions of CVS
created the two revisions with two separate invocations of the RCS
"ci" command. We have many old files in the tree in which the
dates of revisions 1.1 and 1.1.1.1 differ by 1 second.
Approved by: peter
|
| |
| |
| |
| | |
anoncvs no-password hack is gone and is replaced by the official version.
|
|\ \
| |/
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
checkouts from a local repo and committing via remote cvs. A cvs -d
override of the mismatched CVS/Root files was missing. This is a client
side fix, I'd appreciate it if the folks having trouble with this would
update their cvs client and pay particular attention next time..
|
| |
| |
| |
| | |
the other temporary file creation functions..
|
| | |
|
| |
| |
| |
| |
| | |
as cvs update -j had kittens over the whole thing and I ended up merging
it by hand.
|
| | |
|
|\ \
| |/
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| |
| |
| |
| | |
Obtained from: cyclic.com
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
default options for cvs. These options are interpreted first and can be
overwritten by explicit command line parameters.
Obtained from: GNU Grep 2.3
|
| |
| |
| |
| |
| |
| |
| | |
trying to do a commit. The server side will use the correct name, and the
client side restriction is just an annoyance.
Requested by: lots of folks
|
| |
| |
| |
| | |
sources.
|
| |
| |
| |
| | |
older 1.9.26 baseline)
|
| |
| |
| |
| |
| | |
Changes of significance include the top level CVS directory being optional
and defaulting to off..
|