public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: Vladimir Makarov <vmakarov@redhat.com>
Cc: overseers@sourceware.org
Subject: Re: sourceware/gcc ssh public key analysis
Date: Wed, 13 Jan 2016 10:48:00 -0000	[thread overview]
Message-ID: <alpine.LSU.2.20.1601131507160.8075@anthias> (raw)
In-Reply-To: <5695C7B9.4000106@redhat.com>

On Tue, 12 Jan 2016, Vladimir Makarov wrote:
> On 01/12/2016 08:33 PM, Ian Lance Taylor wrote:
>> Installed.  But actually I think you could have installed it yourself.
> Thanks, Ian.  And sorry for bothering you.  I tried to install it by using
> rsync or scp but it did not work.  May be there is another way I don't know.

https://gcc.gnu.org/svnwrite.html#account tries to cover it.

If you have a recomendation on where/how to link there more
prominently, I'll happily have a look making such a change.

Gerald

  reply	other threads:[~2016-01-13 10:48 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20160112220954.72461.qmail@sourceware.org>
     [not found] ` <569598D0.9010304@redhat.com>
2016-01-13  0:27   ` Vladimir Makarov
2016-01-13  1:34     ` Ian Lance Taylor
2016-01-13  3:42       ` Vladimir Makarov
2016-01-13 10:48         ` Gerald Pfeifer [this message]
     [not found] <20160112220926.52144.qmail@sourceware.org>
2016-01-13  7:07 ` Tobias Burnus
2016-01-13 13:20   ` Ian Lance Taylor
     [not found] <20160112220924.50132.qmail@sourceware.org>
2016-01-13  9:39 ` Andrew Stubbs
2016-01-13 13:21   ` Ian Lance Taylor
     [not found] <20160112220925.51505.qmail@sourceware.org>
2016-01-13 10:31 ` Brian Gough
2016-01-13 15:00   ` Christopher Faylor
     [not found] <20160112220949.67889.qmail@sourceware.org>
2016-01-13 20:55 ` Volker Reichelt
     [not found] <20160112220949.67993.qmail@sourceware.org>
2016-01-14 12:30 ` Ricard Wanderlof
2016-01-14 18:14   ` Frank Ch. Eigler
     [not found] <20160112220924.50203.qmail@sourceware.org>
2016-01-17  2:29 ` Joern Wolfgang Rennecke
2016-01-21 12:54 Alfred M. Szmidt
2016-01-21 15:06 ` Ian Lance Taylor
2016-01-21 15:45   ` Alfred M. Szmidt
     [not found] <20160112220927.53009.qmail@sourceware.org>
2016-01-21 17:44 ` Chris Metcalf
     [not found]   ` <20160126162348.GA14318@elastic.org>
2016-07-05 21:20     ` Chris Metcalf
2016-07-05 21:40       ` Christopher Faylor
2016-07-05 21:49         ` Christopher Faylor
2016-07-06  0:43           ` Chris Metcalf
     [not found] <20160112220953.71700.qmail@sourceware.org>
2016-02-18 13:35 ` Tom Tromey
2016-02-18 15:30   ` Frank Ch. Eigler
     [not found] <20160112220955.73318.qmail@sourceware.org>
2016-03-08 16:00 ` Zack Weinberg
     [not found] <20160112220930.55610.qmail@sourceware.org>
2020-03-07 18:47 ` Ed Smith-Rowland
     [not found] <20160112220951.69787.qmail@sourceware.org>
     [not found] ` <2F12E318-AF48-47F5-98D0-03421055FE59@nasilyan.com>
2024-03-23 15:32   ` Simon Martin
2024-03-23 21:56     ` Mark Wielaard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LSU.2.20.1601131507160.8075@anthias \
    --to=gerald@pfeifer.com \
    --cc=overseers@sourceware.org \
    --cc=vmakarov@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).