From: Marc Lehmann <schmorp@schmorp.de>
To: linux-f2fs-devel@lists.sourceforge.net
Subject: status of 3.18 branch?
Date: Sat, 12 Dec 2015 22:27:21 +0100 [thread overview]
Message-ID: <20151212212721.GB3480@schmorp.de> (raw)
Hi!
I was just told that my instructions for SMR drives no longer work because
the f2fs 3.18 branch no longer exists, and indeed, it seems to be gone:
# git clone -b linux-3.18 git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git
Cloning into 'f2fs'...
warning: Could not find remote branch linux-3.18 to clone.
Was this intentional? If yes, is there an old copy somewhere (I don't have
one unfortunately)?
Thanks!
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / schmorp@schmorp.de
-=====/_/_//_/\_,_/ /_/\_\
------------------------------------------------------------------------------
next reply other threads:[~2015-12-12 21:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-12 21:27 Marc Lehmann [this message]
[not found] ` <CAOtxgycxVkuLFOBiB0FGfJ3UrE-5TZCDK8dVu8XeNZrb2hb28w@mail.gmail.com>
2015-12-12 23:13 ` status of 3.18 branch? Marc Lehmann
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=20151212212721.GB3480@schmorp.de \
--to=schmorp@schmorp.de \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).