git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Gunnlaugur Þór Briem" <gunnlaugur@gmail.com>
To: git@vger.kernel.org
Cc: "Gunnlaugur Þór Briem" <gunnlaugur@gmail.com>
Subject: [PATCH] Document git-svn fetch --log-window-size parameter
Date: Tue, 23 Oct 2012 10:33:26 +0000	[thread overview]
Message-ID: <1350988406-97624-1-git-send-email-gunnlaugur@gmail.com> (raw)

The --log-window-size parameter to git-svn fetch is undocumented.

Minimally describe what it does and why the user might change it.

Signed-off-by: Gunnlaugur Þór Briem <gunnlaugur@gmail.com>
---
 Documentation/git-svn.txt | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt
index cfe8d2b..64756c9 100644
--- a/Documentation/git-svn.txt
+++ b/Documentation/git-svn.txt
@@ -146,6 +146,12 @@ Skip "branches" and "tags" of first level directories;;
 ------------------------------------------------------------------------
 --
 
+--log-window-size=<n>;;
+    Fetch <n> log entries per request when scanning Subversion history.
+    The default is 100. For very large Subversion repositories, larger
+    values may be needed for 'clone'/'fetch' to complete in reasonable
+    time. But overly large values may lead to request timeouts.
+
 'clone'::
 	Runs 'init' and 'fetch'.  It will automatically create a
 	directory based on the basename of the URL passed to it;
-- 
1.7.12.3

             reply	other threads:[~2012-10-23 10:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-23 10:33 Gunnlaugur Þór Briem [this message]
2012-10-25  9:52 ` [PATCH] Document git-svn fetch --log-window-size parameter Jeff King
2012-10-26  9:46   ` Eric Wong
2012-10-26 13:32     ` Jeff King
2012-10-26 13:45       ` Gunnlaugur Thor Briem
2012-10-29 20:18       ` Eric Wong
2012-10-29 22:02         ` Jeff King
2012-10-29 22:36           ` Eric Wong

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=1350988406-97624-1-git-send-email-gunnlaugur@gmail.com \
    --to=gunnlaugur@gmail.com \
    --cc=git@vger.kernel.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).