BK->CVS (real time mirror)
[BK is locking up our data]
[BitMover has to give us our data in an open format] [The BK pill is oh-so-bitter]
[My tummy hurts and it's Larry's fault]
Boo hoo, cry me a river.
Those of you complaining ought to at least look before you complain. You just assumed that we were screwing you and you couldn't be bothered to verify it before you complained. We didn't screw you at all, all the data is there. And BK itself has always had the ability to export any data in any format, if you read the man pages you might notice that, but that would be too much work, it's easier to complain.
If you had actually gone and looked at the CVS repository you would have seen that there is nothing of value missing, in almost 100% of the files, the full revision history is preserved:
CVS: 110,076 deltas over all files
BK: 121,891 deltas over all files
You guys don't have that much parallelism in your files and the exporter is capturing all that it can which is virtually everything. It's worth noting that many deltas in BK are just event recorders, they are just empty merge delta noise and in fact many people have asked us to get rid of them. Once again, it's easier to complain than think. I'm detecting a trend.
The graph traversal managed to capture an amazing amount of information, it's bloody awesome, which you might have noticed if you had looked. But, nooooo, let's just piss and moan. What a bunch of friggin' whiners.
The next time you open your mouth, the words that come out of it should be "thank you". Nothing else, just that. If you can't say something nice, now is a good time to say nothing at all because we are sick and tired of dealing with people who complain far more than they code. I'm serious, we've done way more than anyone could reasonably expect and you react with no basis in fact, assume bad things that aren't true, don't bother to look to see if there is a real problem, and don't bother to say thanks. Aren't you the slightest bit ashamed of your behaviour?
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Hi,
Quoted 6 lines · Larry McVoy
Those of you complaining ought to at least look before you complain. You just assumed that we were screwing you and you couldn't be bothered to verify it before you complained. We didn't screw you at all, all the data is there. And BK itself has always had the ability to export any data in any format, if you read the man pages you might notice that, but that would be too much work, it's easier to complain.
Well, exactly the people, who are most interested in the complete data, cannot do this, because they are not allowed to do this. They have to find someone else to extract the data.
Quoted 4 lines
But, nooooo, let's just piss and moan. What a bunch of friggin' whiners.
The next time you open your mouth, the words that come out of it should be "thank you". Nothing else, just that.
Your whining is getting more and more unbearable. If you don't stop with your insults, "fuck you" is the only thing you will hear. :-(
bye, Roman
Quoted 2 lines
CVS: 110,076 deltas over all files
BK: 121,891 deltas over all files
(I can recalculate this if you tell me how many of the BK ones are empty
merge pointers)
90.31%
I wasn't far off by saying 90%. And don't tell me I can get all the data, when in fact, I can't. Unless of course you give me an explicit variance from your license, I pay for a license, or I get someone else with BK to get me the data.
Larry, I am not trying to knock your efforts for the kernel. I am going on record as saying "thank you, Larry". Linus has been much more productive since using BK. The kernel patch quality and productivity of the core kernel developers has increased. A new paradigm in source control has come about.
But being a person who also has certain beliefs, I am not going to stand on the side lines and watch the fight. Please don't drop me into the pool of people who believe all source should be free. I work for companies that retain some of their IP for good reason. I have signed NDA's to get at source and work on things that I cannot give out for free. I'm ok with that choice for a company. What I am not ok with, is seeing something that I work with everyday slowly becoming engulfed in gray area.
The kernel's revision history is always available. I get the cset emails. I can extract all the info I want manually.
The problem I have is that you are going to make it so that the original files that hold this data cannot be extracted in any meaningful way without your tools. So if bitkeeper suddenly could not be used by Linus or any others, for whatever reason, we are locked out of that original dataset.
Signature · 4 lines
Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ Deqo - http://www.deqo.com/
Quoted 7 lines · Ben Collins
Quoted 2 lines
CVS: 110,076 deltas over all files
BK: 121,891 deltas over all files(I can recalculate this if you tell me how many of the BK ones are empty
merge pointers)90.31%
In the linux-2.5 tree there are 19300 changesets, of which there are 2705 empty changesets - 14%.
Public information that does not require a license to read.
Quoted 2 lines
I wasn't far off by saying 90%. And don't tell me I can get all the data, when in fact, I can't.
What kind of data is actually _missing_ in the CVS repository. Whit data I understand something usefull!
Judging based on above numbers does not make much sense to me. How does CVS handle a cset where the same patch got applied twice, does that count as a delta or not. Does that count as missing data? Empty csets touching 20 files - does that count as deltas etc. See, lots of open questions.
Quoted 3 lines
Unless of course you give me an explicit
variance from your license, I pay for a license, or I get someone else with BK to get me the data.
Browsing linux.bkbits.net does not require a license - or?
Quoted 3 lines
What I am not ok with, is
seeing something that I work with everyday slowly becoming engulfed in gray area.
Opinions vary of course. What I have seen is that the S/N ratio has increased on lkml due to usage of BK, but...
1) Errors are fixed sooner when Linus apply patches that has errors
2) "make defconfig" can always compile on new kernel versions
3) I can follow what has been accepted in the kernel
4) i can generate patches that does not reject due to other changes in a tee I cannot access
5) My "diff" patches get applied and credited to me
6) Valueable comments are preserved when patches are applied
7) The kernel src has become accessible in more (not less) formats
8) The changelogs posted upon release has been much more informative
So I simply do not recognize the pattern that "becoming engulfed". I have even better access to the kernel src that I had in the past.
Several options exist, only one of them require BK.
Now I even have access via CVS (not that I plan to use it)
As a happy BK user I get frustrated reading also this negative stuff, and wanted to give Larry & Co a heads up.
A lot has improved after introducing BK.
But I see that whatever Bitmover does that is (by some persons) seen as negative.
Sam
Quoted 11 lines · Larry McVoy
[BK is locking up our data]
[BitMover has to give us our data in an open format] [The BK pill is oh-so-bitter]
[My tummy hurts and it's Larry's fault]Boo hoo, cry me a river.
Those of you complaining ought to at least look before you complain. You just assumed that we were screwing you and you couldn't be bothered to verify it before you complained. We didn't screw you at all, all the data is there.
Larry, please don't fall into that trap.
There will _always_ be people to whine at you. For _ever_, and even longer if your business remains healthy.
There was a conflict issue before since one was forced into using BK in order to have real time access to the very latest changeset in the reference development kernel repository. Now that this issue has been resolved there is rationally nothing else to complain about. Those who want to/can use BK just do it, those who don't want to/can't use BK aren't penalized anymore with regard to access to the very data they care about.
Oh then why are they still whining? Because they are humans with their own ego, pride and beliefs. Maybe they are upset because you just removed the best argument they had against BK up to now, maybe they have a hard time convincing themselves that BK is superior because you managed to create a favorable climate for its rapid development, maybe they are religious extremists (read Free Software extremists) always about to go on a crusade for the only True Way of living, etc. There's nothing you can do to help those irrational issues besides just ignoring them. Linus himself just mentioned recently that he's getting more and more effective at ignoring BSD extremists for his Linux licensing choice. It's about time you do the same.
So please Larry don't let your feelings be trapped into critics that will _never_ end. There will still be people to disagree with your licensing decisions, to hate your business model, and to simply hate you. But if _you_ know that you've made everything to make this part of the world a better place then it should be enough to make you feel good. Seeking for public rewards is mostly impossible as long as you're alive.
Quoted 2 lines
The next time you open your mouth, the words that come out of it should be "thank you". Nothing else, just that.
Larry, I say "Thank you".
Quoted 3 lines
If you can't say something nice, now is a good time to say nothing at all because we are sick and tired of dealing with people who complain far more than they code.
Then why do you let them turn you down? Why are those people so credible to you so you feel you must listen to them?
Quoted 4 lines
I'm serious, we've done way more than anyone could reasonably expect and you react with no basis in fact, assume bad things that aren't true, don't bother to look to see if there is a real problem, and don't bother to say thanks.
If you expect that aspect of human beings to change frankly you are dreaming. I'm sorry to make it sound bad but that's reality. There will _always_ be people to disagree and whine at something, and statistically that something will be BK from time to time. Those who are happy with the system usually just say nothing unfortunately and they go back to coding right away.
Nicolas
Quoted 10 lines · Ben Collins
Quoted 2 lines
CVS: 110,076 deltas over all files
BK: 121,891 deltas over all files(I can recalculate this if you tell me how many of the BK ones are empty
merge pointers)90.31%
I wasn't far off by saying 90%. And don't tell me I can get all the data, when in fact, I can't.
What the hell don't you understand in the fact that the remaining 10% is USELESS DATA WITH NO VALUE WHAT SO EVER ???
Oh of course you won't trust Larry and maybe he's trying to screw you with that 10% by carefully crafting essential details in there so you'll end up being forced into buying a BK license otherwise you won't be able to make any sense of what happened in the source tree, or even make it compile! Isn't it pure paranoia?
Please, get a life.
Nicolas
Hi,
Quoted 3 lines · Sam Ravnborg
As a happy BK user I get frustrated reading also this negative stuff, and wanted to give Larry & Co a heads up.
A lot has improved after introducing BK.
Nobody denies that things have become better, but Larry's arrogance makes it extremely difficult to be thankful for that. Somehow Larry assumes everyone should just use bk and be happy (and don't work on other SCM systems), but that would be like asking that all people should just use vimacs.
bye, Roman
Quoted 3 lines
Quoted 1 line
Boo hoo, cry me a river.
Larry, please don't fall into that trap.
I'm not, I was just blowing off steam. Ya gotta admit it is pretty unreasonable for people to complain without even checking. I'm tailing the history log in the CVS repository, there have been 3 or 4 downloads since last night, that's it. All that whining and no looking at all.
Quoted 6 lines
Quoted 3 lines
If you can't say something nice, now is a good time to say nothing at all because we are sick and tired of dealing with people who complain far more than they code.
Then why do you let them turn you down? Why are those people so credible to you so you feel you must listen to them?
Well, I agree that they should be able to get at the information in a neutral way. I guess it was unrealistic, but I was expecting that people would go download the CVS tree and poke around and see if it is what they wanted. We could have had a nice technical discussion about what was missing, if anything. If the discussion had happened, they would have found out that even for the missing deltas we captured the information.
Here's an example. Suppose the graph is like
1.1 (torvalds) -> 1.2 (alan) -> 1.3 (sct) -> 1.4 (torvalds) \ / \-> 1.1.1.1 (davej) --------/
and we picked the straight 1.1 to 1.4 path. When we created the CVS 1.4 delta, we knew that it was a merge delta and we needed to capture the data off on the branch. We already capture the contents, the missing part is what davej may have typed in as comments. We capture that as well, it looks like this:
revision 1.342
date: 2003/03/07 15:39:16; author: torvalds; state: Exp; lines: +7 -1
[PATCH] kbuild: Smart notation for non-verbose output
2003/03/05 19:50:27-06:00 kai
kbuild: Make build stop on vmlinux link error
(Logical change 1.8166)That particular example is from the top level Makefile, Linus merged in Kai's work and we added the "kbuild: Make build stop on vmlinux link error" comments from the merged in delta. If there were more than one delta, they get merged as well, so the rlog output is completely accurate.
So we actually captured 100% of the checkin information, both in data files and in the pseudo ChangeSet file, not one byte of that is lost. All we did is collapse all the branches into the longest possible straight line, which is actually for many purposes nicer than the rats nets that you get with BK.
Anyway, to get back to your question, what gets me down is that we did what we believe to be the absolute perfect job. All the data is captured, all the checkin comments are captured, we made all the dates go forward properly so that diffs would work, there is nothing wrong with the CVS tree, it's perfect. It would have been nice if people had actually looked at it. You can, go look at
http://linux.bkbits.net:8080/linux-2.5/hist/Makefile
and compare it to this:
cvs -d:pserver:[email protected]:/home/cvs rlog linux-2.5/Makefile
Poke around, play with your favorite files, you'll see your checkin comments, we didn't lose anything at all. Apparently, that's too much to ask, and that's what gets me down. I don't expect people to say "rah rah, you guys are great" but I did expect the people who have been bitching non-stop that they can't get what they want would at least go see if they could get it now. Silence would be a more than adequate reward as far as I'm concerned, I don't need the strokes but I am sick of the baseless whining. Fear not, I'll get over it.
What I expected from Ben was a polite request for a tarball of the CVS tree so he could go convert it to SVN and see if all his checkin comments are there. No such request, polite or otherwise, has happened, from him or anyone else. So it's becoming apparent that the whole data/metadata whatever is a red herring, they just want to flame. Whatever, somebody will get some good use out of the CVS trees, if I were in your shoes I'd want them as a safety net so it's cool they exist.
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Quoted 13 lines · Nicolas Pitre
Quoted 10 lines · Ben Collins
Quoted 2 lines
CVS: 110,076 deltas over all files
BK: 121,891 deltas over all files(I can recalculate this if you tell me how many of the BK ones are empty
merge pointers)90.31%
I wasn't far off by saying 90%. And don't tell me I can get all the data, when in fact, I can't.
Quoted 9 lines
What the hell don't you understand in the fact that the remaining 10% is USELESS DATA WITH NO VALUE WHAT SO EVER ???
Oh of course you won't trust Larry and maybe he's trying to screw you with that 10% by carefully crafting essential details in there so you'll end up being forced into buying a BK license otherwise you won't be able to make any sense of what happened in the source tree, or even make it compile! Isn't it pure paranoia?
What part of the structure of the BK repo don't you understand? Didn'y you pay attention to what Larry said? The tree looks like branches that always return to the trunk. To put this into CVS, he had to choose a line of those branches that contained the _most_ changesets (which doesn't always equate to the most important, or largest deltas). There are some changesets on the side that are not included here. Are all of those changesets empty merges? No.
Signature · 4 lines
Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ Deqo - http://www.deqo.com/
Quoted 5 lines
So we actually captured 100% of the checkin information, both in data files and in the pseudo ChangeSet file, not one byte of that is lost. All we did is collapse all the branches into the longest possible straight line, which is actually for many purposes nicer than the rats nets that you get with BK.
Now that wasn't apparent from your original post. You made it sound more like meta-data was missing (we all know that via the merges, as long as you picked a line, none of the diffs were missing).
That's good to know, and makes my whole rant kind of pointless now.
I still don't like your move to change the SCCS format. Regardless of your intentions, it makes my gut hurt. That doesn't mean I don't like you or what you do. I never said I didn't in this discussion, although some people decided to get rude on my behalf, when they shouldn't which triggered others to target people in the discussion with rudeness, which shouldn't have happened.
I can dislike the change, just the same as you can license your product and develop it any way you want. The day someone takes that right away from either of us is when we have a real problem.
Signature · 4 lines
Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ Deqo - http://www.deqo.com/
Quoted 7 lines
Quoted 6 lines
Oh of course you won't trust Larry and maybe he's trying to screw you with that 10% by carefully crafting essential details in there so you'll end up being forced into buying a BK license otherwise you won't be able to make any sense of what happened in the source tree, or even make it compile! Isn't it pure paranoia?
Quoted 7 lines
What part of the structure of the BK repo don't you understand? Didn'y you pay attention to what Larry said? The tree looks like branches that always return to the trunk. To put this into CVS, he had to choose a line of those branches that contained the _most_ changesets (which doesn't always equate to the most important, or largest deltas). There are some changesets on the side that are not included here. Are all of those changesets empty merges? No.
s/changeset/metadata/ to clarify my point, which is of no use now.
Signature · 4 lines
Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ Deqo - http://www.deqo.com/
Quoted 6 lines · Larry McVoy
is what davej may have typed in as comments. We capture that as well, it looks like this:
revision 1.342 date: 2003/03/07 15:39:16; author: torvalds; state: Exp; lines: +7 -1 [PATCH] kbuild: Smart notation for non-verbose output
Ho humm, I did this not Linus.
Checked the web which is correct.
Same goes for 1.340 for the Makefile. Kai did it, not Linus.
Sam
Quoted 4 lines · Sam Ravnborg
Quoted 3 lines · Larry McVoy
is what davej may have typed in as comments. We capture that as well, it looks like this:
Quoted 8 lines
Quoted 3 lines
revision 1.342 date: 2003/03/07 15:39:16; author: torvalds; state: Exp; lines: +7 -1 [PATCH] kbuild: Smart notation for non-verbose outputHo humm, I did this not Linus.
Checked the web which is correct.Same goes for 1.340 for the
Makefile. Kai did it, not Linus.
Right you are, looks like a bug. I'm digging into it. I suspect I have an off by one delta error but I'm not sure. Please be aware that it takes 4.5 hours of CPU on our fastest machine to do the conversion so fixed trees are probably due tomorrow.
If you want to help, see if you can find a pattern the user names, being aware that the revision numbers don't map one to one.
Thanks for pointing this out, this was what I wanted.
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Quoted 7 lines · Ben Collins
What part of the structure of the BK repo don't you understand? Didn'y you pay attention to what Larry said? The tree looks like branches that always return to the trunk. To put this into CVS, he had to choose a line of those branches that contained the _most_ changesets (which doesn't always equate to the most important, or largest deltas). There are some changesets on the side that are not included here. Are all of those changesets empty merges? No.
What are you attempting to insinuate?
I think BK had has positive benefits to all Linux kernel hackers, whether or not they use BitKeeper. The current patch flow is pretty amazing, and we seemed to have avoided the Linus burn-out that threatened to come to pass pre-BK.
It's getting to the point where it seems like every time BitMover does something to appease the non-BK crowd, people (a) read evil intentions into the action, and/or (b) just keep asking for more.
Can someone please tell what is the overall point? what is the endgame here? what is a concrete technical solution that will satisfy you (Ben), Pavel, and everybody else?
Jeff
Quoted 24 lines · Ben Collins
Quoted 13 lines · Nicolas Pitre
Quoted 10 lines · Ben Collins
Quoted 2 lines
CVS: 110,076 deltas over all files
BK: 121,891 deltas over all files(I can recalculate this if you tell me how many of the BK ones are empty
merge pointers)90.31%
I wasn't far off by saying 90%. And don't tell me I can get all the data, when in fact, I can't.
Quoted 9 lines
What the hell don't you understand in the fact that the remaining 10% is USELESS DATA WITH NO VALUE WHAT SO EVER ???
Oh of course you won't trust Larry and maybe he's trying to screw you with that 10% by carefully crafting essential details in there so you'll end up being forced into buying a BK license otherwise you won't be able to make any sense of what happened in the source tree, or even make it compile! Isn't it pure paranoia?
Quoted 7 lines
What part of the structure of the BK repo don't you understand? Didn'y you pay attention to what Larry said? The tree looks like branches that always return to the trunk. To put this into CVS, he had to choose a line of those branches that contained the _most_ changesets (which doesn't always equate to the most important, or largest deltas). There are some changesets on the side that are not included here. Are all of those changesets empty merges? No.
Did you at least care to inspect the resulting CVS repository before complaining? It looks you didn't, and still so quick to dismiss what Larry and co have done.
Nicolas
Quoted 4 lines · Sam Ravnborg
Quoted 3 lines · Larry McVoy
is what davej may have typed in as comments. We capture that as well, it looks like this:
Quoted 8 lines
Quoted 3 lines
revision 1.342 date: 2003/03/07 15:39:16; author: torvalds; state: Exp; lines: +7 -1 [PATCH] kbuild: Smart notation for non-verbose outputHo humm, I did this not Linus.
Checked the web which is correct.Same goes for 1.340 for the
Makefile. Kai did it, not Linus.
It seems that some things that should have been attributed to me (or others) are listed as from torvalds too.
Example: drivers/char/tty_io.c
revision 1.59
date: 2003/03/04 02:13:05; author: torvalds; state: Exp; lines: +4 -6 small tty irq race fix
(Logical change 1.8144)
Nicolas
Quoted 10 lines · Nicolas Pitre
It seems that some things that should have been attributed to me (or others) are listed as from torvalds too.
Example:
drivers/char/tty_io.crevision 1.59
date: 2003/03/04 02:13:05; author: torvalds; state: Exp; lines: +4 -6 small tty irq race fix(Logical change 1.8144)
Yeah, I'm almost there, I'm pretty sure that what is happening is that the user name is being picked up from the changeset which is current in the path. We extract the user name and put it in the comments but I don't see where we set $LOGNAME before doing the ci.
So here's a question. Suppose we have a series of deltas being clumped together in a file. All made by different people. Whose name wins? My gut is to sort them, run them through uniq -c, and take the top one. The other idea is to count up lines inserted/deleted over each delta and take the user who has done the most work.
Thoughts?
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Quoted 28 lines · Larry McVoy
Well, I agree that they should be able to get at the information in a neutral way. I guess it was unrealistic, but I was expecting that people would go download the CVS tree and poke around and see if it is what they wanted. We could have had a nice technical discussion about what was missing, if anything. If the discussion had happened, they would have found out that even for the missing deltas we captured the information.
Here's an example. Suppose the graph is like
1.1 (torvalds) -> 1.2 (alan) -> 1.3 (sct) -> 1.4 (torvalds) \ / \-> 1.1.1.1 (davej) --------/and we picked the straight 1.1 to 1.4 path. When we created the CVS 1.4 delta, we knew that it was a merge delta and we needed to capture the data off on the branch. We already capture the contents, the missing part is what davej may have typed in as comments. We capture that as well, it looks like this:
revision 1.342 date: 2003/03/07 15:39:16; author: torvalds; state: Exp; lines: +7 -1 [PATCH] kbuild: Smart notation for non-verbose output 2003/03/05 19:50:27-06:00 kai kbuild: Make build stop on vmlinux link error (Logical change 1.8166)
Quoted 4 lines
That particular example is from the top level
Makefile, Linus merged in Kai's work and we added the "kbuild: Make build stop on vmlinux link error" comments from the merged in delta. If there were more than one delta, they get merged as well, so the rlog output is completely accurate.
Larry, this brings up something I was meaning to ask you before this thread exploded. What happens to those "logical change" numbers over time?
My understanding (since you mentioned ~ 3 minute latency on BK pushes, not five hour latency) was that future changes would go into CVS incrementally. As far as I understand the "revision numbers" that BK uses, they're subject to change. Based on what trees Linus merges from, a revision number in his repository may not always have the same number. So the comments will become out-of-date and inaccurate.
Or am I wrong about the potential for change within a single repository?
Signature · 2 lines
Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer
Quoted 17 lines · Larry McVoy
Quoted 10 lines · Nicolas Pitre
It seems that some things that should have been attributed to me (or others) are listed as from torvalds too.
Example:
drivers/char/tty_io.crevision 1.59
date: 2003/03/04 02:13:05; author: torvalds; state: Exp; lines: +4 -6 small tty irq race fix(Logical change 1.8144)
Yeah, I'm almost there, I'm pretty sure that what is happening is that the user name is being picked up from the changeset which is current in the path. We extract the user name and put it in the comments but I don't see where we set $LOGNAME before doing the ci.
Quoted 7 lines
So here's a question. Suppose we have a series of deltas being clumped together in a file. All made by different people. Whose name wins? My gut is to sort them, run them through uniq -c, and take the top one. The other idea is to count up lines inserted/deleted over each delta and take the user who has done the most work.
Thoughts?
And/or add them all into the CVS log comment, with their full names when available.
If such information can't be made into CVS directly then adding those to the log comment is certainly the best thing to do.
Nicolas
Quoted 3 lines
Larry, this brings up something I was meaning to ask you before this thread exploded. What happens to those "logical change" numbers over time?
They are stable in the CVS tree because the CVS tree isn't distributed. So "Logical change 1.900" in the context of the exported CVS tree is always the same thing. That's one advantage centralized has, things don't shift around on you.
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Quoted 17 lines · Larry McVoy
Quoted 10 lines · Nicolas Pitre
It seems that some things that should have been attributed to me (or others) are listed as from torvalds too.
Example:
drivers/char/tty_io.crevision 1.59
date: 2003/03/04 02:13:05; author: torvalds; state: Exp; lines: +4 -6 small tty irq race fix(Logical change 1.8144)
Yeah, I'm almost there, I'm pretty sure that what is happening is that the user name is being picked up from the changeset which is current in the path. We extract the user name and put it in the comments but I don't see where we set $LOGNAME before doing the ci.
Quoted 7 lines
So here's a question. Suppose we have a series of deltas being clumped together in a file. All made by different people. Whose name wins? My gut is to sort them, run them through uniq -c, and take the top one. The other idea is to count up lines inserted/deleted over each delta and take the user who has done the most work.
Thoughts?
Another option:
Choose the name that _removed_ the most lines.
Reward the desired behaviour. ;)
Wha? Right, back to work.
Eli
--------------------. "If it ain't broke now,
Eli Carter \ it will be soon." -- crypto-gram
eli.carter(a)inet.com `-------------------------------------------------
Quoted 8 lines · Larry McVoy
Quoted 3 lines
Larry, this brings up something I was meaning to ask you before this thread exploded. What happens to those "logical change" numbers over time?
They are stable in the CVS tree because the CVS tree isn't distributed. So "Logical change 1.900" in the context of the exported CVS tree is always the same thing. That's one advantage centralized has, things don't shift around on you.
OK, so the logical change numbers there are only related to the CVS tree, not related to revision numbers in the BK tree being converted? That makes more sense, thank you.
Signature · 2 lines
Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer
Quoted 5 lines · Daniel Jacobowitz
Quoted 4 lines · Larry McVoy
Quoted 3 lines
Larry, this brings up something I was meaning to ask you before this thread exploded. What happens to those "logical change" numbers over time?
Quoted 7 lines
Quoted 4 lines
They are stable in the CVS tree because the CVS tree isn't distributed. So "Logical change 1.900" in the context of the exported CVS tree is always the same thing. That's one advantage centralized has, things don't shift around on you.
OK, so the logical change numbers there are only related to the CVS tree, not related to revision numbers in the BK tree being converted?
Correct. The BK revs are in there though, that's what
BKrev: <long string of bits>
is in the change log.
Quoted 1 line
That makes more sense, thank you.
Hey cool, you're welcome!
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Quoted 8 lines · Larry McVoy
Quoted 3 lines
Larry, this brings up something I was meaning to ask you before this thread exploded. What happens to those "logical change" numbers over time?
They are stable in the CVS tree because the CVS tree isn't distributed. So "Logical change 1.900" in the context of the exported CVS tree is always the same thing. That's one advantage centralized has, things don't shift around on you.
Isn't there a more general problem, though? (I hope I'm wrong)
You want to update the CVS tree near-realtime. However, the longest-path through your graph may change with new merges, but CVS of course cannot cope with already committed data changing (already committed csets may all of a sudden not be in the longest path anymore)? This is a CVS limitation, of course, but still a problem AFAICS.
--Kai
Quoted 11 lines · Kai Germaschewski
Quoted 8 lines · Larry McVoy
Quoted 3 lines
Larry, this brings up something I was meaning to ask you before this thread exploded. What happens to those "logical change" numbers over time?
They are stable in the CVS tree because the CVS tree isn't distributed. So "Logical change 1.900" in the context of the exported CVS tree is always the same thing. That's one advantage centralized has, things don't shift around on you.
Quoted 7 lines
Isn't there a more general problem, though? (I hope I'm wrong)
You want to update the CVS tree near-realtime. However, the longest-path through your graph may change with new merges, but CVS of course cannot cope with already committed data changing (already committed csets may all of a sudden not be in the longest path anymore)? This is a CVS limitation, of course, but still a problem AFAICS.
Yup, you're right, there is a tradeoff between real time updates and best path. We've already seen it in incremental updates.
We were talking about this internally when your mail came in. I suspect it isn't really a problem in practice because we can always redo the entire export from scratch and get an optimal path.
Wayne pointed out that in the cases where it collapses a pile of csets that is usually because Linus pulled some wad from somebody and one could argue the collapse is a good thing. But it depends, sometimes it is and sometimes it isn't. Our commercial users have frequently asked for a way to "collapse the tree and clean up the noise in the graphs", in fact, one called this morning and said "that BK to CVS thing, could that be a BK to cleaner-BK thing?" so opinions vary on what is the perfect granularity.
My belief is that the real time updates is something that people value more than the granularity. You guys can vote and if you reach agreement we'll do what you want.
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
and if you did real-time updates but once a month or so redid the 'longest-path' thing that would change the CVS version info, correct?
David Lang
Quoted 53 lines · Larry McVoy
Date: Wed, 12 Mar 2003 14:01:56 -0800
From: Larry McVoy <[email protected]>
To: Kai Germaschewski <[email protected]>
Cc: Larry McVoy <[email protected]>, [email protected]
Subject: Re: [ANNOUNCE]BK->CVS(real time mirror)Quoted 11 lines · Kai Germaschewski
Quoted 8 lines · Larry McVoy
Quoted 3 lines
Larry, this brings up something I was meaning to ask you before this thread exploded. What happens to those "logical change" numbers over time?
They are stable in the CVS tree because the CVS tree isn't distributed. So "Logical change 1.900" in the context of the exported CVS tree is always the same thing. That's one advantage centralized has, things don't shift around on you.
Quoted 7 lines
Isn't there a more general problem, though? (I hope I'm wrong)
You want to update the CVS tree near-realtime. However, the longest-path through your graph may change with new merges, but CVS of course cannot cope with already committed data changing (already committed csets may all of a sudden not be in the longest path anymore)? This is a CVS limitation, of course, but still a problem AFAICS.
Yup, you're right, there is a tradeoff between real time updates and best path. We've already seen it in incremental updates.
We were talking about this internally when your mail came in. I suspect it isn't really a problem in practice because we can always redo the entire export from scratch and get an optimal path.
Wayne pointed out that in the cases where it collapses a pile of csets that is usually because Linus pulled some wad from somebody and one could argue the collapse is a good thing. But it depends, sometimes it is and sometimes it isn't. Our commercial users have frequently asked for a way to "collapse the tree and clean up the noise in the graphs", in fact, one called this morning and said "that BK to CVS thing, could that be a BK to cleaner-BK thing?" so opinions vary on what is the perfect granularity.
My belief is that the real time updates is something that people value more than the granularity. You guys can vote and if you reach agreement we'll do what you want.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
-
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/
Quoted 2 lines · David Lang
and if you did real-time updates but once a month or so redid the 'longest-path' thing that would change the CVS version info, correct?
Exactly. So if we redo it then anyone who has active CVS workspaces will get the wrong thing when they update if the revs have moved around and they will.
I suspect the right answer is that we do the real time updates, see how it goes, if it starts to suck we'll periodically toss the CVS tree and start over.
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Quoted 11 lines · Larry McVoy
Quoted 2 lines · David Lang
and if you did real-time updates but once a month or so redid the 'longest-path' thing that would change the CVS version info, correct?
Exactly. So if we redo it then anyone who has active CVS workspaces will get the wrong thing when they update if the revs have moved around and they will.
I suspect the right answer is that we do the real time updates, see how it goes, if it starts to suck we'll periodically toss the CVS tree and start over.
What you could do is have a CVS "realtime" branch which is forked from the trunk, say once a week, or whenever Linux makes a point release. On this branch you do incremental updates as they are merged into CVS. When it is time to create a new branch (say for 2.5.99-pre12), you re-do the export from the branch base tag (at 2.5.99-pre11) to the current BK head in an "optimal" way, and retag the "realtime" branch off of the new base tag.
We do this in our current CVS development, and CVS is smart enough to keep local changes over the update and/or generate conflicts. That way, most people can have a simple-but-good trunk to follow, but people who want up-to-the-second updates can have it too, and you don't end up renumbering the CVS revisions for times in the past. It also avoids the need to re-crunch the entire BK repository to get an optimal path (which is only going to get slower as time goes on, and I'm not sure whether Linux development is ahead of or behind Moore's law).
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
Hi,
Quoted 3 lines · Jeff Garzik
It's getting to the point where it seems like every time BitMover does something to appease the non-BK crowd, people (a) read evil intentions into the action, and/or (b) just keep asking for more.
Where did you see anyone asking for more? People are worried, that they suddenly have less. If Larry is taking the ability away to extract information from the SCCS files, something has to replace this. Especially SCM developers are worried that they loose information, the Linux repository is a very valuable resource and since they can't use bk, they always depend on others to get to that information as complete as possible.
Quoted 3 lines
Can someone please tell what is the overall point? what is the endgame here? what is a concrete technical solution that will satisfy you (Ben), Pavel, and everybody else?
Well, all this reminds me a bit of a missionary trying to convert the pagans to the one true god and all the true believers can't understand, why they don't want to be converted. If we could get our preacher to preach a little less, we all could live peacefully together. :-)
bye, Roman
Quoted 8 lines
Quoted 8 lines
Quoted 5 lines
revision 1.59
date: 2003/03/04 02:13:05; author: torvalds; state: Exp; lines: +4 -6 small tty irq race fix(Logical change 1.8144)
Yeah, I'm almost there, I'm pretty sure that what is happening is that the user name is being picked up from the changeset which is current in
OK, I think I have a fix, I'm starting another conversion and going out to dinner. This was a lot harder to fix than I thought, it cost me the whole day. I can't wait until Pavel is doing this crap.
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Quoted 4 lines · Sam Ravnborg
Quoted 3 lines · Larry McVoy
is what davej may have typed in as comments. We capture that as well, it looks like this:
Quoted 8 lines
Quoted 3 lines
revision 1.342 date: 2003/03/07 15:39:16; author: torvalds; state: Exp; lines: +7 -1 [PATCH] kbuild: Smart notation for non-verbose outputHo humm, I did this not Linus.
Checked the web which is correct.Same goes for 1.340 for the
Makefile. Kai did it, not Linus.
There is a "fixed" (I hope) linux-2.4 tree up. We're still converting the 2.5 tree, ETA is about 6 hours (the fix substantially slowed down the coversion process, did I mention that this stuff is a pain?). I'm going out for a while but I'll send out mail when the 2.5 tree is up.
If you have worked on files in 2.4 please go poke at them at
cvs -d:pserver:[email protected]:/home/cvs rlog linux-2.4/<your file>
and see if you think that is accurate. Let me know either way. Thanks.
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Quoted 2 lines · Ben Collins
But being a person who also has certain beliefs, I am not going to stand on the side lines and watch the fight.
Then I guess you'll get killfiled by a lot of people. I don't like bk's licensing either but I'm not going to whine for months about it. Linus knows how people feel about it and he's made a decision to use bk anyway. People have tried to change his mind, and they have failed. If you have a problem with bk, please just ignore it. Send diffs the old way. Why not pick on Microsoft or Adobe? When you complain about Larry trying to steal 10% of your data (wtf? Linus still releases regularly. I don't see how we have any less data than before even without BK), you're wasting your energy and annoying the huge fraction of people who read this mailing list who don't care what software Linus or anyone else wants to run.
The only thing that gets on my nerves is when people don't bother to make GNU patches available. If Larry is able to turn the diff exporter on eventually, this should make the problem almost moot. To someone who doesn't use BK, people posting changesets would essentially just be hosting their patches on bkbits.net. And if they want to host them there, who am I to tell them no, no matter how they get there or what format they're stored in internally?
Apparently linux-2.5/ChangeSet is an empty file?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Larry McVoy <[email protected]> said:
[...]
Quoted 5 lines
So here's a question. Suppose we have a series of deltas being clumped together in a file. All made by different people. Whose name wins? My gut is to sort them, run them through uniq -c, and take the top one. The other idea is to count up lines inserted/deleted over each delta and take the user who has done the most work.
Say Several and add the list to the comment (after sort | uniq)?
Signature · 4 lines
Dr. Horst H. von Brand User #22616 counter.li.org Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513
Quoted 19 lines · Larry McVoy
Quoted 10 lines · Kai Germaschewski
Quoted 8 lines · Larry McVoy
Quoted 3 lines
Larry, this brings up something I was meaning to ask you before this thread exploded. What happens to those "logical change" numbers over time?
They are stable in the CVS tree because the CVS tree isn't distributed. So "Logical change 1.900" in the context of the exported CVS tree is always the same thing. That's one advantage centralized has, things don't shift around on you.
Quoted 7 lines
Isn't there a more general problem, though? (I hope I'm wrong)
You want to update the CVS tree near-realtime. However, the longest-path through your graph may change with new merges, but CVS of course cannot cope with already committed data changing (already committed csets may all of a sudden not be in the longest path anymore)? This is a CVS limitation, of course, but still a problem AFAICS.
Quoted 6 lines
Yup, you're right, there is a tradeoff between real time updates and best path. We've already seen it in incremental updates.
We were talking about this internally when your mail came in. I suspect it isn't really a problem in practice because we can always redo the entire export from scratch and get an optimal path.
Then the CVS tree won't be stable, and so useless to remote people just wanting to "cvs update" their stuff. Or am I missing something here?
Quoted 8 lines
Wayne pointed out that in the cases where it collapses a pile of csets that is usually because Linus pulled some wad from somebody and one could argue the collapse is a good thing. But it depends, sometimes it is and sometimes it isn't. Our commercial users have frequently asked for a way to "collapse the tree and clean up the noise in the graphs", in fact, one called this morning and said "that BK to CVS thing, could that be a BK to cleaner-BK thing?" so opinions vary on what is the perfect granularity.
I'd add the possibility to group csets into super-csets (and so on, why not?), without ever losing the individual pieces. Masoch^Wadventurous folks could then grovel around inside as needed. Linus' 2.5.63 --> 2.5.64 would then just be such a super-cset, separately manipulable.
No, I have no clue of how to do this.
Signature · 4 lines
Dr. Horst H. von Brand User #22616 counter.li.org Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513
Quoted 1 line · Geert Uytterhoeven
Apparently linux-2.5/ChangeSet is an empty file?
Yeah, it's just a place holder for the ChangeSet comments. The changeset boundaries are implicit in the dates and explict with the (Logical change x.y) markers.
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Quoted 4 lines · Sam Ravnborg
Quoted 3 lines · Larry McVoy
is what davej may have typed in as comments. We capture that as well, it looks like this:
Quoted 8 lines
Quoted 3 lines
revision 1.342 date: 2003/03/07 15:39:16; author: torvalds; state: Exp; lines: +7 -1 [PATCH] kbuild: Smart notation for non-verbose outputHo humm, I did this not Linus.
Checked the web which is correct.Same goes for 1.340 for the
Makefile. Kai did it, not Linus.
Can you look over the linux-2.4 tree? I've done another pass on it. The fixes slowed down the export process, we're looking at about 7 hours of CPU time to get the 2.5 tree converted and I just started a run.
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Quoted 6 lines · Larry McVoy
Quoted 1 line · Geert Uytterhoeven
Apparently linux-2.5/ChangeSet is an empty file?
Yeah, it's just a place holder for the ChangeSet comments. The changeset boundaries are implicit in the dates and explict with the (Logical change x.y) markers.
Ah, IC. Then I must have misread your mail, and incorrectly understood that you added a ChangeSet file with a list of comments.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Quoted 6 lines
Quoted 3 lines
I suspect the right answer is that we do the real time updates, see how it goes, if it starts to suck we'll periodically toss the CVS tree and start over.
What you could do is have a CVS "realtime" branch which is forked from the trunk, say once a week, or whenever Linux makes a point release.
I'm not sure it is worth it. If you are using BK, run revtool and look at the recent history in 2.5. I just updated the CVS tree on kernel.bkbits.net and looked carefully at the collapsing it did. It collapsed a pile of Greg's stuff into one cset, but that's actually OK as far as I can tell, it's all related. And there was more work on the other path.
We've done several updates to the 2.5 tree and so far the number of changesets we would have gotten if we had done it all in one pass and the number that we actually got is identical. So maybe the reality of the incremental updates is better than we expected.
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Quoted 2 lines · Ben Collins
or any others, for whatever reason, we are locked out of that original dataset.
true but the missing bits are nearly worthless, I wouldn't be ok with CVS if this wasn't the case. I mean, in the very worst case, we're not totally screwed, we probably won't even notice the difference.
Andrea
Hi,
Quoted 3 lines · Andrea Arcangeli
true but the missing bits are nearly worthless, I wouldn't be ok with CVS if this wasn't the case. I mean, in the very worst case, we're not totally screwed, we probably won't even notice the difference.
The missing bits are absolutely not worthless. They are very useful when you want to test other SCM system to simulate distributed development.
bye, Roman
Quoted 10 lines · Roman Zippel
Hi,
Quoted 3 lines · Andrea Arcangeli
true but the missing bits are nearly worthless, I wouldn't be ok with CVS if this wasn't the case. I mean, in the very worst case, we're not totally screwed, we probably won't even notice the difference.
The missing bits are absolutely not worthless. They are very useful when you want to test other SCM system to simulate distributed development.
This is completely ridiculous. Isn't this a bit too demanding? What will be next?
Be realistic. The missing bits are worthless and add absolutely no value to kernel development which is supposed to be the topic for this mailing list.
It's not the missing bits that will prevent you from making a better alternative to BK or whatever either. If it really does you should consider spending your time on another project. But since I truly believe you are more clever than that I suspect you're just trying to stretch the issue out of reasonable bounds because of your political beliefs.
Nicolas
Quoted 9 lines · Nicolas Pitre
Quoted 7 lines · Roman Zippel
Hi,
Quoted 3 lines · Andrea Arcangeli
true but the missing bits are nearly worthless, I wouldn't be ok with CVS if this wasn't the case. I mean, in the very worst case, we're not totally screwed, we probably won't even notice the difference.
The missing bits are absolutely not worthless. They are very useful when you want to test other SCM system to simulate distributed development.
This is completely ridiculous. Isn't this a bit too demanding?
I think so.
Quoted 2 lines
Be realistic. The missing bits are worthless and add absolutely no value to kernel development which is supposed to be the topic for this mailing list.
They are not useless. It definitely adds value. It's just that it's more than developers had before, and they want all the extra BK gives them without having to say "ok" to a license which they do not like.
Fact is, folks simply forget to make sense sometimes.
Quoted 5 lines
It's not the missing bits that will prevent you from making a better alternative to BK or whatever either. If it really does you should consider spending your time on another project. But since I truly believe you are more clever than that I suspect you're just trying to stretch the issue out of reasonable bounds because of your political beliefs.
Hi,
Quoted 4 lines · Nicolas Pitre
Quoted 2 lines
The missing bits are absolutely not worthless. They are very useful when you want to test other SCM system to simulate distributed development.
This is completely ridiculous. Isn't this a bit too demanding?
Not really, it's actually more simple to what Larry is currently offering. A simply SCCS to RCS converter would be enough. Merging information is easy to add as well. If you now also add a sequence number is quite simple to modify a CVS server which can export the data reliably.
Quoted 2 lines
Be realistic. The missing bits are worthless and add absolutely no value to kernel development which is supposed to be the topic for this mailing list.
If you want to test an alternative system to see whether it's usable for kernel development, what better data is there? How could you compare it against bk?
bye, Roman
[ hoping this is the last email in this thread, I know I'm not
contributing to this reach this objective :) ]
Quoted 4 lines · Roman Zippel
Hi,
On Sun, 16 Mar 2003, Nicolas Pitre wrote:
Quoted 8 lines
Quoted 4 lines
Quoted 2 lines
The missing bits are absolutely not worthless. They are very useful when you want to test other SCM system to simulate distributed development.
This is completely ridiculous. Isn't this a bit too demanding?
Not really, it's actually more simple to what Larry is currently offering. easy to add as well. If you now also add a sequence number is quite simple to modify a CVS server which can export the data reliably.
CVS basically exports RCS through the network, your argument makes no sense to me, what's the difference, I don't see what you mean.
Quoted 6 lines
Quoted 2 lines
Be realistic. The missing bits are worthless and add absolutely no value to kernel development which is supposed to be the topic for this mailing list.
If you want to test an alternative system to see whether it's usable for kernel development, what better data is there? How could you compare it against bk?
Larry has all the rights to not to help providing a testcase, it makes no sense for you to complain he's not providing a testcase for a competitive system. It make no sense just like complaining that if Larry changes the bk format to something encrypted compressed or .doc. he has the rights to do it, so please stop raising pointless arguments.
You could make a bit more of sense if your argument was that you still miss the visibility on the jfs developement or similar, but the fact a "testcase" for a competitive SCM this way is missing makes no sense at all. Infact a much testcase is not missing! just give us the alternative open SCM and we'll be glad to try using it in real life, which is an order of magnitude better testcase than feeding the old data into the repository offline.
If you're still unhappy now that the mainline data is open it means you're either a jfs developer (but I assume they're all fine with bk since they're just using it, so I doubt this is the case) or your problem is that you don't like the fact that Linux is still developed with proprietary software but in such case go speak with Linus not with Larry.
Quoted 1 line
From my part - now that the full data and metadata of the main branch is
available in the open in a usable form - I have no problem anymore with Linus using bitkeeper. I'm not religious about Linux, I'm only religious about my freedom. Sure, now I would like if Linus and Marcelo would be the only one using bitkeeper (so CVS would miss zero info), yes, but really all other branches are of nearly zero interest to me compared to the main branch and usually important branches like the jfs one (I don't know the others since I can't see them, I only know the jfs one because it gave me troubles with bkweb, this is why I'm only mentioning such one) can be retrieved via other methods (like asking the developers by emails).
Now I need to write tools to extract the stuff and parse it with more intelligent software than CVS, one of those tools is just available, so please stop these complains, and help writing a reliable changelog extractor using the dates and verifying the stuff with the logic tag. It doesn't matter if the CVS protocol is good or bad, as far as the whole mainline kernel evolution data is available reliably in the open, so from my part I'm extremely happy because I finally have a chance to start appreciating the advantages of Linus and Marcelo using bitkeeper ;)
Andrea
Hi,
Quoted 7 lines · Andrea Arcangeli
Quoted 4 lines
Not really, it's actually more simple to what Larry is currently offering. A simply SCCS to RCS converter would be enough. Merging information is easy to add as well. If you now also add a sequence number is quite simple to modify a CVS server which can export the data reliably.
CVS basically exports RCS through the network, your argument makes no sense to me, what's the difference, I don't see what you mean.
RCS is not that limited. It's very simple to take all deltas from a SCCS file and put it into a RCS file:
for delta in (all sorted deltas)
get -rdelta foo.c
ci -rdelta foo.c
Now one needs a little knowledge about the SCCS format. New deltas are added at the top and deltas have their own sequence numbers, it's no problem to add this sequence number to a RCS delta. This sequence number can be used by CVS to export the data reliable, the client would simply see 1.sequencenr as the version number.
If one looks now at the bk SCCS files, it's pretty easy to guess, which deltas are merges, so it should be really no problem to add this info to the RCS file as well.
Quoted 9 lines
Quoted 3 lines
If you want to test an alternative system to see whether it's usable for kernel development, what better data is there? How could you compare it against bk?
Larry has all the rights to not to help providing a testcase, it makes no sense for you to complain he's not providing a testcase for a competitive system. It make no sense just like complaining that if Larry changes the bk format to something encrypted compressed or .doc. he has the rights to do it, so please stop raising pointless arguments.
Well, this wasn't the deal. Larry doesn't own the data, he can't say that you only get all the data, if you use bk. One of the arguments for the move to bk was that the format was open and the data wasn't locked in. Technically it makes a lot of sense to move to a different format, but if he needs help to convert the data into proper RCS format, he only needs to ask, I'd be happy to help.
bye, Roman
Quoted 2 lines · Roman Zippel
Well, this wasn't the deal. Larry doesn't own the data, he can't say that you only get all the data, if you use bk.
Perhaps you can explain the benefits to BitMover of this "deal". If you are going to say that we get tons of marketing and sales from the free use of BK, forget about it. Sales in this product space are made at the CEO/CTO/VP level and I can assure you they don't read this mailing list, they don't read slashdot, and if they did they would view what we are doing as too risky. I tend to agree with them.
So what's the part of the "deal" that benefits BitMover?
As for the data, you are right, we don't own that. As for the metadata which makes BK work, that's ours, not yours. BK made that metadata, you did not. If you don't like those terms, convince Linus and friends to get off of BK. That would be just fine with us.
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Hi,
Quoted 4 lines · Larry McVoy
As for the data, you are right, we don't own that. As for the metadata which makes BK work, that's ours, not yours. BK made that metadata, you did not. If you don't like those terms, convince Linus and friends to get off of BK. That would be just fine with us.
This is getting ridiculous. Thank you, I have no doubts anymore that for you your ego is more important, than working with the community.
bye, Roman
Quoted 6 lines · Larry McVoy
use of BK, forget about it. Sales in this product space are made at the CEO/CTO/VP level and I can assure you they don't read this mailing list, they don't read slashdot, and if they did they would view what we are doing as too risky. I tend to agree with them.
So what's the part of the "deal" that benefits BitMover?
Sales in this product space are made by CEO/CTO/VP level after their engineers, which will have to use the product later did evaluation and investigation of a product. No (rotm) CEO/CTO/VP will ever _use_ this product. He will buy whatever got recommended by the engineers because they have to use it.
And they _do_ read the mailing lists / Slashdot.
You're throwing up smoke screens again. Larry, please try to be honest once. It is no bad thing that you lobby your (obviously fine) product by giving it away for free for kernel development. Why don't you simply admit it and be proud of it? Why do you try to be "more holy than holy?"
Your hidden agenda is showing once again quite clearly.
Regards
Henning
Signature · 5 lines
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH [email protected] +49 9131 50 654 0 http://www.intermeta.de/ Java, perl, Solaris, Linux, xSP Consulting, Web Services freelance consultant -- Jakarta Turbine Development -- hero for hire
Roman Zippel <[email protected]> said:
[...]
Quoted 3 lines
If you want to test an alternative system to see whether it's usable for kernel development, what better data is there? How could you compare it against bk?
Either it is a bk clone of some sort (which adds little value, and probably won't get the head hackers to switch) or it works on different principles. In the first case the info you request might be useful to peek at (but Larry (quite understandably IMVHO) will veto that), but you won't need it for day-to-day LKML bussiness; or it is utterly useless because it is from an incompatible worldview.
Signature · 4 lines
Dr. Horst H. von Brand User #22616 counter.li.org Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513
Quoted 4 lines · Larry McVoy
Quoted 2 lines · Roman Zippel
Well, this wasn't the deal. Larry doesn't own the data, he can't say that you only get all the data, if you use bk.
Quoted 8 lines
Perhaps you can explain the benefits to BitMover of this "deal". If you are going to say that we get tons of marketing and sales from the free use of BK, forget about it. Sales in this product space are made at the CEO/CTO/VP level and I can assure you they don't read this mailing list, they don't read slashdot, and if they did they would view what we are doing as too risky. I tend to agree with them.
So what's the part of the "deal" that benefits BitMover?
Let me reinsert the essential part of Roman's message that was censo^H^H^Homitted:
Quoted 2 lines · Roman Zippel
you only get all the data, if you use bk. One of the arguments for the move to bk was that the format was open and the data wasn't locked in.
Being seen to keep the promise would be the benefit to BitMover. Personally, I no longer hold any hope of that - the migration to increasingly proprietary formats and secret/patented protcols will be inexorable. Hence, no more flaming, just doing.
Regards,
Daniel
Quoted 7 lines · Daniel Phillips
Quoted 2 lines · Roman Zippel
you only get all the data, if you use bk. One of the arguments for the move to bk was that the format was open and the data wasn't locked in.
Being seen to keep the promise would be the benefit to BitMover. Personally, I no longer hold any hope of that - the migration to increasingly proprietary formats and secret/patented protcols will be inexorable.
$subject proves you wrong. cvs is an open format, and open protocol.
We hope to have cset retrieval via http available soon, too.
Quoted 2 lines
Hence, no more
flaming, just doing.
Larry seems to be the only one 'doing', ATM. :)
Jeff
Dear diary, on Mon, Mar 17, 2003 at 06:41:33PM CET, I got a letter, where Horst von Brand <[email protected]> told me, that...
Quoted 7 lines
Roman Zippel <[email protected]> said:
[...]
Quoted 3 lines
If you want to test an alternative system to see whether it's usable for kernel development, what better data is there? How could you compare it against bk?
It is perfectly reasonable for Larry not to support such a thing (unless he is so beated down by lkml people already that he seeks a way to escape, though still with grace yet ;).
Still the potential competing version control would have *MUCH* larger test base than without BitKeeper at all --- it is IMHO fine to politely ask for more, but if Larry doesn't want to do it, why to beat it from him so agressively? It's an added value which is here *thanks* to BitKeeper (and noone was able to pose any what BitKeeper *removed*, so the value has to be positive, mathematically speaking ;) so I think it is in competency of KitBeeper maintainers to regulate the size of such a value --- BitKeeper will probably be used as long as the value will stay high at least short-term (for runtime maintainement of various trees) and even if the value will approach zero by time (ie. only partial records in CVS, and it looks they are almost complete), as long as it's not negative I can't see why people whine about it so much.
Quoted 2 lines
Either it is a bk clone of some sort (which adds little value, and probably won't get the head hackers to switch)
..snip..
If it will approach the feature set AND usability of bk (or at least the subset which matters for kernel development), the information are somehow translatable from the bk's format AND it has acceptable licence, I can see big potential audience for it, at least to keep private trees (and merge together busily behind the Linus' back ;). Also the licence can be a big plus given the current state of things, even for Linus (he even stated so before some time, IIRC).
Kind regards,
Signature · 7 lines
Petr "Pasky busy playing with own supposedly-BK-alike SCM" Baudis . The pure and simple truth is rarely pure and never simple. -- Oscar Wilde . Stuff: http://pasky.ji.cz/
I still don't understand why bkbits.net does not simply make the SCCS files available.
That would render every objection moot.
-- Jamie
they do (and they ahve been available for quite a while), just not through bkbits.net due to bandwidth requirements. I think it was David M that has them available via rsync.
David Lang
Quoted 22 lines · Jamie Lokier
Date: Mon, 17 Mar 2003 19:32:09 +0000
From: Jamie Lokier <[email protected]>
To: Jeff Garzik <[email protected]>
Cc: Daniel Phillips <[email protected]>, Larry McVoy <[email protected]>,
Roman Zippel <[email protected]>, Andrea Arcangeli <[email protected]>, Nicolas Pitre <[email protected]>, Ben Collins <[email protected]>, lkml <[email protected]>
Subject: Re: [ANNOUNCE]BK->CVS(real time mirror)I still don't understand why bkbits.net does not simply make the SCCS files available.
That would render every objection moot.
-- Jamie
-
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/
Quoted 3 lines · David Lang
they do (and they ahve been available for quite a while), just not through bkbits.net due to bandwidth requirements. I think it was David M that has them available via rsync.
No, that's Rik van Riel you're thinking of.
ftp://nl.linux.org/pub/linux/bk2patch/
<whine>
But they aren't the originals (they contain lots of "merging into Rik's tree" entries) and they aren't real time!
</whine> :)
-- Jamie
Hi,
Quoted 4 lines · Jeff Garzik
Quoted 2 lines
Hence, no more
flaming, just doing.Larry seems to be the only one 'doing', ATM. :)
That's not really true, I posted an example RCS file. I explained how the data can be represented in a CVS tree.
The problem is Larry has the tools to easily extract all the data, I don't. I offered my help, all Larry has to do is to ask, but it seems he prefers to stay in control, which data you will get back.
BTW the data Larry is trying to hide is actually quite simple. The merge delta is simply the sum of all deltas from the branch (+ the conflict fixes you've done), which was merged.
bye, Roman
Quoted 4 lines · Jamie Lokier
I still don't understand why bkbits.net does not simply make the SCCS files available.
That would render every objection moot.
tell me how to get the data and metadata out of the SCCS files for changeset 1.786.202.5 like in the below:
http://linux.bkbits.net:8080/linux-2.5/user=akpm/[email protected]?nav=!-|index.html|stats|!+|index.html|ChangeSet@-6M|[email protected]
then tell me how to find the number "1.786.202.5" watching the SCCS history of kernel/timer.c.
SCCS provides per-file info, not the global metadata of the tree. That other information is stored in a proprietary format that the bitbucket project is trying to parse. CVS exports the whole info in a open format, this is why it's so much better than trying to parse the proprietary format that can be changed anyways to compressed and maybe encrypted format too.
Andrea
Hi!
Quoted 3 lines
If you're still unhappy now that the mainline data is open it means you're either a jfs developer (but I assume they're all fine with bk since they're just using it, so I doubt this is the case) or your
Actually, fact that "longest path" algorithm may well choose non-mainline branch because it likes it more worries me a bit.
Pavel
Signature · 2 lines
Horseback riding is like software... ...vgf orggre jura vgf serr.
Quoted 8 lines · Pavel Machek
Hi!
Quoted 3 lines
If you're still unhappy now that the mainline data is open it means you're either a jfs developer (but I assume they're all fine with bk since they're just using it, so I doubt this is the case) or your
Actually, fact that "longest path" algorithm may well choose non-mainline branch because it likes it more worries me a bit.
AFIK it's supposed to be the "longest path" of Linus's and Marcelo's branches which means it'll reproduce all the modifcations of the mainline trees only.
Andrea
Quoted 6 lines · Andrea Arcangeli
Quoted 2 lines
Actually, fact that "longest path" algorithm may well choose non-mainline branch because it likes it more worries me a bit.
AFIK it's supposed to be the "longest path" of Linus's and Marcelo's branches which means it'll reproduce all the modifcations of the mainline trees only.
By the way, we've been incrementally updating both trees and while in theory the incremental could result in shorter paths with less detail, so far the incremental export and the one pass export result in exactly the same path:
slovax $ bk _eventpath 1.0 + | wc -l
8498
slovax $ cd ../linux-2.5-cvs/linux-2.5
slovax $ rlog -r -N ChangeSet | grep revision
revision 1.8498I've actually reimported the data in one pass and diffed the RCS files, it's the same.
HPA, should we be mirroring the CVS tarballs to kernel.org?
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Quoted 19 lines · Larry McVoy
Quoted 6 lines · Andrea Arcangeli
Quoted 2 lines
Actually, fact that "longest path" algorithm may well choose non-mainline branch because it likes it more worries me a bit.
AFIK it's supposed to be the "longest path" of Linus's and Marcelo's branches which means it'll reproduce all the modifcations of the mainline trees only.
By the way, we've been incrementally updating both trees and while in theory the incremental could result in shorter paths with less detail, so far the incremental export and the one pass export result in exactly the same path:
slovax $ bk _eventpath 1.0 + | wc -l 8498 slovax $ cd ../linux-2.5-cvs/linux-2.5 slovax $ rlog -r -N ChangeSet | grep revision revision 1.8498
Quoted 4 lines
I've actually reimported the data in one pass and diffed the RCS files, it's the same.
HPA, should we be mirroring the CVS tarballs to kernel.org?
fine thanks!
BTW, CVS kernel + cvsps is just been extremely useful to me so far.
I also run into some huge patches like PatchSet 4711 in the 2.5 tree that I would love if it could be splitted properly but I understand it's impossible, right?
Thank you very much again for this great open service!
Andrea
Followup to: <[email protected]> By author: Larry McVoy <[email protected]> In newsgroup: linux.dev.kernel
Quoted 3 lines
HPA, should we be mirroring the CVS tarballs to kernel.org?
That would be highly useful. I would also like to see the bk export text file, whatever it's called, mirrored there.
-hpa
Signature · 3 lines
<[email protected]> at work, <[email protected]> in private! "Unix gives you enough rope to shoot yourself in the foot." Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
Quoted 9 lines · H. Peter Anvin
Followup to: <[email protected]> By author: Larry McVoy <[email protected]> In newsgroup: linux.dev.kernelQuoted 3 lines
HPA, should we be mirroring the CVS tarballs to kernel.org?
That would be highly useful. I would also like to see the bk export text file, whatever it's called, mirrored there.
There is no bk export text file, the output of the export is the CVS repository, there isn't anything else. Everything that we could extract has been extracted and put in CVS. It's a fairly complete and accurate extraction, too. Far more than the traditional releases and pre-releases, I don't know how many of those there have been in the 2.5 timeframe but I can't imagine more than a couple hundred; there are 8500 commits in the 2.5 CVS tree.
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Followup to: <[email protected]> By author: Larry McVoy <[email protected]> In newsgroup: linux.dev.kernel
Quoted 12 lines · H. Peter Anvin
Quoted 9 lines
Followup to: <[email protected]> By author: Larry McVoy <[email protected]> In newsgroup: linux.dev.kernelQuoted 3 lines
HPA, should we be mirroring the CVS tarballs to kernel.org?
That would be highly useful. I would also like to see the bk export text file, whatever it's called, mirrored there.
Quoted 8 lines
There is no bk export text file, the output of the export is the CVS repository, there isn't anything else. Everything that we could extract has been extracted and put in CVS. It's a fairly complete and accurate extraction, too. Far more than the traditional releases and pre-releases, I don't know how many of those there have been in the 2.5 timeframe but I can't imagine more than a couple hundred; there are 8500 commits in the 2.5 CVS tree.
I was referring to this stuff:
Date: Wed, 12 Mar 2003 10:03:04 -0800
X-Hdr-Sender: [email protected]
From: Larry McVoy <[email protected]>
Subject: Re: [ANNOUNCE] BK->CVS (real time mirror)
Message-ID: <[email protected]>
References: <[email protected]> <[email protected]>
Quoted 2 lines
I thought that BK has been able to export everything to a text file since the first version.
bk export -tpatch -r1.900 > patch.1.900
bk changes -v -r1.900 > comments.1.900
Been there forever. So has ways to get all the metadata from the command line without having to reverse engineer the file format. See
http://www.bitkeeper.com/manpages/bk-prs-1.html
it's all there. Always has been.
Wayne wanted me to point that it is easy to write the BK to CVS exporter completely from the command line, we prototyped it that way, the only reason we rewrote part of it in C was for performance. The point being that you guys could have done this yourself without help from us because all the metadata is right there. Ditto for anyone else worried about getting their data out of BK now or in the future. The whole point of prs is to be able to have a will-always-work way to get at the data or the metadata, it makes the file format a non-issue.
Signature · 3 lines
<[email protected]> at work, <[email protected]> in private! "Unix gives you enough rope to shoot yourself in the foot." Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64