Re: BK kernel workflow

From: Roman Zippel (zippel_at_linux-m68k.org)
Date: 10/30/04

  • Next message: Dave Airlie: "Re: 2.6.10-mm1, class_simple_* and GPL addition" 
    Date:	Sat, 30 Oct 2004 13:38:34 +0200 (CEST)
To: Larry McVoy <lm@bitmover.com>

    Hi,

    On Fri, 29 Oct 2004, Larry McVoy wrote:

    > Roman, you can have any of your data that you want, including the metadata
    > such as dates, times, user names, etc. Nobody is hiding that from you,
    > it's all there, you don't need a license to get it, go to bkbits.net and
    > get it.

    I had another closer look and it seems there are good chances to
    reconstruct the data in useable way (especially the rather recently
    added gnupatch and constant link should help). It's not my favourite
    solution, since it has to be pieced together from more parts than really
    necessary, but as proof of concept it should be interesting. So far I
    stayed away from this, because of the traffic this will cause and your
    previous disapproval of causing such traffic, but I can assure you I do my
    best to keep it to a minimum.

    > > To make this easier to understand for everyone, here is a simple example:
    > > a very simple network protocol would be to extend the current commit mails
    > > with the identifiers one can already find in bkcvs, so they can be put
    > > into the correct order.
    >
    > That's not a network protocol, just change the bloody commit trigger.
    > I don't care if you get that information, if you want it, have at it.

    I'm still a little confused how this matches your earlier statement, if
    you had said this earlier, we could have cut the whole thing short and I
    could have avoided getting roasted by Linus.
    Anyway, I don't really care and thanks for the offer, I certainly will
    come back to it (although not immediately).

    bye, Roman
    -
    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/

  • Next message: Dave Airlie: "Re: 2.6.10-mm1, class_simple_* and GPL addition"

    Relevant Pages

    • Re: BK kernel workflow
      ... Roman, you can have any of your data that you want, including the metadata ... That's not a network protocol, just change the bloody commit trigger. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Fw: signed kernel modules?
      ... On an Intel test board. ... I did a module signing patch some years ago. ... All I say is, take care. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: WINE + NX (No eXecute) support for x86, 2.6.7-rc2-bk2
      ... if there is no standard, ... > If you don't care about binary compatability, ... At least some people out there seem to care about it. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: BK kernel workflow
      ... > I just care that there is some sanity in the discussion. ... BK really shines when you have people above ... and below (other developers) you. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Autoregulate swappiness & inactivation
      ... How much RAM do you have? ... Page reclaim doesn't really know or care about processes, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)