From: Thierry Reding <thierry.reding@gmail•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org,
Stephen Warren <swarren@wwwdotorg•org>,
Olof Johansson <olof@lixom•net>
Subject: linux-next fixes
Date: Fri, 1 Nov 2013 10:36:39 +0100 [thread overview]
Message-ID: <20131101093638.GE27864@ulmo.nvidia.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1428 bytes --]
Hi Stephen,
There have been some discussions lately revolving around the topic of
linux-next fixes. That is, commits that people come up with over the
course of a day to fix issues found in the latest linux-next trees.
It's a fact that many people rely on linux-next for everyday work, so
whenever things break in linux-next a lot of people end up chasing the
same bugs and posting the same patches (or not posting them for that
matter).
A lot of developer time is wasted that way, so I originally proposed
that we could set up a separate linux-next-fixes tree where we collect
patches of interest. I volunteer to do that, since, well, I'm doing it
anyway as part of my daily routine. Timezone-wise it also fits pretty
well, since I usually start my day sometime around when you publish
linux-next.
If we can establish a canonical location where such fixes are
accumulated, people could fetch those at the same time they fetch the
linux-next tree and automatically get fixes.
One idea was to carry those fixes within the linux-next tree, within
separate tags (next-YYYYMMDD-fixes). If you don't feel comfortable with
that I suppose we could also set up a separate repository. It that case
I think it would still make sense to run it as part of the "Linux Next
Group" on kernel.org.
What do you think? If it's something you'd be okay with I can contact
the administrators to have me added to the linux-next group.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-11-01 9:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 9:36 Thierry Reding [this message]
2013-11-01 15:09 ` linux-next fixes Randy Dunlap
2013-11-04 8:34 ` Thierry Reding
[not found] ` <CAOesGMivU0rz+HgA7HjJ4trdJ5QMu2mbHSpLJQ0PvGOtQR6iNQ@mail.gmail.com>
2013-11-04 8:38 ` Thierry Reding
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=20131101093638.GE27864@ulmo.nvidia.com \
--to=thierry.reding@gmail$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=olof@lixom$(echo .)net \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=swarren@wwwdotorg$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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