![]() | |||||||||||||
Messages in this thread |
> > > > I always thought that that is what the bk-commit mailing lists were > > > > for? I could be wrong about that, not having used BitKeeper - if so, > > > > what are they for, and would it not be possible to simply have a > > > > mailing list which got sent a diff every time Linus' updated his tree?> > > > > > The latest diff against the last-released kernel is always available > > > at http://www.kernel.org/pub/linux/kernel/v2.5/testing/cset/> > > > > > "Gzipped full patch from ..."> > > > So it's perfectly possible to poll> > http://www.kernel.org/pub/linux/kernel/v2.5/testing/cset/ every half > > hour or so, > > Well, the diff is made daily, at some relatively early time during the > morning in one of the time zones continental US is in. I think it's 4am > GMT -0800, but I could be wrong. Are you sure? At the moment, the latest changeset is 1.1027, made at 12:49:07 -08:00 today. That's just under four hours ago. In any case, it would be better not to have to poll a website to get updates, but have them actively delivered by smtp, which brings us back to what I first suggested: Why can't we have a mailing list that sends out a diff for each update? That way, all you need is: :0 * ^X-Mailing-List: up-to-the-second-linux-patches | /usr/local/bin/apply_patches and #!/bin/sh cd /usr/src/linux-current cat | patch -p1 mail $username John, - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-03-22 12:33 [from the cache] ©2003-2008 | |||||||||||||