From: Thierry Reding <thierry.reding@gmail•com>
To: Randy Dunlap <rdunlap@infradead•org>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org,
Stephen Warren <swarren@wwwdotorg•org>,
Olof Johansson <olof@lixom•net>
Subject: Re: linux-next fixes
Date: Mon, 4 Nov 2013 09:34:30 +0100 [thread overview]
Message-ID: <20131104083429.GA27445@ulmo.nvidia.com> (raw)
In-Reply-To: <5273C445.7060900@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 2023 bytes --]
On Fri, Nov 01, 2013 at 08:09:57AM -0700, Randy Dunlap wrote:
> On 11/01/13 02:36, Thierry Reding wrote:
> > 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.
>
> Stephen has had a location for linux-next fixes for quite some time now --
> in the linux-next tree itself.
>
> Apparently Olof objected to this and you agreed with him.
> and I object to not having the fixes in the linux-next tree.
What I did agree to was a compromise. I do see some sense in not
carrying all the fixes in linux-next so that the actual state of
brokenness is reflected.
But I also think that for everyone using linux-next for daily work it
makes sense to have these patches in a central location in order to
minimize duplicate work.
> Maybe Stephen can work it out. :)
If nobody wants to have this in linux-next itself, then I still plan on
maintaining a tree for myself so that people that work in the same areas
in a later timezone don't have to duplicate all of that.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-11-04 8:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 9:36 linux-next fixes Thierry Reding
2013-11-01 15:09 ` Randy Dunlap
2013-11-04 8:34 ` Thierry Reding [this message]
[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=20131104083429.GA27445@ulmo.nvidia.com \
--to=thierry.reding@gmail$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=olof@lixom$(echo .)net \
--cc=rdunlap@infradead$(echo .)org \
--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