BK kernel workflow
Quoted 3 lines · Larry McVoy
we're working bug database integration, we're working
on review queues, we're working on project management, we're working on large binary management, etc.
How about support for backporting patches, e.g. backport csets
1.2000.4.120 and 1.2000.12.16 to kernel 2.6.9? I could see no way to get bk to spit out these two changes as patches against 2.6.9. Given all the info in there this should be trivial...
But first you should write some actual documentation and fix your programs
so they emit error messages when something goes wrong:
[me@d4 linux-2.6]$ bk c2r [email protected] mm/vmscan.c
[me@d4 linux-2.6]$ <--- what???
[me@d4 linux-2.6]$ bk tags
<snip>
[email protected], 2004-10-18 11:50:06-07:00, [email protected]
Linux 2.6.9
TAG: v2.6.9
<snip>
[me@d4 linux-2.6]$ bk c2r -r1.1988.97.17 mm/vmscan.c
1.231
'bk help terms' says a tag can be used, but apparently not and there's
no error message.
Then there's this one:
[me@d4 linux-2.6]$ bk difftool -rv2.6.8 -rv2.6.9 mm/vmscan.c <--- forgot the @
child process exited abnormally <--- hee hee!
I like the way the GUI flashes up on the screen then abruptly disappears, leaving
the user wondering what happened.
Quoted 2 lines
The list goes on, if anyone wants to come work on it we are always looking for good systems people and we pay well.
But you're located in a large American metro area, a.k.a. "hell on earth."
--Chuck Ebbert 26-Oct-04 03:19:25
Quoted 10 lines · Chuck Ebbert
Quoted 3 lines · Larry McVoy
we're working bug database integration, we're working
on review queues, we're working on project management, we're working on large binary management, etc.How about support for backporting patches, e.g. backport csets
1.2000.4.120 and 1.2000.12.16 to kernel 2.6.9? I could see no way to get bk to spit out these two changes as patches against 2.6.9. Given all the info in there this should be trivial...
Trivial? Sure, if the patches apply cleanly. Not trivial if the changesets have other changesets in the way.
But I have a 70 line shell script which does this, I'm not sure why you can't write the same thing.
Quoted 5 lines
But first you should write some actual documentation and fix your programs
so they emit error messages when something goes wrong:[me@d4 linux-2.6]$ bk c2r [email protected]
mm/vmscan.c
[me@d4 linux-2.6]$ <--- what???
That's because you didn't read the documentation which you appear to love so much.
work /tmp/linux-2.5 bk c2r -rv2.6.9 mm/vmscan.c
1.231
Quoted 2 lines
'bk help terms' says a tag can be used, but apparently not and there's
no error message.
You passed a legal rev syntax to the command. I can't help it if you don't understand the tool.
Quoted 7 lines
Then there's this one:
[me@d4 linux-2.6]$ bk difftool -rv2.6.8 -rv2.6.9
mm/vmscan.c<--- forgot the @
child process exited abnormally <--- hee hee!I like the way the GUI flashes up on the screen then abruptly disappears, leaving
the user wondering what happened.
You know, I like the way you politely offer to help out by sending in patches to the documentation for this tool which you get to use for free. You are an inspiration to us and you are just the sort of user we love to help.
Quoted 4 lines
Quoted 2 lines
The list goes on, if anyone wants to come work on it we are always looking for good systems people and we pay well.
But you're located in a large American metro area, a.k.a. "hell on earth."
No worries, Chuck, after careful consideration of your skills we don't see a match at this time. But we'll keep your resume on file and thanks for your interest.
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitkeeper.com
Quoted 2 lines · Larry McVoy
That's because you didn't read the documentation which you appear to love so much.
Well, Larry, to be perfectly honest - the documentation is ... terse, at the moment.
Yes, I know, documentation isn't fun - it probably needs an editor to go over it and say, "What assumptions should we make about the knowledge a user has?" and then try really hard to keep that list *short* and strictly adhered to in all the pages.
Oh, and I *do* play a paying customer at my day job. Just some days I wish the documentation was a little more helpful. (Specifically, you desperately need more examples of triggers.)
Signature · 2 lines
Ryan Anderson sometimes Pug Majere
Quoted 6 lines · Ryan Anderson
Quoted 2 lines · Larry McVoy
That's because you didn't read the documentation which you appear to love so much.
Well, Larry, to be perfectly honest - the documentation is ... terse, at the moment.
Yes, we know. On the other hand, we're probably pushing 60,000 users or so who have figured it out by tinkering with the tool. There is no question that there needs to be a BitKeeper book or at least a much more expanded and updated userguide.
Quoted 4 lines
Yes, I know, documentation isn't fun - it probably needs an editor to go over it and say, "What assumptions should we make about the knowledge a user has?" and then try really hard to keep that list *short* and strictly adhered to in all the pages.
Yup. We have an open req for a docs person, if you know someone who wants a fulltime job in the Bay Area or an incredibly exceptional remote person we're very interested (and I'll shut up about that, I'm not trying to use the list for free job advertising, just don't want to create the impression that we don't recognize the issues).
Quoted 3 lines
Oh, and I *do* play a paying customer at my day job. Just some days I wish the documentation was a little more helpful. (Specifically, you desperately need more examples of triggers.)
Well if you are paying your support includes that sort of help. Call us up and ask for examples or send mail to support and ask for help. Even if you aren't paying you can always ask, if we can we help people out promptly.
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitkeeper.com