Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: bugzilla-daemon@libre-riscv.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 265] new server from raptorcs needs set up with build/test environment
Date: Mon, 23 Mar 2020 08:14:08 +0000
Message-ID: <bug-265-13-rNBSbM65E9@http.bugs.libre-riscv.org/> (raw)
In-Reply-To: <bug-265-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=265

--- Comment #4 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to vklr@vkten.in from comment #3)

> > the VPN also has access to libre-riscv.org, to the build server that jacob
> > set up, and to my laptop.  so we need to be careful.
> 
> Luke, I will try. 

appreciated.

> How quickly it has to be done? How much time I would have
> to
> spend? 

it's not a major blocker at the moment.

> I am sending you my ssh pub key by mail.

appreciated.  got it.  what's your preferred username?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

  parent reply index

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-22 23:28 [libre-riscv-dev] [Bug 265] New: new server from raptorcs needs set up with build/test rnvironment bugzilla-daemon
2020-03-22 23:36 ` [libre-riscv-dev] [Bug 265] " bugzilla-daemon
2020-03-23  0:07 ` [libre-riscv-dev] [Bug 265] new server from raptorcs needs set up with build/test environment bugzilla-daemon
2020-03-23  1:53 ` bugzilla-daemon
2020-03-23  8:14 ` bugzilla-daemon [this message]
2020-03-23  9:12 ` bugzilla-daemon
2020-03-23 12:31 ` bugzilla-daemon
2020-03-23 12:50 ` bugzilla-daemon

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=bug-265-13-rNBSbM65E9@http.bugs.libre-riscv.org/ \
    --to=bugzilla-daemon@libre-riscv.org \
    --cc=libre-riscv-dev@lists.libre-riscv.org \
    /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

Libre RISC-V Mailing list Archives (accessible via public-inbox)

Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev

Example config snippet for mirrors


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git