From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Possible regression and bug in userdom_base_user_template
Date: Tue, 02 Mar 2010 09:19:51 -0500 [thread overview]
Message-ID: <4B8D1E87.50001@redhat.com> (raw)
In-Reply-To: <1267539196.30557.71.camel@gorn.columbia.tresys.com>
On 03/02/2010 09:13 AM, Christopher J. PeBenito wrote:
> On Mon, 2010-03-01 at 21:14 +0100, Michal Svoboda wrote:
>
>> Martin Orr wrote:
>>
>>> Yes, this is a Debian only patch. According to my history, it was
>>> added somewhere between 0.0.20080702-1 and 0.0.20080702-4.
>>>
>> Sigh. I guess the reasoning behind this is the same as in fedora? I'm
>> getting a little dizzy about these distro specific patches. Sad too.
>>
> Well, unfortunately, thats how things work in Linux distros. If you
> look at Fedora cvs or other distros' packaging RCSs, you'll see patching
> happening on many packages.
>
>
That is also how innovation happens. When someone has a good idea they
first try it out within their distribution. If it turns out it works
well then hopefully they upstream it. If upstream accepts the patch
then all distributions benefit. Sometimes upstream does not accept the
patch for one reason or another and distributions copy each others patches.
next prev parent reply other threads:[~2010-03-02 14:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 10:54 [refpolicy] Possible regression and bug in userdom_base_user_template Michal Svoboda
2010-02-24 14:29 ` Christopher J. PeBenito
2010-02-24 15:10 ` Alan Rouse
2010-02-24 14:36 ` Daniel J Walsh
2010-03-01 10:22 ` Michal Svoboda
2010-03-01 13:39 ` Daniel J Walsh
2010-03-01 13:42 ` Christopher J. PeBenito
2010-03-01 15:01 ` Michal Svoboda
2010-03-01 15:32 ` Christopher J. PeBenito
2010-03-01 17:03 ` Michal Svoboda
2010-03-01 17:48 ` Martin Orr
2010-03-01 20:14 ` Michal Svoboda
2010-03-02 14:13 ` Christopher J. PeBenito
2010-03-02 14:19 ` Daniel J Walsh [this message]
2010-03-03 20:22 ` Michal Svoboda
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=4B8D1E87.50001@redhat.com \
--to=dwalsh@redhat.com \
--cc=refpolicy@oss.tresys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.