public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Justin Lecher" <jlec@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/recruiters:master commit in: /
Date: Sun, 10 Jan 2016 11:56:30 +0000 (UTC)	[thread overview]
Message-ID: <1452426983.d9e2cce6eb5b3980fc35a49a7e1f1909c2520574.jlec@gentoo> (raw)

commit:     d9e2cce6eb5b3980fc35a49a7e1f1909c2520574
Author:     Justin Lecher <jlec <AT> gentoo <DOT> org>
AuthorDate: Sun Jan 10 11:56:23 2016 +0000
Commit:     Justin Lecher <jlec <AT> gentoo <DOT> org>
CommitDate: Sun Jan 10 11:56:23 2016 +0000
URL:        https://gitweb.gentoo.org/proj/recruiters.git/commit/?id=d9e2cce6

Add Q about dynamic deps

Signed-off-by: Justin Lecher <jlec <AT> gentoo.org>

 questions | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/questions b/questions
index 5220b58..9abfdf5 100644
--- a/questions
+++ b/questions
@@ -12,6 +12,8 @@ Quiz Questions:
   * All devs who are official devs with start of voting period
 - What would you do if you were not happy with what comrel decided?
   * Council can overrule all Comrel decisions
+- What are dynamic deps? And why schould they be avoided?
+  *
 - What are GLSAs? How do they come into play in day to day developer work?
   * 
 - What is the difference between einfo and elog?


             reply	other threads:[~2016-01-10 11:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-10 11:56 Justin Lecher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-10-25 12:25 [gentoo-commits] proj/recruiters:master commit in: / Amy Winston
2016-10-25 11:58 Amy Winston
2016-10-25 11:28 Amy Winston
2016-04-03  7:49 Justin Lecher
2016-01-10 15:22 Justin Lecher
2016-01-10 12:00 Justin Lecher
2015-12-17 16:08 Justin Lecher
2015-11-26 11:37 Justin Lecher
2015-09-18 12:46 Justin Lecher
2015-08-24 20:26 Mikle Kolyada
2015-08-21 18:44 Justin Lecher
2015-08-21 18:03 Justin Lecher

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=1452426983.d9e2cce6eb5b3980fc35a49a7e1f1909c2520574.jlec@gentoo \
    --to=jlec@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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
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