From: "Wesley J. Landaker" <wjl@icecavern.net>
To: git@vger.kernel.org
Subject: [PATCH] Documentation: git-svn: fix trunk/fetch svn-remote key typo
Date: Wed, 1 Apr 2009 15:02:30 -0600 [thread overview]
Message-ID: <200904011502.31465.wjl@icecavern.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 519 bytes --]
Fix the git-svn documentation svn-remote example section talking about
tags and branches by using the proper key "fetch" instead of "trunk".
Using "trunk" actually might be nice, but it doesn't currently work.
The fetch line for the trunk was also reordered to be at the top of the
list, since most people think about the trunk/tags/branches trio in that
logical order.
Signed-off-by: Wesley J. Landaker <wjl@icecavern.net>
---
Documentation/git-svn.txt | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
[-- Attachment #2: fa96799d745c94a691cb71a3768afc328718416c.diff --]
[-- Type: text/x-patch, Size: 726 bytes --]
diff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt
index cda3389..64f1c55 100644
--- a/Documentation/git-svn.txt
+++ b/Documentation/git-svn.txt
@@ -672,9 +672,9 @@ listed below are allowed:
------------------------------------------------------------------------
[svn-remote "project-a"]
url = http://server.org/svn
+ fetch = trunk/project-a:refs/remotes/project-a/trunk
branches = branches/*/project-a:refs/remotes/project-a/branches/*
tags = tags/*/project-a:refs/remotes/project-a/tags/*
- trunk = trunk/project-a:refs/remotes/project-a/trunk
------------------------------------------------------------------------
Keep in mind that the '*' (asterisk) wildcard of the local ref
reply other threads:[~2009-04-01 21:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200904011502.31465.wjl@icecavern.net \
--to=wjl@icecavern.net \
--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.
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).