git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Lichtenheld <frank@lichtenheld.de>
To: git@vger.kernel.org
Cc: Junio C Hamano <junkio@cox.net>,
	Frank Lichtenheld <frank@lichtenheld.de>
Subject: [PATCH 1/4] config.txt: Document gitcvs.allbinary
Date: Fri, 13 Apr 2007 18:02:30 +0200	[thread overview]
Message-ID: <1176480153972-git-send-email-frank@lichtenheld.de> (raw)
In-Reply-To: <11764801533023-git-send-email-frank@lichtenheld.de>


Signed-off-by: Frank Lichtenheld <frank@lichtenheld.de>
---
 Documentation/config.txt |    7 +++++++
 1 files changed, 7 insertions(+), 0 deletions(-)

diff --git a/Documentation/config.txt b/Documentation/config.txt
index cf1e040..061c585 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -408,6 +408,13 @@ gitcvs.logfile::
 	Path to a log file where the cvs pserver interface well... logs
 	various stuff. See gitlink:git-cvsserver[1].
 
+gitcvs.allbinary::
+	If true, all files are sent to the client in mode '-kb'. This
+	causes the client to treat all files as binary files which suppresses
+	any newline munging it otherwise might do. A work-around for the
+	fact that there is no way yet to set single files to mode '-kb'.
+	See gitlink:git-cvsserver[1].
+
 http.sslVerify::
 	Whether to verify the SSL certificate when fetching or pushing
 	over HTTPS. Can be overridden by the 'GIT_SSL_NO_VERIFY' environment
-- 
1.5.1.1

  reply	other threads:[~2007-04-13 16:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-13 16:02 [PATCH 0/4] Random fixes to Documentation/config.txt Frank Lichtenheld
2007-04-13 16:02 ` Frank Lichtenheld [this message]
2007-04-13 16:02 ` [PATCH 2/4] config.txt: Document core.autocrlf Frank Lichtenheld
2007-04-13 16:02 ` [PATCH 3/4] config.txt: Change pserver to server in description of gitcvs.* Frank Lichtenheld
2007-04-13 16:02 ` [PATCH 4/4] config.txt: Fix grammatical error in description of http.noEPSV Frank Lichtenheld

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1176480153972-git-send-email-frank@lichtenheld.de \
    --to=frank@lichtenheld.de \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).