Maintenance for linux-lowlatency on Precise

Leann Ogasawara leann.ogasawara at
Tue Sep 4 19:33:22 UTC 2012

Hi Kaj,

I just saw this email here after replying to you on a separate thread
about the maintenance of the lowlatency kernel.  I just wanted to state
publicly here so everyone is aware, I've gotten you in touch with Andy
Whitcroft who is currently helping maintain the lowlatency kernel.  You
and he should be able to work together to transition any maintenance
responsibilities going forward.  Thanks again for your help.


On 09/03/2012 07:52 AM, Kaj Ailomaa wrote:
> I'm Kaj Ailomaa, member of the Ubuntu Studio dev team, and the Ubuntu
> Studio kernel team.
> On behalf of the Ubuntu Studio kernel team, I'd very much like to take
> over maintenance for linux-lowlatency on Precise.
> I'd appreciate some help to get started.
> First of all, I assume would be a good place to put the
> git tree, so I'll need to know how I can get that done. From what I hear,
> Pete Graner is no longer the person to ask about this?
> In the source prepared by Luke
> git:// (the
> currently used source), there is a short maintenance guide in the file
> git remote add precise git://
> git fetch precise
> git fetch precise master
> git rebase refs/remotes/precise/master
> fakeroot debian/rules startnewrelease insertchanges
> git add -u
> git commit -s -m"low-latency: rebased against ubuntu-precise master"
> I found that this might need some polishing.
> At least it seems I need to add a "fakeroot debian/rules clean" in there.
> Perhaps also do a git clean?
> And how do I best handle the changelog?
> No worries about ABI, or any of that?
> Can't say I'm perfectly comfortable with either Ubuntu Kernel git
> practice, or debian/rules (in the same context), so if someone could help
> make the above workflow foolproof, so that I, or anyone else in the
> Ubuntu
> Studio kernel team could merrily just keep updating linux-lowlatency to
> the latest version, that would be awesome.
> Since all we are doing here is updating to the latest Ubuntu release of
> the kernel, I imagine it should be fairly easy to accomplish.
> What else do I need to think about?
> And is there any particular documentation that would help explain this
> particular maintenance problem?

More information about the kernel-team mailing list