| 1 |
On 08/05/2014 21:13, James wrote: |
| 2 |
> So, what a torrent_style tool that uses a distributed hashes/keys to check |
| 3 |
> code integrity; is possible? |
| 4 |
|
| 5 |
In one word: git |
| 6 |
|
| 7 |
> Surely the code histogram idea is possible? |
| 8 |
|
| 9 |
Again, git. |
| 10 |
|
| 11 |
An aspect of the git design spec is to try deal with the kind of things |
| 12 |
you are pondering here. It seems a valid approach - if many people out |
| 13 |
there clone and make copies of the code then work on it, and if a bad |
| 14 |
hat injects some weirdness, there are enough eyes to hopefully catch it. |
| 15 |
|
| 16 |
Now that I think of it, it's an elegant solution: |
| 17 |
|
| 18 |
Avoid the problems of a single master store but not having one. |
| 19 |
|
| 20 |
-- |
| 21 |
Alan McKinnon |
| 22 |
alan.mckinnon@×××××.com |
Archives