-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Howdy all,
I don't know who decided that .monotone/keys was a good idea but it is
a DISASTER for me.
For various reasons It is desirable to use the same real world
identity, q.v. [EMAIL PROTECTED], in several different databases with
different keys
Daniel Carrera wrote:
Robert White wrote:
If you don't believe in these use cases, consider contractors who may
need to keep work separate for different employers but will want to
use their one business email address for all their business;
One thing I don't understand is why
Daniel Carrera wrote:
Robert White wrote:
One thing I don't understand is why this contractor needs different
keys for each employer.
Try things like wanting to be able to revoke/destroy one key when the
contract is over etc.
Why would I want to do that?
The question isn't whether
Ethan Blanton wrote:
That said, the conflation of email address and key ID is an
unfortunate early design decision in monotone which pretty much
everyone now understands was not ideal. Keys in databases are not
ideal for other reasons (databases should not be sensitive, as it is
reasonable to
Timothy Brownawell wrote:
There is another use, where people will often want to use the same key
in multiple databases that do talk to eachother. If a key is local to a
database, it's more common that they'll generate a second key with the
same name and have problems when syncing both databases
Sebastian Rose wrote:
(a bunch of drivel based on the belief that old databases and data are
inferior to new information in all circumstances, so if my databases
were old they
were unworthy.)
A nice ad-hominim deserves retaliation in kind, but since you are
sleepy I'll leave it at that...
So here is five of the most dangerous words in computing:
So I have been thinking...
A lot of people who use CVS don't really use modules. Some of us do. I
am a huge fan of modules because of the need to make stable builds in a
world where projects need to share sub-projects. In
