From: Christian Weiske <cweiske@cweiske.de>
To: git@vger.kernel.org
Subject: git svn clone clone php/pear/Net_LDAP2 misses tags and branches
Date: Sun, 25 Oct 2015 15:43:25 +0100 [thread overview]
Message-ID: <20151025154325.36eddb4c@bogo> (raw)
[-- Attachment #1: Type: text/plain, Size: 587 bytes --]
Hi,
Using git 2.6.2 to clone an SVN repository misses out branches and tags.
The clone command:
$ git svn clone --trunk=trunk --tags=tags --branches=branches
--prefix=origin/
https://svn.php.net/repository/pear/packages/Net_LDAP2 -r 255346
The final repository's tag and branch list is empty.
There are tags and branches, though - see the web interface at
http://svn.php.net/viewvc/pear/packages/Net_LDAP2/
What am I doing wrong here?
--
Regards/Mit freundlichen Grüßen
Christian Weiske
-=≡ Geeking around in the name of science since 1982 ≡=-
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next reply other threads:[~2015-10-25 14:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-25 14:43 Christian Weiske [this message]
2015-10-25 15:32 ` git svn clone clone php/pear/Net_LDAP2 misses tags and branches Edmundo Carmona Antoranz
2015-10-25 16:30 ` Christian Weiske
2015-10-25 18:48 ` Christian Weiske
2015-10-25 19:25 ` Edmundo Carmona Antoranz
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=20151025154325.36eddb4c@bogo \
--to=cweiske@cweiske.de \
--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