From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Google Code EOL
Date: Fri, 13 Mar 2015 13:07:53 +0100 [thread overview]
Message-ID: <20150313120753.GA28041@tansi.org> (raw)
In-Reply-To: <55027F98.103@gmail.com>
On Fri, Mar 13, 2015 at 07:11:36 CET, Milan Broz wrote:
> On 03/13/2015 03:28 AM, Justin Tracey wrote:
> > For those who don't know, Google Code will be shutting down.
> >
> > http://google-opensource.blogspot.com/2015/03/farewell-to-google-code.html
>
> Yes, I know about this.
>
> All releases tarballs are already on kernel.org anyway (all completely signed
> with whole releases history), so I it is just about pages and issues.
> https://www.kernel.org/pub/linux/utils/cryptsetup/
>
> TBH I do not like GitHub (fot this particular project, not general :)
> But cryptsetup has already git mirror there, ditto kernel org.
>
> https://github.com/mbroz/cryptsetup
> http://git.kernel.org/cgit/utils/cryptsetup/cryptsetup.git/
>
> The kernel org git will probably become upstream git, not yet sure with
> pages and issues yet.
That solves the most critical question IMO. For the rest we will find
something.
Arno
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
prev parent reply other threads:[~2015-03-13 12:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 2:28 [dm-crypt] Google Code EOL Justin Tracey
2015-03-13 4:14 ` Arno Wagner
2015-03-13 6:11 ` Milan Broz
2015-03-13 10:12 ` toki clover
[not found] ` <CAGw_SrPZCyUquVn5XpHVS6YOKAu3MTy3XOnhgaNWSgBx_Z4fiw@mail.gmail.com>
2015-03-13 10:16 ` [dm-crypt] Fwd: " toki clover
2015-03-13 12:07 ` Arno Wagner [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=20150313120753.GA28041@tansi.org \
--to=arno@wagner.name \
--cc=dm-crypt@saout.de \
/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.