All of lore.kernel.org
 help / color / mirror / Atom feed
From: Justin Tracey <j2tracey@gmail.com>
To: dm-crypt <dm-crypt@saout.de>
Subject: [dm-crypt] Google Code EOL
Date: Thu, 12 Mar 2015 19:28:28 -0700	[thread overview]
Message-ID: <55024B4C.4070107@gmail.com> (raw)

For those who don't know, Google Code will be shutting down.

http://google-opensource.blogspot.com/2015/03/farewell-to-google-code.html

As I would hope everyone on this list knows, Google Code hosts
Cryptsetup (Code, issues, and wiki). The most important date in that
post for this project is probably *August 24, 2015* -- the date that
Google Code becomes read-only. Other, less important dates are January
25, 2016 when everything is hosted only as a tarball, and January 1,
2017 when they may or may not delete everything.

Are there any plans for migration? Github seems to be the favorite,
followed by BitBucket.

 - Justin

             reply	other threads:[~2015-03-13  2:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13  2:28 Justin Tracey [this message]
2015-03-13  4:14 ` [dm-crypt] Google Code EOL 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   ` [dm-crypt] " Arno Wagner

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=55024B4C.4070107@gmail.com \
    --to=j2tracey@gmail.com \
    --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.