On Mon, 2005-02-14 at 19:01 -0800, Larry McVoy wrote: > Would the tarball + patch server suffice for you? We could make a > ChangeSet file which had bk changes -v output in it and that would > give you a fairly useful set of version information. For those who > don't know, bk changes -v is output in time sorted order of changesets > with the changeset comments then each file's comments like the output > below. >
This is perfect for me. The only time I've ever used BK was when someone told me that I needed the lastest snapshot from the bk-tree. What I do with the kernel is to port it, write drivers or customize it for customers. So I'm not in the development part of the kernel (although I'll report bugs and fixes when I find them). I really believe that the majority that download the kernel from BK are doing things like I am and not part of the core development team. Currently, I'm working on a customization of Ingo's RT version, so really at the moment I don't even need access to BK. But with my previous job, I was downloading the bk version quite a lot. But just to get the latest updates. So what you have suggested would have been all that I needed. As I've mentioned, earlier. I work from job to job and my needs change with each one. I joined in this discussion because it could have affected me quite a bit, since someday I might be hired to work on a SCM tool, and I'm very careful about NDAs and the like. -- Steve PS - I'm packing up now to drive to Boston. See everyone at LinuxWorld ;-) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
