log-buf-len dynamic
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 4 lines · Andrea Arcangeli
if Marcelo would be using open source code to exports the patchsets in his tree, we could fix it to add the email address along the name in the checkin logs metadata, to avoid this sort of mistakes.
Andrea - please just shut up.
Until you can point to anything even _remotely_ as good as BitKeeper, there's no point in just continually trying to start a flame-war.
I agree that Larry ends up being a jerk about it too, but I can well see that he reacts negatively to your totally unproductive comments.
BK has the email in the meta-data already, and a lot of tools to extract all the necessary data from mailboxes etc.
In other words, your argument is nonexistant, and your whole posting is pointless - except as flame-bait. And yes, Larry likely _will_ eat your bait, something I've berated him for in private emails several times.
So shut up or put up. Go off and write your own tool. In the meantime, stop complaining about people who wrote _their_ tools and selected a license that you wouldn't choose.
When you write some code of your own, you get to choose the license. And I haven't seen you make CVS usable - I've only seen you bitch, moan, and complain..
Linus
Quoted 3 lines · Linus Torvalds
When you write some code of your own, you get to choose the license. And I haven't seen you make CVS usable - I've only seen you bitch, moan, and complain..
we have cvsps and subversion these days, it's not about cvs only anymore.
if I would know that you will eventually get interested into anything not bitkeeper I would be glad to hack in this area (I can use some spare time too) to provide a service to the community. The main reason I will never use b*tkeeper is because I want to retain the freedom to do that, something that you and many others won't be able to do anymore.
But note that cvs+cvsps is already perfectly usable for me, most people is readonly anyways, and if you would checkin into cvs instead of b*tkeeper I couldn't notice any difference (except that I could send you a patch to add the email at the top of the cvs log). So from my part, using cvsps is just good enough and I've no idea why you call it "unusable" (just as example see the two patches I extracted in a second, in the old days I certainly couldn't do that).
There's a chance cvsps is even more friendly than b*tkeeper for my common usages.
Andrea - If you prefer relying on open source software, check these links:
rsync.kernel.org::pub/scm/linux/kernel/bkcvs/linux-2.[45]/ http://www.cobite.com/cvsps/ svn://svn.kernel.org/linux-2.[46]/trunk
Quoted 2 lines · Andrea Arcangeli
we have cvsps and subversion these days, it's not about cvs only anymore.
Neither of those are anywhere close to bk.
In particular, they don't support any kind of distributed development. They aren't even trying to, I'm sad to say. And to me, distributed development is the only thing that matters.
And I realise it isn't to you. You don't much care about merging, you only have your tree you need to worry about.
And you know what? You shouldn't have to care. I'm not berating you for using CVS/SVN/whatever. I'm berating you for complaining when _others_ have come to the conclusion that CVS/SVN/whatever really doesn't cut it for them.
Use CVS and be happy. But don't complain to others that have needs that CVS simply can't fill.
[ Bad analogy time ]
You're acting like a husband that has a wife that refuses to use make-up, and thinks that everybody else should have ugly wives too, and calls them whores for being prettier.
Actually, in the CVS analogy, I don't think it's that your wife refuses to use make-up, but that make-up doesn't actually help.
[ Ok, let's see just _how_ badly I get flamed for that analogy. I
admit, it really sucks, and is tasteless to boot. My bad. ]
Quoted 2 lines
But note that cvs+cvsps is already perfectly usable for me, most people is readonly anyways
Indeed. That's pretty much all non-distributed stuff is useful for, from where I'm stading. Small projects with a few developers and a lot of read-only stuff. And even there the developers will bitch about the limitations.
Sure, SVN makes branches cheaper, but you still have to work with them like under CVS, ie merging is a total disaster. And you still can't make it your private repository.
But that wasn't really my point. My point is that you're only starting flame wars, with no actual point to your emails. Please don't.
"Those that can, do. Those that can't, complain".
You're complaining, right now. Everybody who has ever used BK admits to its techical superiority. That's just a fact.
I don't care about source control software, so I'm not likely to start coding one any time soon (like "ever") - but if I did, I'd be totally _ashamed_ to push lower-quality stuff on users. I'd make excuses for it, and I'd 'fess up when they didn't work. And I'd try my best to make it better. Even if it took me a decade.
In contrast, what you're doing is saying "ignore the good stuff: use this crap, because I'm buddies with the people developing it. We aren't even trying to compete on technical terms, but we'll push our version on you because we've got religion, and this doesn't contain any cow-meat". That's bad - especially if others DON'T share the religion.
I'm ok with other people using NT. When it's better for them, that's their choice. I work hard to make sure that the Linux kernel is technically superior, and if I feel it isn't I want to fix it. Because I do _not_ want people using Linux for religious reasons. I want people to use Linux because it is _better_ for them, of because they truly believe that they can make it so (or at least have fun trying).
Take pride in what you do. But don't make that pride blind you to what is good technology, and what isn't. Don't get religion. It's a science.
Oh well. I told you not to start a flamewar, and I told Larry to not raise to the bait. Now I'll just take my own advice and stop responding. You too please stop baiting,
Linus
Quoted 11 lines · Linus Torvalds
[ Bad analogy time ]
You're acting like a husband that has a wife that refuses to use make-up, and thinks that everybody else should have ugly wives too, and calls them whores for being prettier.
Actually, in the CVS analogy, I don't think it's that your wife refuses to use make-up, but that make-up doesn't actually help.
[ Ok, let's see just _how_ badly I get flamed for that analogy. I
admit, it really sucks, and is tasteless to boot. My bad. ]
amusing ;)
well, following your bad analogy time, with software we can do the equivalent of changing the dna, that can fix the problem unlike than markup. So even starting from a very bad dna may not be a disaster as far as there's a critical mass behind it, able to eventually rewrite it from scratch. sure if we could choose the dna of a beautiful woman, it would be easier, but we don't have much choice (cvs/svn). either that or we start from scratch.
Quoted 1 line
because we've got religion, and this doesn't contain any cow-meat".
this is not religion this is primarly a law matter from my point of view.
AFIK it's illegal for me to use bitkeeper, because I'm not giving up the freedom to fix bugs in cvs or hack subversion, like the one that I'm going to fix to avoid losing the domain, period.
It's a pleasure for me to be able to very seldom fix an annoying bug once in a while in some random app, that nobody else cared about or noticed. It doesn't happen frequently, but it's one of the things I also like of using open source.
And secondly I prefer "open" to "immediatly better" or even to "immediatly so much better". Again, not because of religion (at least I don't feel it that way), but because of a better long term business investment. What you call religion I call long term investment. yeah, it maybe too long term, but I won't take the risk of trading it with the freedom of innovating in this area (even if I may never will).
You're right I should provide new code, and avoid comments on the a bit inferior info in bkcvs (that Larry nicely offered to even improve after cvs gets properly fixed), but I had no real interest in this area todate and my job keeps most of my time full already and that's higher priority. So I'm trying to at least raise the issue to see if somebody else shares my view, and maybe in more people it'll be easier to write code. I'm not complaining anything to Larry, quite the opposite, he was very annoyed by my signature, but I respect Larry and the signature has really nothing directly against him or bitkeeper. I'm advertizing the open links, that were not posted into any webpage or anywhere else, and I tought they deserved to be better known.
As for the merging with mainline, these patches were merged from 2.4.22 to 2.4.23pre5 (not all of them have been developed from me):
Only in 2.4.22aa1: 00_config-smp-1
Only in 2.4.22aa1: 00_copy-namespace-1
Only in 2.4.22aa1: 00_panic-console-switch-1 Only in 2.4.22aa1: 00_pgt-cache-leak-2
Only in 2.4.22aa1: 00_read_full_page-get_block-err-2 Only in 2.4.22aa1: 00_sk98lin_2.4.22-20030902-1.gz Only in 2.4.22aa1: 05_vm_03_vm_tunables-4 Only in 2.4.22aa1: 05_vm_05_zone_accounting-2 Only in 2.4.22aa1: 05_vm_06_swap_out-3
Only in 2.4.22aa1: 05_vm_07_local_pages-4 Only in 2.4.22aa1: 05_vm_09_misc_junk-3
Only in 2.4.22aa1: 05_vm_16_active_free_zone_bhs-1 Only in 2.4.22aa1: 05_vm_17_rest-10
Only in 2.4.22aa1: 70_xfs-sysctl-3
Only in 2.4.22aa1: 9999900_request-firmware-1
I know this time more patches have been merged than in the previous kernels (in this case some of the vm enhacements), but almost the same number gets regularly merged into mainline in the other releases too.
You're wrong saying that all I care is my tree, I'm deeply careful in keeping those patches in a way that can be merged with the minor possible pain from the kernel maintainer, infact I hope Marcelo also was confortable with that. My object is to get everything merged into mainline. Personally I wish my tree would be empty.
Andrea - If you prefer relying on open source software, check these links:
rsync.kernel.org::pub/scm/linux/kernel/bkcvs/linux-2.[45]/ http://www.cobite.com/cvsps/ svn://svn.kernel.org/linux-2.[46]/trunk
Quoted 5 lines · Andrea Arcangeli
You're right I should provide new code, and avoid comments on the a bit inferior info in bkcvs (that Larry nicely offered to even improve after cvs gets properly fixed), but I had no real interest in this area todate and my job keeps most of my time full already and that's higher priority.
The problem I have is as follows:
a) I understand your point of view and from the very first version of BK we released we addressed it. 100% of the data and the metadata is available from the command line with BK. Always has been and always will be, if that's not true that is is a bug and we'll fix it. People use BK because they like it, not because we locked them in.
b) I understand your need to not be dependent on BitMover or BitKeeper. That's why we built the CVS gateway, so you wouldn't need to depend on us, the data you care about is available in a form that doesn't require any license agreements.
What the above two points demonstrate, dramatically so, is that we understand your concerns and agree with them. We have spent a lot of time and money to make sure that you are happy. Not whining, not flaming, we were writing code to make you happy. We were writing that code long before you ever heard of BitKeeper and we have the revision history to prove it.
What we expected in return was the same understanding.
What we got was you complaining about us, in public, over and over.
Andrea, you need to grow up and learn that biting the hand that is held out to you and is helping you, that's not smart. What you have done is to make all the people who tried so hard to help you dislike you. That is your problem. You need to grow up. The world is based on relationships, people helping each other. That means you help those who help you, or at least don't piss all over those who help you.
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Quoted 20 lines · Larry McVoy
Quoted 5 lines · Andrea Arcangeli
You're right I should provide new code, and avoid comments on the a bit inferior info in bkcvs (that Larry nicely offered to even improve after cvs gets properly fixed), but I had no real interest in this area todate and my job keeps most of my time full already and that's higher priority.
The problem I have is as follows:
a) I understand your point of view and from the very first version of BK we released we addressed it. 100% of the data and the metadata is available from the command line with BK. Always has been and always will be, if that's not true that is is a bug and we'll fix it. People use BK because they like it, not because we locked them in.
b) I understand your need to not be dependent on BitMover or BitKeeper. That's why we built the CVS gateway, so you wouldn't need to depend on us, the data you care about is available in a form that doesn't require any license agreements.
Quoted 6 lines
What the above two points demonstrate, dramatically so, is that we understand your concerns and agree with them. We have spent a lot of time and money to make sure that you are happy. Not whining, not flaming, we were writing code to make you happy. We were writing that code long before you ever heard of BitKeeper and we have the revision history to prove it.
I defininitely agree with that and I appreciate that you acknowledge my requests when the bkcvs didn't exist.
(I was also using cvs for kernel development way before I ever heard of bitkeeper too, then I had to giveup because it was too slow to handle branches)
Quoted 1 line
What we expected in return was the same understanding.
that is not accurate, you also asked us to giveup the freedom of development in your area. And I wouldn't be too interested in a closed software anyways but at least I could consider using it in the meantime without feeling tainted.
NOTE: I'm not asking you to remove that clause, nor I'm complaining about it, I would feel bad for you if you had problems because you removed that clause. I perfectly understand why you put that clause in and it makes sense to me.
Quoted 1 line
Andrea, you need to grow up and learn that biting the hand that is held
It's because I grow up that I can actually better understand the deals it's in my own (again speaking only for myself and not for anybody else) interest to avoid.
(changing email address as well to make it clear I'm speaking only for myself here)
Last but not the least, if I was required to use bitkeeper as part of my job, then I would use it and I'd giveup that bit of freedom, but as far as I'm free to choose, I will avoid it. But that's my own choice, it has nothing to do with anybody else.
Andrea - If you prefer relying on open source software, check these links:
rsync.kernel.org::pub/scm/linux/kernel/bkcvs/linux-2.[45]/ http://www.cobite.com/cvsps/ svn://svn.kernel.org/linux-2.[46]/trunk
Quoted 4 lines · On Wed, Sep 24, 2003 at 04:04:09AM +0200, [email protected] wrote:
Quoted 1 line
What we expected in return was the same understanding.
that is not accurate, you also asked us to giveup the freedom of development in your area.
If you were actually doing some significant development then maybe I'd respect you. But you aren't. So I don't. You don't have the slightest understanding in this area, you've proved that beyond all reasonable doubt. So you are just complaining about something you don't understand.
I truly hope you follow in the footsteps of others who got pissed at the BK licensing and try to implement a replacement. BK makes VM systems seem like child's play. Centralized systems like CVS are child's play. Distributed systems like BK actually have to address all the problems that CVS ignores. Those problems are really hard. Not because they are so hard (even though they are), but because there are so many of them.
It may be an eye opener to you if you realized that most of the problems that the researchers are discussing about distributed file systems, those are problems that we have solved. Computer science research is behind us. No kidding. Go get your best and bring 'em on, we'll take the challenge. There are at least a dozen excellent PhD theses in BK. And those are the ones I can think of at the end of a very long tiring day.
If you understood that you'd understand why I am so unhappy with you. We've bent over backwards to give you what you need and you still don't understand what we have given you. You think it is something that you can fix in a few days of hacking.
I'm reminded of something Peter Gutmann said recently:
Whenever someone thinks that they can replace SSL/SSH with something much better that they designed this morning over coffee, their computer speakers should generate some sort of penis-shaped sound wave and plunge it repeatedly into their skulls until they achieve enlightenment.
Change "SSL/SSH" to "useful source mangement" and it makes the point. I hope your skull hurts. It should. Enlightenment is then forthcoming.
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Quoted 6 lines · Larry McVoy
Quoted 4 lines · On Wed, Sep 24, 2003 at 04:04:09AM +0200, [email protected] wrote:
Quoted 1 line
What we expected in return was the same understanding.
that is not accurate, you also asked us to giveup the freedom of development in your area.
Quoted 8 lines
If you were actually doing some significant development then maybe I'd respect you. But you aren't. So I don't. You don't have the slightest understanding in this area, you've proved that beyond all reasonable doubt. So you are just complaining about something you don't understand.
I truly hope you follow in the footsteps of others who got pissed at the BK licensing and try to implement a replacement. BK makes VM systems seem like child's play. Centralized systems like CVS are child's play.
If you weren't using the linux VM I'd respect you, but you are, and still I respected you so far, probably I was wrong.
Andrea - If you prefer relying on open source software, check these links:
rsync.kernel.org::pub/scm/linux/kernel/bkcvs/linux-2.[45]/ http://www.cobite.com/cvsps/ svn://svn.kernel.org/linux-2.[46]/trunk
Quoted 12 lines · Andrea Arcangeli
Quoted 11 lines · Larry McVoy
Quoted 4 lines · On Wed, Sep 24, 2003 at 04:04:09AM +0200, [email protected] wrote:
Quoted 1 line
What we expected in return was the same understanding.
that is not accurate, you also asked us to giveup the freedom of development in your area.
If you were actually doing some significant development then maybe I'd respect you. But you aren't. So I don't. You don't have the slightest understanding in this area, you've proved that beyond all reasonable doubt. So you are just complaining about something you don't understand.
Quoted 6 lines
Quoted 3 lines
I truly hope you follow in the footsteps of others who got pissed at the BK licensing and try to implement a replacement. BK makes VM systems seem like child's play. Centralized systems like CVS are child's play.
If you weren't using the linux VM I'd respect you, but you are, and still I respected you so far, probably I was wrong.
Yeah. I'm using the Linux VM. And it _still_ isn't up to what I managed to accomplish in SunOS. Wake up, dude. You aren't the first one to work in this area, you are just one of the first to work in this area without learning from the people who came before you. Don't believe me? Go to OLS and read the papers. Then read the OS research that has happened in the last 20 years or so. So far you are still catching up.
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Quoted 6 lines · Larry McVoy
Yeah. I'm using the Linux VM. And it _still_ isn't up to what I managed to accomplish in SunOS. Wake up, dude. You aren't the first one to work in this area, you are just one of the first to work in this area without learning from the people who came before you. Don't believe me? Go to OLS and read the papers. Then read the OS research that has happened in the last 20 years or so. So far you are still catching up.
Bad example ;)
While it is true that the Linux VM doesn't do a whole lot of the things a VM should do, there is also the fact that the VM problem space has gotten a lot harder over the last decade due to the fact that the size of disk and memory has grown way faster than the speed of disk and memory.
Simply put, nowadays it takes more than 10 times as long to swap out a process then it took 10 years ago. This puts interesting constraints on the design of a VM...
Signature · 3 lines
"Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan
Quoted 9 lines · Rik van Riel
Quoted 6 lines · Larry McVoy
Yeah. I'm using the Linux VM. And it _still_ isn't up to what I managed to accomplish in SunOS. Wake up, dude. You aren't the first one to work in this area, you are just one of the first to work in this area without learning from the people who came before you. Don't believe me? Go to OLS and read the papers. Then read the OS research that has happened in the last 20 years or so. So far you are still catching up.
Quoted 8 lines
Bad example ;)
While it is true that the Linux VM doesn't do a whole lot of the things a VM should do, there is also the fact that the VM problem space has gotten a lot harder over the last decade due to the fact that the size of disk and memory has grown way faster than the speed of disk and memory.
Oh, I agree. The problem space changes and you have to move with it. I was just pointing out that by not learning from others you put yourself at a disadvantage. There are a lot of bright minds in the Linux space, there is no question of that. But they would do so much better if they understood the past. The past holds a lot of information, ignoring it is a disadvantage.
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Larry, I think you remember the good old days of SunOS, when 16MB of RAM was a lot, and people expected less of their hardware. In particular, interactive programs used to have a _tiny_ footprint. Often even under X.
Then we put Solaris, Motif and CDE on those suckers, and it was horrible.
Yeah, SunOS was nice. But I really think it's the access patterns that changed.
Linus
Quoted 2 lines · Linus Torvalds
Yeah, SunOS was nice. But I really think it's the access patterns that changed.
Absolutely. Garbage collection and object orientation have obsoleted LRU and related algorithms.
Huge memory sizes also have done their share to obsolete recency based replacement algorithms.
I suspect we'll want something closer to a frequency based replacement scheme in the future. Possibly something like LIRS or ARC, but adapted to work in a general purpose OS in a very light weight way.
The argument that because we have more memory replacement is no longer as important doesn't quite hold because the cost of page replacement, measured in cpu cycles, has gone completely through the roof in the last decades.
Then there's the whole different bag of cookies that is the caching of filesystem metadata, like our inode and dentry caches. I'm not sure what would be a good replacement strategy for those, but I do know that we'll want a good algorithm here because hard disks (and the number of files on them) are growing so much faster than anything else in our computers...
Signature · 3 lines
"Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan
If people would just wake up to the lossy memory compression algorithms that Steve Tweedie invented, the whole problem could be solved in a moment.
Quoted 39 lines · Rik van Riel
Quoted 2 lines · Linus Torvalds
Yeah, SunOS was nice. But I really think it's the access patterns that changed.
Absolutely. Garbage collection and object orientation have obsoleted LRU and related algorithms.
Huge memory sizes also have done their share to obsolete recency based replacement algorithms.
I suspect we'll want something closer to a frequency based replacement scheme in the future. Possibly something like LIRS or ARC, but adapted to work in a general purpose OS in a very light weight way.
The argument that because we have more memory replacement is no longer as important doesn't quite hold because the cost of page replacement, measured in cpu cycles, has gone completely through the roof in the last decades.
Then there's the whole different bag of cookies that is the caching of filesystem metadata, like our inode and dentry caches. I'm not sure what would be a good replacement strategy for those, but I do know that we'll want a good algorithm here because hard disks (and the number of files on them) are growing so much faster than anything else in our computers...
Signature · 9 lines
"Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan - 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/
Signature · 5 lines
--------------------------------------------------------- Victor Yodaiken Finite State Machine Labs: The RTLinux Company. www.fsmlabs.com www.rtlinux.com 1+ 505 838 9109
Quoted 6 lines · Larry McVoy
Oh, I agree. The problem space changes and you have to move with it. I was just pointing out that by not learning from others you put yourself at a disadvantage. There are a lot of bright minds in the Linux space, there is no question of that. But they would do so much better if they understood the past. The past holds a lot of information, ignoring it is a disadvantage.
It isnt just sizes. As the size has risen rapidly the disk data rates have increased pretty well (factor of about 100 over an MFM disk 386) but the seek time has shifted by a factor of 10. This has a huge impact on the whole basic theory of things like paging in applications versus doing a streaming preload of the code/data.
It also has a big impact on how swap is managed - it is pretty much as cheap now to swap out 2Mb as 4K
Quoted 9 lines · Alan Cox
It isnt just sizes. As the size has risen rapidly the disk data rates have increased pretty well (factor of about 100 over an MFM disk 386) but the seek time has shifted by a factor of 10. This has a huge impact on the whole basic theory of things like paging in applications versus doing a streaming preload of the code/data.
It also has a big impact on how swap is managed - it is pretty much as cheap now to swap out 2Mb as 4K
How do you get to 2MB? My rule of thumb number is still 100kB.
Jörn
Signature · 2 lines
Invincibility is in oneself, vulnerability is in the opponent. -- Sun Tzu
Quoted 2 lines · Larry McVoy
Yeah. I'm using the Linux VM. And it _still_ isn't up to what I managed to accomplish in SunOS. Wake up, dude. You aren't the first one to
if this would be really true, then why do you use linux then? I don't understand. I've to exclude the reason is that it's free and open.
I heard arguments like yours for years and years from tons of different people, 7 years ago I heard the very same again and again about linux at large compared to other operative systems (way before I was using linux myself).
Personally I don't believe you. I'm not saying the vm is too complex, but it's heavily dominatd by details, it's simply not possible to unique describe the vm in terms of algorithms like most parers do, and I believe what we have in linux (mainline 2.4.23pre5 and 2.6 [modulo rmap]) is very optimal.
Andrea - If you prefer relying on open source software, check these links:
rsync.kernel.org::pub/scm/linux/kernel/bkcvs/linux-2.[45]/ http://www.cobite.com/cvsps/ svn://svn.kernel.org/linux-2.[46]/trunk
Quoted 6 lines · Andrea Arcangeli
Quoted 2 lines · Larry McVoy
Yeah. I'm using the Linux VM. And it _still_ isn't up to what I managed to accomplish in SunOS. Wake up, dude. You aren't the first one to
if this would be really true, then why do you use linux then? I don't understand. I've to exclude the reason is that it's free and open.
Because I have huge respect for Linus' leadership. I've met a lot of talented people in my life, people who were good engineers, good architects, and good managers. Linus is _all_ of those and that, in my opinion, is unique. BitKeeper exists because I believe that Linus is unique and BK is my way of helping him be productive and continue to be the leader of the Linux effort.
I don't know if you get it, you could go a lifetime and not meet someone like Linus. Don't get me wrong, we've had screaming matches, I remember one where I was yelling "I just want you to work for me so I can fire your sorry ass", it's not like I worship the ground he walks on or anything. But I do respect, deeply respect, what he has done. I've demonstrated here that I don't have what it takes to do his job. You have too. So have others. If we really care about the good of the world then we help in the way that helps the most. That's what I'm doing.
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Quoted 8 lines · Andrea Arcangeli
Quoted 2 lines · Larry McVoy
Yeah. I'm using the Linux VM. And it _still_ isn't up to what I managed to accomplish in SunOS. Wake up, dude. You aren't the first one to
I heard arguments like yours for years and years from tons of different people, 7 years ago I heard the very same again and again about linux at large compared to other operative systems (way before I was using linux myself).
And you know what? Larry is right that the Linux VM still lacks a number of things, like being robust under heavy overload situations, etc...
Yes, the Linux VM is fast, but that isn't much good if you can drive it into a death spiral with a single load spike.
Quoted 5 lines
Personally I don't believe you. I'm not saying the vm is too complex, but it's heavily dominatd by details, it's simply not possible to unique describe the vm in terms of algorithms like most parers do, and I believe what we have in linux (mainline 2.4.23pre5 and 2.6 [modulo rmap]) is very optimal.
You'll want to catch up to the 1990's some day. Maybe even to the current decade. For example, it's pretty much proven that lru-like algorithms (like in 2.4-rmap) are suboptimal, while the use-once stuff in 2.4 mainline and 2.6 is only metastable, meaning that it doesn't recover from load spikes except through some combination of clever tricks and sheer luck, that works only under some loads.
Likewise, the way we write out dirty pages on page replacement just can't scale to huge amounts of memory, because it'd take minutes to write out all of the pages on the inactive list. The non-blocking VM stuff akpm implemented for 2.6 should alleviate that on medium sized systems, but on truly huge systems we'll need a page laundering strategy that also improves CPU efficiency when faced with dozens of gigabytes of inactive pages.
I'll happily concede that you are the absolute champion when it comes to tuning the VM to get the best possible benchmark numbers, but that is just not the same as trying to deal with all the corner cases people run into in real life.
Larry really does have a point.
Signature · 3 lines
"Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan
Quoted 4 lines · On Wed, 24 Sep 2003 [email protected] wrote:
It's because I grow up that I can actually better understand the deals it's in my own (again speaking only for myself and not for anybody else) interest to avoid.
You've claimed this now twice.
However, that only explains why you don't use BitKeeper. And everybody accepts that. When I started to use BK, I made it _very_ clear that service for non-BK users will be _at_least_ as good as it ever was before I started using BK.
And I think everybody agrees that is true. ChangeLogs, CVS exports, daily snapshots. And that's just the advantages to _others_.
But your lack of interest in BK does _not_ explain why you whine about it, and try to goad Larry, and just generally are nasty about it.
You remind me of how some of the BSD people complaining about me using the GPL. They whined and whined about how the GPL is not as free as the BSD license.
In other words:
- you don't have to agree with another persons choice of license, and you don't have to to use the software using it. That is _your_ choice.
- But you also don't have the moral right to whine about another persons choice of license (or choice of using software under that license). That was _their_ choice.
See? You're not just being impolite; your complaints are actually morally offensive. The same way I found it morally offensive when people complained about my choice of GPL. They didn't have the right. And _you_ don't have the right.
It's the old
"I disapprove of what you say, but I will defend to the death your
right to say it"
approach: even if you disapprove of Larry's license, you should defend his _right_ to that license. Instead of whining about it.
Linus
Quoted 14 lines · Linus Torvalds
Quoted 4 lines · On Wed, 24 Sep 2003 [email protected] wrote:
It's because I grow up that I can actually better understand the deals it's in my own (again speaking only for myself and not for anybody else) interest to avoid.
You've claimed this now twice.
However, that only explains why you don't use BitKeeper. And everybody accepts that. When I started to use BK, I made it _very_ clear that service for non-BK users will be _at_least_ as good as it ever was before I started using BK.
Quoted 5 lines
And I think everybody agrees that is true. ChangeLogs, CVS exports, daily snapshots. And that's just the advantages to _others_.
But your lack of interest in BK does _not_ explain why you whine about it, and try to goad Larry, and just generally are nasty about it.
I wasn't whining about BK at all, nor about the licence, I just advertized the open links in my signature, the word "refuse" may be not a nice one, I didn't feel to be rude when I wrote it, now I changed it and I hope it's a more friendly wording, though the meaning it's the same.
Quoted 2 lines
approach: even if you disapprove of Larry's license, you should defend his _right_ to that license. Instead of whining about it.
I defend his right to the licence, it makes perfect business sense, if he wanted to be safer he had to take a couple of patents too I guess (but I'm not a lawyer and I certainly prefer the licence to the patents). I don't think I ever complained to the licence. I only said I'm not applying to the licence and _you_ have to respect my _right_ not to use the software and to advertize the _open_ links, without seeing it as an offensive thing.
Andrea - If you prefer relying on open source software, check these links:
rsync.kernel.org::pub/scm/linux/kernel/bkcvs/linux-2.[45]/ http://www.cobite.com/cvsps/ svn://svn.kernel.org/linux-2.[46]/trunk
Quoted 6 lines · Andrea Arcangeli
I wasn't whining about BK at all, nor about the licence, I just advertized the open links in my signature, the word "refuse" may be not a nice one, I didn't feel to be rude when I wrote it, now I changed it and I hope it's a more friendly wording, though the meaning it's the same.
Andrea, be honest.
This latest thing didn't start with just the signature. In fact, the signature flame-war I berated Larry for - ask Larry. I told him he shouldn't let himself be goaded.
This one started with you very much making the whole point of your whole post be a complaint about the license:
"if Marcelo would be using open source code to exports the patchsets in
his tree, we could fix it to add the email address along the name in the checkin logs metadata, to avoid this sort of mistakes."
That quote is not just some small snippet: it is the _entirety_ of new material in the whole post.
You are whining. You did nothing _but_ whine in the post. About other peoples choice of license usage.
Quoted 3 lines
I only said I'm not applying to the licence and _you_ have to respect
my _right_ not to use the software and to advertize the _open_ links, without seeing it as an offensive thing.
(a) It wasn't all you said
(b) I can, and do, get offended by postings to public non-religious lists that have no redeeming value except to push your religious views.
I despise people who come up to me in the street (or even worse - ring the doorbell on my house) to tell me about Jesus, and how they found happiness in him.
Good for you and your buddy Jesus/buddha/Moses/AlienFromAnotherPlanet. But get the _hell_ out of my face. If I come to your church to listen to your sermons, that's when I'll respect your right to tell me. But if you stand up with a megaphone in the park when I'm having a picknick, I'd much rather kick your sorry ass the h*ll out of there.
So go to gnu.misc.discuss if you want to discuss the immorality of licenses. There you'll find people who care. linux-kernel is about technical discussions about the kernel, and yes IT IS OFFENSIVE to push religion here.
It's also offensive to have comments about abortion or guns in your signature. For exactly the same reason (and btw, I complained to esr when he had his gun-control signature, so I'm not just making these up).
Do you see?
Now can we get back to complaining about the scheduler behaviour and xmms?
Please?
Linus
Quoted 9 lines · Linus Torvalds
Quoted 6 lines · Andrea Arcangeli
I wasn't whining about BK at all, nor about the licence, I just advertized the open links in my signature, the word "refuse" may be not a nice one, I didn't feel to be rude when I wrote it, now I changed it and I hope it's a more friendly wording, though the meaning it's the same.
Quoted 3 lines
Andrea, be honest.
This latest thing didn't start with just the signature. In fact, the
the latest not, but that was the latest, and I still recommend Marcelo to stop using bitkeeper and to do the checkins directly in cvs. That would be a start and it would motivate me more too into adding more effort there.
I need a bit of feedback from a kernel maintainer that there will be a slight chance to use something non bitkeeper in the future before I invest a bit of (probably my spare) time into this.
Quoted 6 lines
"if Marcelo would be using open source code to exports the patchsets in
his tree, we could fix it to add the email address along the name in the checkin logs metadata, to avoid this sort of mistakes."That quote is not just some small snippet: it is the _entirety_ of new material in the whole post.
yes that was the whole point of the email. That was a suggestion for Marcelo.
Quoted 12 lines
Quoted 3 lines
I only said I'm not applying to the licence and _you_ have to respect
my _right_ not to use the software and to advertize the _open_ links, without seeing it as an offensive thing.(a) It wasn't all you said
(b) I can, and do, get offended by postings to public non-religious lists that have no redeeming value except to push your religious views.I despise people who come up to me in the street (or even worse - ring the doorbell on my house) to tell me about Jesus, and how they found happiness in him.
Quoted 7 lines
Good for you and your buddy Jesus/buddha/Moses/AlienFromAnotherPlanet. But get the _hell_ out of my face. If I come to your church to listen to your sermons, that's when I'll respect your right to tell me. But if you stand up with a megaphone in the park when I'm having a picknick, I'd much rather kick your sorry ass the h*ll out of there.
So go to gnu.misc.discuss if you want to discuss the immorality of
Really I don't find anything immoral, nor religious here. I only care about law. Law says if I use bitkeeper I can't develop in the same area, and so I refuse to use it. it's as simple as that.
To me it looks like you're confusing law and free market, with religion.
To make an example, I used netscape for years, netscape was the only reasonable software at the time, and I would have never expected that they would release the sources anytime soon, nor I was extremely interested into it, since netscape just worked fine (on alpha I used the tru64 version for a long time too). I preferred an open alternative but there wasn't so I happily used netscape. I still used netscape for a long time even when mozilla was usable because some website didn't work with mozilla and I had no time to fix it myself. The netscape licence was acceptable to me to use for something not critical for me like browsing the web (I mean who cares if netscape crashes). I can make lots more examples like that. I don't feel religious about stuff, and you certainly can't claim I'm religious because I refuse to giveup my rights to fix or improve cvs or subversion or to write a filesystem with versioning, that may effectively collide with future jobs as well. that's about freedom, not religion.
Andrea - If you prefer relying on open source software, check these links:
rsync.kernel.org::pub/scm/linux/kernel/bkcvs/linux-2.[45]/ http://www.cobite.com/cvsps/ svn://svn.kernel.org/linux-2.[46]/trunk
Quoted 4 lines · Andrea Arcangeli
Really I don't find anything immoral, nor religious here. I only care about law. Law says if I use bitkeeper I can't develop in the same area, and so I refuse to use it. it's as simple as that.
Go away. I will tell you one more time: it is _fine_ that you don't use BK. Nobody has ever asked you to, in fact.
So don't use it. Please. You don't like the license, and what it means. Agreed. That license is a legal document. Agreed. BUT THAT ISN'T THE ISSUE.
And that was NEVER the issue, even though you keep bringing it up. Again and again.
The issue is that you should not complain about other peoples choices. They are not _your_ choices. Never were, and never will be.
Linus
Quoted 1 line · Linus Torvalds
And that was NEVER the issue, even though you keep bringing it up. Again
that is _the_ issue from my part, the thing that isn't remotely going to make me think to use bitkeeper. If there wasn't that clause in the licence I would probably find acceptable to use it in the meantime.
But I guess I'd better go away as you ask since I feel like nobody understands why I'm not using it despite I'm trying to explain it a few times already.
Quoted 1 line
The issue is that you should not complain about other peoples choices.
I'm not complaining about that, I was making a suggestion to Marcelo outlighting what was possible to achieve if it was open (yeah, it's a minor thing). Larry even said what I suggested was not an optimal fix and I agree with that so I will try to fix it right. I think it was a productive suggestion after all.
Andrea - If you prefer relying on open source software, check these links:
rsync.kernel.org::pub/scm/linux/kernel/bkcvs/linux-2.[45]/ http://www.cobite.com/cvsps/ svn://svn.kernel.org/linux-2.[46]/trunk
Quoted 3 lines · Andrea Arcangeli
But I guess I'd better go away as you ask since I feel like nobody understands why I'm not using it despite I'm trying to explain it a few times already.
Three letters: TMI. Look, if you really wanted you could post
the description of your favorite positions and comparative study of their effects on your productivity. Once. It would certainly raise a lot of eyebrows, but that would be it. But if you kept explaining your preferences again and again and again, people would get annoyed. And if you would get into a habit of making recommendations to other folks, people would get *really* annoyed. Fast. And that's pretty much what's happening.
Quoted 3 lines · Andrea Arcangeli
the latest not, but that was the latest, and I still recommend Marcelo to stop using bitkeeper and to do the checkins directly in cvs. That would be a start
That would break so many 3rd party trees. It would mean Marcelo would no longer be able to just pull in eg. the PPC tree, it would mean merging pain for branched trees, etc...
Quoted 1 line
and it would motivate me more too into adding more effort there.
Effort where ?
If you're talking about adding more effort into merging things into 2.4, then DUH. You would NEED more effort to get stuff merged, if marcelo used something as bad as CVS.
If you're talking about improving CVS, don't bother. The model is broken.
Quoted 3 lines
I need a bit of feedback from a kernel maintainer that there will be a slight chance to use something non bitkeeper in the future before I invest a bit of (probably my spare) time into this.
There's more than a slight chance. Just come up with something that's as good as, or better than, bitkeeeper and people will switch in a heartbeat.
Signature · 3 lines
"Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan
Quoted 1 line · On Wed, 24 Sep 2003 04:48:31 +0200 Andrea Arcangeli <[email protected]> wrote:
I wasn't whining about BK at all, nor about the licence,
Let me remind you, what you said which prompted Linus to reply in the first place:
"if Marcelo would be using open source code to exports the
patchsets in"
This is flame bait. The only thing a sentence like that will do is spark a flame and incite emotional responses from others, not constructive conversation.
That is what you need to stop doing.
Hi,
Quoted 2 lines · Linus Torvalds
See? You're not just being impolite; your complaints are actually morally offensive.
You think this is impolite? I've been quiet lately in these flame wars, because I couldn't have staid that polite to an arrogant asshole, but I won't stay quiet when Larry can now insult other developers and gets away with it. If someone is whining around here, then it's only Larry. A lot of people are contributing to the kernel, but he is the only one constantly whining around that he should be treated special and makes silly threats. Can we please get cause and effect right here? Of course Larry is completely free to choose whatever license he wants, but advertising a stupid license in a free software environment will of course cause disagreement and complaints. There is _nothing_ anyone but Larry can do anything about it, but amazingly enough Larry manages to take every single complaint as personal insult and makes all of the bk flame wars worse than they already are.
Andreas sig is about as offensive as a "Don't drink and drive" spot. The bk license is problematic for a number of developers and it's very important that new developers are made aware of the problems and not just think it's cool to use bk because the mighty Linus is using it.
bye, Roman
Quoted 4 lines · Roman Zippel
amazingly enough Larry manages to take every single complaint as personal insult and makes all of the bk flame wars worse than they already are. ... Andreas sig is about as offensive as a "Don't drink and drive" spot.
Yeah, what he said.
My ruleset looks kinda like this:
Larry contributing BK
==> good, flames inappropriate
Larry being an overbearing, thin-skinned, asshole
==> bad, flames appropriate
Developers using BK
==> their choice, tread lightly
Developers promoting non-BK systems in their sig
==> their choice, tread lightly
Andrea's sig in particular
==> pretty damn innocuous; why on earth is Larry whining about it?
-Miles
Signature · 1 line
Would you like fries with that?
Quoted 8 lines · Miles Bader
Quoted 5 lines · Roman Zippel
amazingly enough Larry manages to take every single complaint as personal insult and makes all of the bk flame wars worse than they already are. ... Andreas sig is about as offensive as a "Don't drink and drive" spot.
Quoted 4 lines
Yeah, what he said.
My ruleset looks kinda like this:
Can we please drop it? Nobody is perfect, just live and let live. I don't mean to sound rude so please don't take it that way. And this is not directed at you in particular Miles.
Thanks,
Nick
Quoted 6 lines · Linus Torvalds
Quoted 4 lines · On Wed, 24 Sep 2003 [email protected] wrote:
It's because I grow up that I can actually better understand the deals it's in my own (again speaking only for myself and not for anybody else) interest to avoid.
Quoted 6 lines
You've claimed this now twice.
However, that only explains why you don't use BitKeeper. And everybody accepts that. When I started to use BK, I made it _very_ clear that service for non-BK users will be _at_least_ as good as it ever was before I started using BK.
And for the core kernel development this is true. There are subprojects that are currently using BK that you can't even get the code without BK. And the only reason they are using BK is they are attempting to following how Linux is managed. So having the Linux kernel development use BK does have some down sides.
In addition there are some major gains to be had in standardizing on a distributed version control system that everyone can use, and unfortunately BK does not fill that position. So I think it is good that there is enough general discontent it the air that people continue to look for alternatives.
The current situation with version control is painful. CVS branches poorly and is not distributed. SVN is not distributed. ARCH is barely distributed and architecturally it makes distributed merging hard. BK requires open logging which makes it unsuitable for working on prerelease hardware. BK does not scale to the low end because to use it successfully you need to make non-BK releases which is an extra burden. Unless I missed something big all of the BK->foo gateways are specific to a few source trees. And of course BK won't let you hack on a replacement.
I don't think the flame wars should stop. The current situation is not half as good as it could be. And discussion is needed to get us there. Even pure flames which accomplish nothing technical accomplish something socially by reminding people that there is the potential to do much better, and that the current situation is painful.
It is clearly not a solution to simply drop BK, that is even more painful. To reduce the pain will take a combination of frustration, time, talent, and a bit of luck that has not happened yet.
Eric
Quoted 5 lines · Eric W. Biederman
And for the core kernel development this is true. There are subprojects that are currently using BK that you can't even get the code without BK. And the only reason they are using BK is they are attempting to following how Linux is managed. So having the Linux kernel development use BK does have some down sides.
Stupid argument. E.g. the ppc folks used BK much longer than Linus. And there are kernel projects using svn (ieee1394) or cvs that you can't access without installing svn or cvs.
Quoted 5 lines
In addition there are some major gains to be had in standardizing on a distributed version control system that everyone can use, and unfortunately BK does not fill that position. So I think it is good that there is enough general discontent it the air that people continue to look for alternatives.
Why should we standardize on one SCM? That's like we standadize on Windows for all computers..
Quoted 3 lines · Christoph Hellwig
Stupid argument. E.g. the ppc folks used BK much longer than Linus. And there are kernel projects using svn (ieee1394) or cvs that you can't access without installing svn or cvs.
I use the 'cvsweb' interface to track the ieee1394 codebase. I can download specific patches, and anytime I feel like it, it will automagically generate a current tarball for me. Therefore, I can easily track it without needing to use svn (which I do not have installed).
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
Quoted 11 lines · Eric W. Biederman
Quoted 5 lines
However, that only explains why you don't use BitKeeper. And everybody accepts that. When I started to use BK, I made it _very_ clear that service for non-BK users will be _at_least_ as good as it ever was before I started using BK.
And for the core kernel development this is true. There are subprojects that are currently using BK that you can't even get the code without BK. And the only reason they are using BK is they are attempting to following how Linux is managed. So having the Linux kernel development use BK does have some down sides.
That's actually a pretty good point. I end up releasing "sparse" only as a BK archive, simply because I'm too lazy to care and there aren't enough people involved (and those that _are_ involved do actually end up re-exporting it as non-BK, but that doesn't invalidate your point).
I don't know what the solution to it might be - but I don't think the reason they are using BK is that they are trying to emulate "the great kernel project". I know it wasn't for me - it's just that once you get used to BK, there's no way you'll ever go back to CVS willingly.
Quoted 3 lines
In addition there are some major gains to be had in standardizing on a distributed version control system that everyone can use, and unfortunately BK does not fill that position.
I don't disagree, but I don't see a real way to solve it. As Larry will tell you, the technical problems are bigger than you imagine. So a BK killer won't be coming any time soon, methinks.
Linus
Quoted 4 lines · Linus Torvalds
I don't know what the solution to it might be - but I don't think the reason they are using BK is that they are trying to emulate "the great kernel project". I know it wasn't for me - it's just that once you get used to BK, there's no way you'll ever go back to CVS willingly.
Nod. All my new projects start out in BitKeeper these days, because it's so much better than cvs.
Jeff
Quoted 6 lines · Linus Torvalds
Quoted 2 lines · Eric W. Biederman
And for the core kernel development this is true. There are subprojects that are currently using BK that you can't even get the code without BK.
That's actually a pretty good point.
[...]
Quoted 1 line
I don't know what the solution to it might be
Perhaps BitMover could release a client that can't do anything but keep a local (unmodified) tree in sync with a public repository tree, so that the "politically objectionable" (to some) parts of the BK license don't matter.
In an idea world, this read-only client could be released in source form, but I'm under no illusions there :).
Charles
Signature · 4 lines
----------------------------------------------------------------------- Charles Cazabon <[email protected]> GPL'ed software available at: http://www.qcc.ca/~charlesc/software/ -----------------------------------------------------------------------
Quoted 6 lines · Charles Cazabon
Perhaps BitMover could release a client that can't do anything but keep a local (unmodified) tree in sync with a public repository tree, so that the "politically objectionable" (to some) parts of the BK license don't matter.
In an idea world, this read-only client could be released in source form, but I'm under no illusions there :).
People ask us for this all the time and it just highlights the point that people don't understand how BK works. It isn't client server, it's peer to peer, every so-called client has to have all the smarts built in that the so-called server has.
There isn't any way to release a stripped down version that makes sense. If there was, we would.
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Larry, have you or could you publish the BK->?? export code?, This way even if you do not host the exported stuff it would be trivial for a person who is willing to use bk to setup a server to mirror any 'bk-only' project.
David Lang
Quoted 30 lines · Larry McVoy
Date: Thu, 25 Sep 2003 11:29:22 -0700
From: Larry McVoy <[email protected]>
To: Kernel Mailing List <[email protected]>,
Larry McVoy <[email protected]>
Subject: Re: log-buf-len dynamicQuoted 6 lines · Charles Cazabon
Perhaps BitMover could release a client that can't do anything but keep a local (unmodified) tree in sync with a public repository tree, so that the "politically objectionable" (to some) parts of the BK license don't matter.
In an idea world, this read-only client could be released in source form, but I'm under no illusions there :).
People ask us for this all the time and it just highlights the point that people don't understand how BK works. It isn't client server, it's peer to peer, every so-called client has to have all the smarts built in that the so-called server has.
There isn't any way to release a stripped down version that makes sense. If there was, we would.
--
---
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/
Signature · 3 lines
"Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan
I can't, it's mostly C code in BK itself and it is in a higher performance commercial version of BK that we haven't released yet.
Quoted 4 lines · David Lang
Larry, have you or could you publish the BK->?? export code?, This way even if you do not host the exported stuff it would be trivial for a person who is willing to use bk to setup a server to mirror any 'bk-only' project.
Quoted 9 lines · Larry McVoy
Quoted 7 lines · Charles Cazabon
Perhaps BitMover could release a client that can't do anything but keep a local (unmodified) tree in sync with a public repository tree, so that the "politically objectionable" (to some) parts of the BK license don't matter.
In an idea world, this read-only client could be released in source form, but I'm under no illusions there :).
Quoted 7 lines
People ask us for this all the time and it just highlights the point that people don't understand how BK works. It isn't client server, it's peer to peer, every so-called client has to have all the smarts built in that the so-called server has.
There isn't any way to release a stripped down version that makes sense. If there was, we would.
I'm under the impression that the real smarts of bitkeeper is keeping a huge database of independent changes and only making a tree out of them when you ask to see the thing. I.E. bitkeeper is a huge pile of merge logic that can take into account not just what the tree looks like now, but everything the tree has _ever_ looked like.
So a read-only client still needs all this merge logic. Export is the easy part. VIEW is the hard part. The protocols to marshall the patches from point A to point B are almost irrelevant, it's sorting and integrating them into something useful that requires work.
And the reason Andrea hasn't found bitkeeper to be nicer than CVS is he isn't trying to integrate the work of 300 other developers into his personal tree simultaneously. BK is really just a merging tool that fixes rejects automatically, everything else is details...
Am I wrong?
Rob
Quoted 2 lines
BK is really just a merging tool that fixes rejects automatically, everything else is details...
IFF that is true, then taking this to it's logical extreme, what is the point in having an SCM system for kernel development at all?
It could be argued that what we really need is enhanced versions of diff and patch that actually understand C constructs and are able to make intellegent decisions about merging two pieces of code, even without knowledge of other merges.
'Enhanced' is, of course, a complete understatement. What I am suggesting is basicaly adding A.I. functionality to diff and patch, to the point where they can merge three pieces of C code as efficiently as a good developer can.
This would probably involve analysing code and identifying discrete sections, (analogous to the way a human developer would draw a flow chart), within which the purpose of algorithms and variable names could be deduced. This knowledge could then be used to adapt code that was submitted as a diff against a compltely different piece of code.
Ultimately, it should be possible for two people to independently write code to do a certain task, for one of them to add an extra facility to their codebase, and for the enhanced diff and patch tools to then add this facilty to the other, completely separate, implementation.
John
Quoted 10 lines · John Bradford
Quoted 2 lines
BK is really just a merging tool that fixes rejects automatically, everything else is details...
IFF that is true, then taking this to it's logical extreme, what is the point in having an SCM system for kernel development at all?
It could be argued that what we really need is enhanced versions of diff and patch that actually understand C constructs and are able to make intellegent decisions about merging two pieces of code, even without knowledge of other merges.
But you can't always make intelligent merging decisions without knowledge about other merges.
Suppose that tree 1 has a line "x=function(3*yy)+2", and tree 2 has the corresponding line "x=fred+1". Your only merge choice is to pick one or the other. You as a fully intelligent human being have no other choice unless you're writing fresh code.
Now let's look at the patch history back to where the two trees diverged from:
Patch series:
original line:
x=yy+1;
Patch 1:
- x=yy+1;
+ x=function(3*yy)+2;
Patch 2:
- x=yy+1;
+ x=fred+1;
Looking at this, you can see that the result you probably want is "x=function(3*fred)+2;", but you couldn't figure that out until you'd see the original line they both diverged from. One tree probably had s/yy/fred/ applied to it, and the other tweaked the algorithm, thus the merges conflict going either way.
But if the original line had instead been "x=fred+2;", the logical merge would instead be "x=function(3*yy)+1;".
Original line:
x=fred+2;
Patch 1:
- x=fred+2;
+ x=function(3*yy)+2;
Patch 2:
- x=fred+2;
+ x=fred+1;
Logical merge: "x=function(3*yy)+1;"
You CANNOT KNOW THIS until you see the common ancestor they diverged from. There just isn't enough information to work it out, unless you do so from first principles by actually comprehending the algorithm being implemented and what the changes are trying to accomplish.
That's why bitkeeper has to remember all the past changes to do its job of merging new ones.
Quoted 4 lines
'Enhanced' is, of course, a complete understatement. What I am suggesting is basicaly adding A.I. functionality to diff and patch, to the point where they can merge three pieces of C code as efficiently as a good developer can.
If you've gotten AI working, why not just have it write the code and save us the trouble?
Quoted 4 lines
This would probably involve analysing code and identifying discrete sections, (analogous to the way a human developer would draw a flow chart), within which the purpose of algorithms and variable names could be deduced.
You're suggesting making a computer figure out the purpose of something. Uh-huh. Has this ever happened, even once, in the entire history of computing?
Quoted 3 lines
This knowledge could then be used to adapt code
that was submitted as a diff against a compltely different piece of code.
Written in a diferent language, performing a completely different task even...
Quoted 5 lines
Ultimately, it should be possible for two people to independently write code to do a certain task, for one of them to add an extra facility to their codebase, and for the enhanced diff and patch tools to then add this facilty to the other, completely separate, implementation.
It'd be nice, sure. I do not know how to implement that. I don't know anybody who does. If you do, by all means code it up. (My guess is you don't understand the scope of the problem, but I could always be wrong....)
Quoted 1 line
John
Rob
Quoted 11 lines
Quoted 10 lines
Quoted 2 lines
BK is really just a merging tool that fixes rejects automatically, everything else is details...
IFF that is true, then taking this to it's logical extreme, what is the point in having an SCM system for kernel development at all?
It could be argued that what we really need is enhanced versions of diff and patch that actually understand C constructs and are able to make intellegent decisions about merging two pieces of code, even without knowledge of other merges.
Quoted 7 lines
But you can't always make intelligent merging decisions without knowledge about other merges.
Suppose that tree 1 has a line "x=function(3*yy)+2", and tree 2 has the corresponding line "x=fred+1". Your only merge choice is to pick one or the other. You as a fully intelligent human being have no other choice unless you're writing fresh code.
Of course not, if you have absolutely no context whatsoever. I'm certainly not going to argue against that.
Quoted 15 lines
Now let's look at the patch history back to where the two trees diverged from:
Patch series:
original line:
x=yy+1;Patch 1:
(quoted diff) +1
-1- x=yy+1; + x=function(3*yy)+2;Patch 2:
(quoted diff) +1
-1- x=yy+1; + x=fred+1;
Quoted 3 lines
Looking at this, you can see that the result you probably want is "x=function(3*fred)+2;", but you couldn't figure that out until you'd see the original line they both diverged from.
Again, I'm not arguing against that - of course you need some context, but you don't need a complete revision history. See [1] below.
Obviously in your example, the complete revision history and the context of the patch are the same thing, as there is only one generation of revision in each case. So, you're saying that you need the patch history, well yes, you do, one generation of it. That's obvious. What I am saying is that when there are 2 or more generations of revision history, if an improvement happens between any two, you should only need those two, and no others, to apply that particular improvement another tree. See [2] below.
Quoted 18 lines
One tree probably had s/yy/fred/
applied to it, and the other tweaked the algorithm, thus the merges conflict going either way.But if the original line had instead been "x=fred+2;", the logical merge would instead be "x=function(3*yy)+1;".
Original line:
x=fred+2;Patch 1:
(quoted diff) +1
-1- x=fred+2; + x=function(3*yy)+2;Patch 2:
(quoted diff) +1
-1- x=fred+2; + x=fred+1;
Quoted 1 line
Logical merge: "x=function(3*yy)+1;"
That's not logical at all. Without any context, I don't think that you can draw a meaningful conclusion at all.
Quoted 7 lines
You CANNOT KNOW THIS until you see the common ancestor they diverged from. There just isn't enough information to work it out, unless you do so from first principles by actually comprehending the algorithm being implemented and what the changes are trying to accomplish.
That's why bitkeeper has to remember all the past changes to do its job of merging new ones.
Maybe I don't really understand how Bit Keeper works.
Imagine that somebody had a tree with the following revisions:
A1-A2-A3-A4-A5-A6
and somebody creates a patch against A1:
A1-A2-A3-A4-A5-A6
|
|
B1
then the owner of the A tree merges in B1 with A6:
A1-A2-A3-A4-A5-A6
| | | V | A7 | ^ | |
B1-------------/
[1]
Does Bit Keeper need to refer to A1, A2, A3, A4, A5, and A6 to do this merge?
[2] It's relatively easy to create A7 by looking at A1->B1, and then looking at A1->A2->A3->A4->A5->A6.
[3] It's an order of magnitude more difficult to create A7 by looking at the patch of B1 against A1, and then applying the fundamental changes that that patch introduced in to A6.
Can Bit Keeper do this?
Now, for this simple example, it's easy to say, "Ah, but a certain amount of guesswork is involved when doing [3], but with [2], the changes are much more likely to be correct, because they've been followed through all of the revisions". For simple examples, maybe that would be correct. When there are hundreds of people merging in to one tree, I don't see how you can follow each change through, unless you do have a complete revision history. I am suggesting that that is inefficient, and not scalable.
Quoted 7 lines
Quoted 4 lines
'Enhanced' is, of course, a complete understatement. What I am suggesting is basicaly adding A.I. functionality to diff and patch, to the point where they can merge three pieces of C code as efficiently as a good developer can.
If you've gotten AI working, why not just have it write the code and save us the trouble?
Nice idea. Shame I haven't got the AI working, eh?
Quoted 8 lines
Quoted 4 lines
This would probably involve analysing code and identifying discrete sections, (analogous to the way a human developer would draw a flow chart), within which the purpose of algorithms and variable names could be deduced.
You're suggesting making a computer figure out the purpose of something. Uh-huh. Has this ever happened, even once, in the entire history of computing?
I'm not sure what point you're trying to make. Analysing the high level algorithms implemented by functions written in C is certainly possible.
Quoted 5 lines
Quoted 3 lines
This knowledge could then be used to adapt code
that was submitted as a diff against a compltely different piece of code.Written in a diferent language, performing a completely different task even...
Again, I'm not sure what point you're trying to make. High level algorithms are comparable whatever language they are coded in.
Quoted 9 lines
Quoted 5 lines
Ultimately, it should be possible for two people to independently write code to do a certain task, for one of them to add an extra facility to their codebase, and for the enhanced diff and patch tools to then add this facilty to the other, completely separate, implementation.
It'd be nice, sure. I do not know how to implement that. I don't know anybody who does. If you do, by all means code it up. (My guess is you don't understand the scope of the problem, but I could always be wrong....)
If it was a 5 minute job, or even a three month job, I'd work on it. I'm not interested in spending years working on this project, which is what I thihnk it would take to develop it.
A possible place to start would be analysing one piece of code for something simple such as bounds checks, then looking back over the code to see where the values being checked came from. Similar checks could then be added to other code automatically.
John.
Quoted 4 lines · John Bradford
'Enhanced' is, of course, a complete understatement. What I am suggesting is basicaly adding A.I. functionality to diff and patch, to the point where they can merge three pieces of C code as efficiently as a good developer can.
In short, you want to implement the "graduate student algorithm" in software ?
Signature · 3 lines
"Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan
Quoted 4 lines · John Bradford
It could be argued that what we really need is enhanced versions of diff and patch that actually understand C constructs and are able to make intellegent decisions about merging two pieces of code, even without knowledge of other merges.
So what you're saying is that diff and patch should drag along all the BK functionality, databases, and so forth.....
% ls -l /usr/bin/diff /usr/bin/patch
-rwxr-xr-x 1 root root 64540 Jun 5 14:57 /usr/bin/diff
-rwxr-xr-x 1 root root 83828 Jun 5 22:41 /usr/bin/patch
% man diff | wc -l
310
% man patch | wc -l
675Larry, how big is the BK binary for an x86? And how big are the docs?
Quoted 2 lines · On Mon, Sep 29, 2003 at 09:23:32AM -0400, [email protected] wrote:
On Mon, 29 Sep 2003 12:24:47 BST, John Bradford <[email protected]> said:
Larry, how big is the BK binary for an x86? And how big are the docs?
# This includes the docs
$ du -sh /usr/libexec/bitkeeper/ 21M
# source $ bk -r cat | wc -l 1181207
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Quoted 4 lines
'Enhanced' is, of course, a complete understatement. What I am suggesting is basicaly adding A.I. functionality to diff and patch, to the point where they can merge three pieces of C code as efficiently as a good developer can.
Or maybe we don't need Linus Torvalds either. We just need an 'enhanced' robot who can code.
/sorry can't resist this one
Hua
Quoted 6 lines · Rob Landley
And the reason Andrea hasn't found bitkeeper to be nicer than CVS is he isn't trying to integrate the work of 300 other developers into his personal tree simultaneously. BK is really just a merging tool that fixes rejects automatically, everything else is details...
Am I wrong?
I think so. That's sort of like saying "the kernel is really just a program that multiplexes processes". Both are true statements if you look at the world that way but both dramatically underestimate the real picture.
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Quoted 5 lines · Linus Torvalds
That's actually a pretty good point. I end up releasing "sparse" only as a BK archive, simply because I'm too lazy to care and there aren't enough people involved (and those that _are_ involved do actually end up re-exporting it as non-BK, but that doesn't invalidate your point).
Actually, sparse taught me how life was before the internet. I had to ask someone else to get it for me, don't want to bother him on a regular basis and am stuck with an old version. Not that I've done anything with it worth giving back, but I do feel the pain.
On the other hand, if it matters enough, people will find solutions. Would be nice, if Larry coded up something central that all projects could benefit from, but that is not necessary. All projects that grow important enough will have a solution someday.
BTW: Is there a non-bk way to get recent sparse code yet?
Jörn
Signature · 3 lines
He who knows others is wise. He who knows himself is enlightened. -- Lao Tsu
Quoted 2 lines · J?rn Engel
Would be nice, if Larry coded up something central that all projects could benefit from, but that is not necessary.
Is the "bkbits.net can export any patch and/or version of a tree as plain text" match what you are asking for or not?
So if there was a URL that you could type in that fed you the patch as plain text, with any associated checkin comments, is that what you meant?
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Quoted 6 lines · Larry McVoy
Quoted 2 lines · J?rn Engel
Would be nice, if Larry coded up something central that all projects could benefit from, but that is not necessary.
Is the "bkbits.net can export any patch and/or version of a tree as plain text" match what you are asking for or not?
Something like that, yes.
Quoted 2 lines
So if there was a URL that you could type in that fed you the patch as plain text, with any associated checkin comments, is that what you meant?
That would be perfect, I would even go for a lot less. As long as I can recreate last weeks code of my pet project of the day, life is good. But feel free to make it even better. :)
Actually, you already do that, just with some html around it. That could be stripped off on your side to save bandwidth or I could do it myself with a little perl.
Either way, nice service. Should have looked there earlier.
Jörn
Signature · 2 lines
He who knows that enough is enough will always have enough. -- Lao Tsu
OT go to gnu-arch-users for these matters (Re: log-buf-len dynamic)
Quoted 3 lines · Jörn Engel
Actually, you already do that, just with some html around it. That could be stripped off on your side to save bandwidth or I could do it myself with a little perl.
I already did that in python, no need to reinvet the wheel :)
It works fine for any project hosted on bkbits but only as far as you've a reference point to start with (i.e. you've an old tarball) and as far as there are no merge from cloned trees in the main branch.
http://www.us.kernel.org/pub/linux/kernel/people/andrea/openbkweb/openbkweb-0.0.tar.gz
I'll let it die quickly first because it was using too much bandwidth according to Larry, and secondly because it couldn't handle merges across different trees. that's why Larry provided us with the bkcvs then. But it should still work in theory, though I doubt it can be very useful if they do merges.
BTW, for obvious reasons I'm posting emails on these matter _only_ on gnu-arch-users, I already suggested a number of features I need and that I'd like to add to arch to be usable for my 2.4-aa (for an usage like b*tkeeper it seems just usable right now but I need more dedicated features to be able to maintain my tree with a revision control system, like being able to hook [tag in arch terms] to a unpacked tree with hardlinks and be able to rollback rejecting patchsets and overwriting them in new revisions, and automatic conversion from patchsets to an ordered serie of patches with a meaningful name). All the details here:
http://mail.gnu.org/mailman/listinfo/gnu-arch-users
thanks,
Andrea - If you prefer relying on open source software, check these links:
rsync.kernel.org::pub/scm/linux/kernel/bkcvs/linux-2.[45]/ http://www.cobite.com/cvsps/ svn://svn.kernel.org/linux-2.[46]/trunk
On Thu, 25 Sep 2003 20:22:33 +0200 Jörn Engel <[email protected]> wrote:
| On Thu, 25 September 2003 10:30:58 -0700, Linus Torvalds wrote: | > | > That's actually a pretty good point. I end up releasing "sparse" only as a | > BK archive, simply because I'm too lazy to care and there aren't enough | > people involved (and those that _are_ involved do actually end up | > re-exporting it as non-BK, but that doesn't invalidate your point). | | Actually, sparse taught me how life was before the internet. I had to | ask someone else to get it for me, don't want to bother him on a | regular basis and am stuck with an old version. Not that I've done | anything with it worth giving back, but I do feel the pain. | | On the other hand, if it matters enough, people will find solutions. | Would be nice, if Larry coded up something central that all projects | could benefit from, but that is not necessary. All projects that grow | important enough will have a solution someday. | | BTW: Is there a non-bk way to get recent sparse code yet?
Snapshots are available at
http://www.codemonkey.org.uk/projects/sparse/
--
~Randy
Quoted 18 lines · Linus Torvalds
Quoted 11 lines · Eric W. Biederman
Quoted 5 lines
However, that only explains why you don't use BitKeeper. And everybody accepts that. When I started to use BK, I made it _very_ clear that service for non-BK users will be _at_least_ as good as it ever was before I started using BK.
And for the core kernel development this is true. There are subprojects that are currently using BK that you can't even get the code without BK. And the only reason they are using BK is they are attempting to following how Linux is managed. So having the Linux kernel development use BK does have some down sides.
That's actually a pretty good point. I end up releasing "sparse" only as a BK archive, simply because I'm too lazy to care and there aren't enough people involved (and those that _are_ involved do actually end up re-exporting it as non-BK, but that doesn't invalidate your point).
Quoted 4 lines
I don't know what the solution to it might be - but I don't think the reason they are using BK is that they are trying to emulate "the great kernel project". I know it wasn't for me - it's just that once you get used to BK, there's no way you'll ever go back to CVS willingly.
I expressed it badly. But the kernel using BK both introduces people to BK, and it validates BK as a useful tool. Especially as the kernel tends to embody many of the best practices in the community.
The only sure piece of the solution I have it to keep saying there is a problem, and to raise the level of the conversation to it's technical merits.
Quoted 7 lines
Quoted 3 lines
In addition there are some major gains to be had in standardizing on a distributed version control system that everyone can use, and unfortunately BK does not fill that position.
I don't disagree, but I don't see a real way to solve it. As Larry will tell you, the technical problems are bigger than you imagine. So a BK killer won't be coming any time soon, methinks.
It does not have to start as a BK killer. Just something that is architecturally sound, once all of the basics work adding the polish can be done by the community.
I am pretty certain I could write up something that got the core of the repository right in a month or two. The hard part is avoiding mistakes in repository architecture. CVS has never recovered, despite a lot of good work put into it. For the few blunders Larry has made he has worked very hard to correct things.
But of course if I do something I won't be targeting the kernel developers directly. I will do it to solve my problems on the projects I lead. Which may not map well to kernel development. But doing anything else would be an academic exercise because I could not maintain it.
Eric
Quoted 5 lines · Eric W. Biederman
And for the core kernel development this is true. There are subprojects that are currently using BK that you can't even get the code without BK. And the only reason they are using BK is they are attempting to following how Linux is managed. So having the Linux kernel development use BK does have some down sides.
I was expecting this to come up when Linus first made sparse publically available only by bitkeeper, so I started the nightly snapshots. If there's any other Linux related project that's bitkeeper only let me know, and I'll be happy to host nightly snapshots of that too.
Dave
Signature · 1 line
Dave Jones http://www.codemonkey.org.uk
Quoted 10 lines · Dave Jones
Quoted 5 lines · Eric W. Biederman
And for the core kernel development this is true. There are subprojects that are currently using BK that you can't even get the code without BK. And the only reason they are using BK is they are attempting to following how Linux is managed. So having the Linux kernel development use BK does have some down sides.
I was expecting this to come up when Linus first made sparse publically available only by bitkeeper, so I started the nightly snapshots.
Qwest is taking forever with our T1 lines but once that problem is solved we'll put up a version of the BK server on bkbits that will give you either GNU style patches or tarballs of an exported tree. Then *all* projects mirrored on bkbits are automagically exported to good old plain text format.
And, because people might want to build their own gateways (we can only hope) the diffs can be extracted with checkin comments as shown below. That ought to be sufficient so that you can do whatever you want. I'm pretty sure that patch(1) will just ignore all the leading comments.
How's that?
===== panic.c 1.12 vs + =====
2003/08/07 10:29:13 [email protected] 1.13 +6 -1
Don't trigger NMI watchdog for panic delay
kernel/panic.c Thu Aug 7 10:29:13 2003 renamed from kernel/panic.c Mon May 12 11:11:38 2003 +6 -1
@@ -16,6 +16,7 @@ #include <linux/init.h> #include <linux/sysrq.h> #include <linux/interrupt.h> +#include <linux/nmi.h> asmlinkage void sys_sync(void); /* it's really int */
@@ -71,12 +72,16 @@ NORET_TYPE void panic(const char * fmt, if (panic_timeout > 0) { + int i; /* * Delay timeout seconds before rebooting the machine. * We can't use the "normal" timers since we just panicked.. */ printk(KERN_EMERG "Rebooting in %d seconds..",panic_timeout); - mdelay(panic_timeout*1000); + for (i = 0; i < panic_timeout; i++) { + touch_nmi_watchdog(); + mdelay(1000); + } /* * Should we run the reboot notifier. For the moment Im * choosing not too. It might crash, be corrupt or do
Quoted 8 lines · Dave Jones
Quoted 5 lines · Eric W. Biederman
And for the core kernel development this is true. There are subprojects that are currently using BK that you can't even get the code without BK. And the only reason they are using BK is they are attempting to following how Linux is managed. So having the Linux kernel development use BK does have some down sides.
Quoted 4 lines
I was expecting this to come up when Linus first made sparse publically available only by bitkeeper, so I started the nightly snapshots. If there's any other Linux related project that's bitkeeper only let me know, and I'll be happy to host nightly snapshots of that too.
The linux infiniband project, is actually what I was thinking of.
http://infiniband.sourceforge.net/
Eric
Quoted 5 lines · Eric W. Biederman
In addition there are some major gains to be had in standardizing on a distributed version control system that everyone can use, and unfortunately BK does not fill that position. So I think it is good that there is enough general discontent it the air that people continue to look for alternatives.
Let's just postulate that my claim that this is harder than it looks is true. You don't have to agree with it, just pretend you do. Given that, it's going to be a while before any alternative shows up. People mumble about arch until they go use it for a while and realize it is about 3-5 years behind BK. Linus isn't about to step backwards that far.
Quoted 1 line
The current situation with version control is painful.
No kidding. Do you have any suggestions, _realistic_ suggestions, that we could do to help? Beyond making plain text patches/tarballs available from every repo hosted on bkbits?
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Quoted 7 lines · Larry McVoy
Quoted 5 lines · Eric W. Biederman
In addition there are some major gains to be had in standardizing on a distributed version control system that everyone can use, and unfortunately BK does not fill that position. So I think it is good that there is enough general discontent it the air that people continue to look for alternatives.
Quoted 5 lines
Let's just postulate that my claim that this is harder than it looks is true. You don't have to agree with it, just pretend you do. Given that, it's going to be a while before any alternative shows up. People mumble about arch until they go use it for a while and realize it is about 3-5 years behind BK. Linus isn't about to step backwards that far.
Nope. I won't. I would much rather postulate that it is easier than it looks so someone will get started :)
Quoted 5 lines
Quoted 1 line
The current situation with version control is painful.
No kidding. Do you have any suggestions, _realistic_ suggestions, that we could do to help? Beyond making plain text patches/tarballs available from every repo hosted on bkbits?
patches/tarballs and a clear way to find them would certainly help. And would pretty much put a project on bkbits on par with the non bk alternatives, for usability.
Eric
Quoted 7 lines · Larry McVoy
Quoted 5 lines · Eric W. Biederman
In addition there are some major gains to be had in standardizing on a distributed version control system that everyone can use, and unfortunately BK does not fill that position. So I think it is good that there is enough general discontent it the air that people continue to look for alternatives.
Quoted 5 lines
Let's just postulate that my claim that this is harder than it looks is true. You don't have to agree with it, just pretend you do. Given that, it's going to be a while before any alternative shows up. People mumble about arch until they go use it for a while and realize it is about 3-5 years behind BK. Linus isn't about to step backwards that far.
Have you tried it lately? I'm not sure who's behind because I've never used bk, but only having a look at arch and using it for a couple of weeks would convince anybody of the opposite. Just wait that there is a linux arch repo with the bk detail and facts will speak.
That's why there's the need of having all the bk linux related repos exported to CVS, not to limit linux development. If only one of these repos is not exported, many people have difficulties in keeping off bk. I appreciate you comment that all will be exported RSN.
The same that you demand respect for bk, please respect the others too and don't spread false comments. Moreover, you are on an advantadgeous position as you can test arch, read its code and learn -it's GPLed-, while the rest of people can't even benchmark arch with bk as it's forbidden by your license. Don't misunderstand me, I'm not flaming anyone, I'm just exposing facts.
Quoted 5 lines
Quoted 1 line
The current situation with version control is painful.
No kidding. Do you have any suggestions, _realistic_ suggestions, that we could do to help? Beyond making plain text patches/tarballs available from every repo hosted on bkbits?
It would be great to keep an arch gateway with the same detail than bk changesets. It looks very easy to do.
Pau
Quoted 2 lines · [email protected] (Eric W. Biederman) writes:
ARCH is barely distributed and architecturally it makes distributed merging hard.
Are you are kidding? Arch is _insanely_ good at handling both distributed repositories and merging -- those are if anything its greatest strengths. Everyday development of tla (the latest/greatest arch implementation) involves many people with their own repositories, merging back and forth.
Really, if you have explicit complaints/observations about arch's handling of these things, please share them, because on the surface that statement just seems kind of bizarre.
-Miles
Signature · 1 line
`The suburb is an obsolete and contradictory form of human settlement'
Quoted 9 lines · Miles Bader
Quoted 2 lines · [email protected] (Eric W. Biederman) writes:
ARCH is barely distributed and architecturally it makes distributed merging hard.
Are you are kidding? Arch is _insanely_ good at handling both distributed repositories and merging -- those are if anything its greatest strengths. Everyday development of tla (the latest/greatest arch implementation) involves many people with their own repositories, merging back and forth.
I definitely agree. It's about a couple of months that I'm playing with it and I have to say that it works great with distributed development. It basically born with that as the very first design rule. It also look very stable AFAICS. And, the old collection of shell scripts (that I didn't like in the beginning) is shaping out toward C code. In three words, I like it. I cannot compare it to bk because I never used it (not because of the license, and not even for political/personal reasons, but because I haven't had any time to do it in the past), and I am sure it still lacks of some useful features when matched with bk, but the fundamentals are definitely there.
- Davide
Before replying, I should let you know that I have made an Arch repository containing every version of Linux since 0.01 clear through 2.6.0-test5 available at http://arch.debian.org/. Please see the docs there for more info. While I have learned a lot about Arch since then (particularly relating to proper naming of categories), you should still be able to use it to experiment with the strengths and weaknesses of arch, particularly relating to branching and marging.
Quoted 3 lines · [email protected] (Eric W. Biederman) writes:
The current situation with version control is painful. CVS branches poorly and is not distributed. SVN is not distributed. ARCH is barely distributed and architecturally it makes distributed merging
That is completely wrong wrt arch; in fact, I would say it is the most intrinsically distributed of any VC system I've seen. Please see:
Elementary Branches
http://regexps.srparish.net/tutorial-tla/elementary-branches.html
Development Branches with star-merge
http://regexps.srparish.net/tutorial-tla/development-branches.html
Introducing Changesets
http://regexps.srparish.net/tutorial-tla/introducing-changesets.html
-- John
Quoted 11 lines · Linus Torvalds
Use CVS and be happy. But don't complain to others that have needs that CVS simply can't fill.
....
Indeed. That's pretty much all non-distributed stuff is useful for, from where I'm stading. Small projects with a few developers and a lot of read-only stuff. And even there the developers will bitch about the limitations.Sure, SVN makes branches cheaper, but you still have to work with them like under CVS, ie merging is a total disaster. And you still can't make it your private repository.
No flame wars intended, but arch does this and more. See:
http://savannah.gnu.org/projects/gnu-arch
Distributed, complex merging, easy branches... and even a linux repository from 0.1, not yet in the detail of the current cvs or bk, but easyly achievable if anyone is interested in spending the time to import it.
Pau