From: Amon Ott <ao@m-privacy.de>
To: Andrey Korolyov <andrey@xdel.ru>
Cc: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>,
Sage Weil <sage@inktank.com>,
ceph-devel@vger.kernel.org
Subject: Re: v0.56.1 released
Date: Tue, 08 Jan 2013 08:44:29 +0100 [thread overview]
Message-ID: <50EBCE5D.3020601@m-privacy.de> (raw)
In-Reply-To: <CABYiri_ECmQGPJDvZoGUybFKuc7HYgk4PJ193U+oTebNMD=O7Q@mail.gmail.com>
Am 08.01.2013 08:40, schrieb Andrey Korolyov:
> On Tue, Jan 8, 2013 at 11:30 AM, Stefan Priebe - Profihost AG
> <s.priebe@profihost.ag> wrote:
>> Hi,
>>
>> i cannot see any git tag or branch claming to be 0.56.1? Which commit id is
>> this?
>>
>> Greets
>> Stefan
>
> Same for me, github simply does not sent a new tag in the pull to
> local tree by some reason. Repository cloning from scratch resolved
> this :)
This is normal git behaviour. "git fetch -t" is your friend.
Amon Ott
--
Dr. Amon Ott
m-privacy GmbH Tel: +49 30 24342334
Am Köllnischen Park 1 Fax: +49 30 99296856
10179 Berlin http://www.m-privacy.de
Amtsgericht Charlottenburg, HRB 84946
Geschäftsführer:
Dipl.-Kfm. Holger Maczkowsky,
Roman Maczkowsky
GnuPG-Key-ID: 0x2DD3A649
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-01-08 7:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 4:53 v0.56.1 released Sage Weil
2013-01-08 5:15 ` Dennis Jacobfeuerborn
2013-01-08 5:37 ` Sage Weil
2013-01-08 7:30 ` Stefan Priebe - Profihost AG
2013-01-08 7:40 ` Andrey Korolyov
2013-01-08 7:44 ` Amon Ott [this message]
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=50EBCE5D.3020601@m-privacy.de \
--to=ao@m-privacy.de \
--cc=andrey@xdel.ru \
--cc=ceph-devel@vger.kernel.org \
--cc=s.priebe@profihost.ag \
--cc=sage@inktank.com \
/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.