- Merge the changes that fixed bug #5212 from branch A to branch B. Don't merge any of the other development that has happened in branch A since then. Make sure to get all the files that were affected.
Simply put, CVS doesn't do this well.
Can you tell us any tool which can handle this better? IMHO, in general case I can't imagine any better way than CVS way of doing this. Or is just that you don't know it's possible to get changes between any two versions and get it applied to some other version?
You might use this to get extra error correction. Store ECC on other CD.
Apply it to ISO filesystem you are creating, so when CD get's damaged, read everything you get to file, and use this to get original ISO-image.
Only problem is, error correction is for bit changes, and normally, when you have broken CD, you can't read part of it at all. So you have to insert missing bits to ISO-image (plain 0) to correct place before using error correction. Don't ask me how, dd conv=noerr will give you all data it can get, no idea where's something missing.
One solution might be writing some structured data, where you can find block numbers from data. CD doesn't have to have ISO filesystem, or filesystem at all. Just create own dataformat, and write it to CD. And tell us when you have solution available!
Slashdot Mirror
Have you checked it's not in http://www.unmaintained-free-software.org/
1) Brains faster than hands. You don't have to be absolutely fast on thinking, but you must be able to think before doing.
2) Ability to read manuals. Start by man man
I think you have right window manager, it's question have you configured it properly.
Take a look at here for example. Direction-command is something usefull you may not have noticed.
Gramofile was mentitioned earlier, but in addition, take a look at xmcd2make
If you just need SQL for one app, take look at SQLite. It's not client-server db, but SQL provided on top of gdbm files.
- Merge the changes that fixed bug #5212 from branch A to branch B. Don't merge any of the other development that has happened in branch A since then. Make sure to get all the files that were affected.
Simply put, CVS doesn't do this well.
Can you tell us any tool which can handle this better? IMHO, in general case I can't imagine any better way than CVS way of doing this. Or is just that you don't know it's possible to get changes between any two versions and get it applied to some other version?
IMHO, /. shouldn't have any animated gif ads. At least some of them generate too much load with netscape & X, so my mpg123 won't get enough time. Yack!
Apply it to ISO filesystem you are creating, so when CD get's damaged, read everything you get to file, and use this to get original ISO-image.
Only problem is, error correction is for bit changes, and normally, when you have broken CD, you can't read part of it at all. So you have to insert missing bits to ISO-image (plain 0) to correct place before using error correction. Don't ask me how, dd conv=noerr will give you all data it can get, no idea where's something missing.
One solution might be writing some structured data, where you can find block numbers from data. CD doesn't have to have ISO filesystem, or filesystem at all. Just create own dataformat, and write it to CD. And tell us when you have solution available!