Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Getting patches committed
Date: Fri, 22 Jan 2010 01:37:42 +0100	[thread overview]
Message-ID: <hjas0r$h18$1@ger.gmane.org> (raw)
In-Reply-To: <1264119214.7697.73.camel@utx.utx.cz>

Stanislav Brabec wrote:
>> FFA branches.  Second, RP and I agreed that security implications are a
>> concern if we allow commit access completely uninhibited.
> 
> Security in world of open source is is always based on web of trust.

Hehe, I was really referring to something else, namely the security of
the git repository host computer.




  reply	other threads:[~2010-01-22  0:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-21  9:43 Getting patches committed Paul Menzel
2010-01-21 10:02 ` Holger Hans Peter Freyther
2010-01-21 10:20   ` Dr. Michael Lauer
2010-01-21 10:30     ` Holger Hans Peter Freyther
2010-01-21 12:15     ` Philip Balister
2010-01-21 12:36       ` Thomas Zimmermann
2010-01-21 12:45         ` Philip Balister
2010-01-21 19:06           ` Paul Menzel
2010-01-21 15:49         ` Konrad Mattheis
2010-01-21 19:10       ` Paul Menzel
2010-01-21 12:16     ` Rolf Leggewie
2010-01-21 12:34       ` Frans Meulenbroeks
2010-01-21 19:01         ` Paul Menzel
2010-01-21 19:48       ` Martin Jansa
2010-01-21 22:06         ` Stanislav Brabec
2010-01-21 22:00       ` Stanislav Brabec
2010-01-21 23:11         ` Rolf Leggewie
2010-01-22  0:13           ` Stanislav Brabec
2010-01-22  0:37             ` Rolf Leggewie [this message]
2010-01-22  0:40             ` Richard Purdie
2010-01-22  7:53             ` Holger Hans Peter Freyther
2010-01-22 11:44           ` Petr Štetiar
2010-01-22 14:53             ` Rolf Leggewie
2010-01-22 16:15               ` Petr Štetiar
2010-01-22 16:44                 ` Rolf Leggewie

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='hjas0r$h18$1@ger.gmane.org' \
    --to=no2spam@nospam.arcornews.de \
    --cc=openembedded-devel@lists.openembedded.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