From: Christian Weiske <cweiske@cweiske.de>
To: Edmundo Carmona Antoranz <eantoranz@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git svn clone clone php/pear/Net_LDAP2 misses tags and branches
Date: Sun, 25 Oct 2015 19:48:51 +0100 [thread overview]
Message-ID: <20151025194851.793f8c64@bogo> (raw)
In-Reply-To: <20151025173033.28346d49@bogo>
[-- Attachment #1: Type: text/plain, Size: 487 bytes --]
Hello Christian,
> > Did you try with -r revision-number:HEAD?
>
> Good idea. I tried it, and now I have the tags and branches:
Unfortunately, the tag branches only have a single commit and have no
relation to the trunk branch:
$ git log --oneline origin/tags/Net_LDAP2-2.0.12
0bc9db1 Tagging the 2.0.12 release
$
What can I do against that?
--
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 prev parent reply other threads:[~2015-10-25 18:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-25 14:43 git svn clone clone php/pear/Net_LDAP2 misses tags and branches Christian Weiske
2015-10-25 15:32 ` Edmundo Carmona Antoranz
2015-10-25 16:30 ` Christian Weiske
2015-10-25 18:48 ` Christian Weiske [this message]
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=20151025194851.793f8c64@bogo \
--to=cweiske@cweiske.de \
--cc=eantoranz@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.