aboutsummaryrefslogtreecommitdiff
path: root/FAQ.in
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@redhat.com>2000-11-01 16:33:25 +0000
committerUlrich Drepper <drepper@redhat.com>2000-11-01 16:33:25 +0000
commit4442d7e8ee42829859f645451d7a8b1c3e0aa9e2 (patch)
tree7851010689069fc354c862899d3a691a19ad6944 /FAQ.in
parenta69a8d9c708a1e66c5427ad177573c8e450da8c6 (diff)
downloadglibc-4442d7e8ee42829859f645451d7a8b1c3e0aa9e2.zip
glibc-4442d7e8ee42829859f645451d7a8b1c3e0aa9e2.tar.gz
glibc-4442d7e8ee42829859f645451d7a8b1c3e0aa9e2.tar.bz2
Update.
2000-11-01 Ulrich Drepper <drepper@redhat.com> * configure.in (with_cvs): Test for pserver access.
Diffstat (limited to 'FAQ.in')
-rw-r--r--FAQ.in8
1 files changed, 8 insertions, 0 deletions
diff --git a/FAQ.in b/FAQ.in
index b57a42d..b3b4843 100644
--- a/FAQ.in
+++ b/FAQ.in
@@ -1023,6 +1023,14 @@ Please read also the NEWS file which is the authoritative source for this
and gives more details for some topics.
+?? The makefiles want to do a CVS commit.
+
+{UD} Only if you are not specifying the --without-cvs flag at configure
+time. This is what you always have to use if you are checking sources
+directly out of the public CVS repository or you have your own private
+repository.
+
+
? Source and binary incompatibilities, and what to do about them
?? I expect GNU libc to be 100% source code compatible with