This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: New SVN Wiki page


On Fri, Oct 28, 2005 at 01:30:13AM +0200, Giovanni Bajo wrote:
>Mike Stump <mrs@apple.com> wrote:
>
>>> Uhm, I'm not sure how to explain this without being too pedantic.
>>> Does this
>>> sound clearer?
>>
>> This tool tracks each individual change (fine-grained) and will never
>> reapply an already applied change.
>>
>> I think that is a high level answer, and completely answers the
>> question to people that have the question, while doing as little as
>> possible to confuse someone that doesn't even have the question.
>> Anyone doing merges should have the question and understand the
>> answer.
>>
>> Or, you can say it merges in N-1 to N, when one requests a merge of
>> N.  A totally different way of expressing the same thing, and conveys
>> the same information.
>>
>> Sound reasonable?
>
>Thanks for the suggestion, I have incorporated this into the Wiki page, I hope
>it's clearer now.

I just updated the cvs/svn shell on gcc.gnu.org.  It now has the ability
to add a v2 key to the system:

  ssh gcc.gnu.org 'updatekey' < ~/.ssh/id_rsa.pub

This will add the id_rsa.pub to the authorized_keys file on gcc.gnu.org.
It will, of course, only work if you are already able to access the
system.

Should the wiki be updated to reflect this change?

As a meta-issue, maybe we should actively promote that people update
their keys and eventually turn off the v1 keys entirely?

cgf


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]