All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
To: backports@vger.kernel.or
Cc: linux-kernel@vger.kernel.org
Subject: [ANN] New central Linux backports tree for development
Date: Mon, 2 Dec 2013 20:26:03 +0100	[thread overview]
Message-ID: <20131202192603.GA15791@cerro.do-not-panic.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 654 bytes --]

First, thanks *tons* to Hauke for taking over the tree maintenance
while I was shackled. I'm back now though and ready to help
out again, so keep 'em patches 'comin.

It was convenient to switch maintenance between me and Hauke but
it was an *inconvenience* to tell developers about a different repo
switch during development, as such we now have a central repository
which you should use and update your trees *one last time*:

git://git.kernel.org/pub/scm/linux/kernel/git/backports/backports.git

Please use this moving forward, if we ever need to switch who is
maintaining the trees this should hopefully be fully transparent to
development.

  Luis

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

                 reply	other threads:[~2013-12-02 19:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20131202192603.GA15791@cerro.do-not-panic.com \
    --to=mcgrof@do-not-panic.com \
    --cc=backports@vger.kernel.or \
    --cc=linux-kernel@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.