<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
If I wrote a guide on setting up the Nvidia SDK for CUDA with OpenCL implementation, would it go in the fedora docs? Or.......is there a wiki place for something like this. I would like to do it for my own reference as well as for others. Thnks. All replies are welcome.<div><br></div><div>William(tertl3)<br><br>> From: docs-request@lists.fedoraproject.org<br>> Subject: docs Digest, Vol 79, Issue 15<br>> To: docs@lists.fedoraproject.org<br>> Date: Sat, 18 Sep 2010 12:00:08 +0000<br>> <br>> Send docs mailing list submissions to<br>> docs@lists.fedoraproject.org<br>> <br>> To subscribe or unsubscribe via the World Wide Web, visit<br>> https://admin.fedoraproject.org/mailman/listinfo/docs<br>> or, via email, send a message with subject or body 'help' to<br>> docs-request@lists.fedoraproject.org<br>> <br>> You can reach the person managing the list at<br>> docs-owner@lists.fedoraproject.org<br>> <br>> When replying, please edit your Subject line so it is more specific<br>> than "Re: Contents of docs digest..."<br>> <br>> <br>> Today's Topics:<br>> <br>> 1. Re: Docs site (Justin Clift)<br>> 2. Re: Docs site (daniel cabrera)<br>> 3. Re: Docs site (Mike McGrath)<br>> 4. Re: Fwd: SE Linux docs (Karsten Wade)<br>> 5. Re: Fwd: SE Linux docs (John J. McDonough)<br>> 6. Re: Fwd: SE Linux docs (Paul W. Frields)<br>> <br>> <br>> ----------------------------------------------------------------------<br>> <br>> Message: 1<br>> Date: Fri, 17 Sep 2010 22:04:49 +1000<br>> From: Justin Clift <justin@salasaga.org><br>> Subject: Re: Docs site<br>> To: For participants of the Documentation Project<br>> <docs@lists.fedoraproject.org><br>> Cc: Piotr Dr?g <piotrdrag@gmail.com><br>> Message-ID: <4C935961.3060805@salasaga.org><br>> Content-Type: text/plain; charset=UTF-8; format=flowed<br>> <br>> On 09/17/2010 04:24 PM, Piotr Dr?g wrote:<br>> <snip><br>> > Anyway, reverting a bad commit is easy, basically it's "git revert<br>> > commit_hash". Commit hash can be obtained from some git command I<br>> > don't know or from my favorite gitweb. :)<br>> <br>> (in case it's useful, or anyone's curious)<br>> <br>> The command "git log" could be what you want. It shows the history<br>> of what has been committed, with the most recent first, then the commit<br>> before it, then the one before that, and so on:<br>> <br>> $ git log<br>> commit 10c592801c32247d1d82520df17ae409d2e55fc7<br>> Author: Eric Blake <eblake@redhat.com><br>> Date: Thu Sep 9 20:32:50 2010 -0600<br>> <br>> tests: clean up qemuargv2xmltest<br>> <br>> Since commit 107a7bd06bc, the extraFlags argument was unused.<br>> <br>> * tests/qemuargv2xmltest.c (DO_TEST): Drop extraFlags argument.<br>> Adjust all callers.<br>> <br>> commit df1718cc7366296be4ab71c830cc2b93e505ceec<br>> Author: Justin Clift <jclift@redhat.com><br>> Date: Thu Sep 16 22:14:18 2010 +1000<br>> <br>> docs: reworked the policykit patch submitted by Patrick Dignan<br>> <br>> Tweaked the PolicyKit documentation improvement patch submitted<br>> by Patrick Dignan.<br>> <br>> Additionally, removed the reference to PolicyKit.conf, which is<br>> no longer used by PolicyKit, plus added a link to the expanded<br>> PolicyKit example page on the wiki.<br>> <br>> commit 5bc4307597d382ab8a951feee0daf13439926238<br>> <snip><br>> <br>> There's also a "--oneline" version:<br>> <br>> $ git log --oneline<br>> 10c5928 tests: clean up qemuargv2xmltest<br>> df1718c docs: reworked the policykit patch submitted by Patrick Dignan<br>> 5bc4307 docs: fix the xml validity errors regarding name and id<br>> 8ae354f build: avoid non-portable IPv6 struct member, for MacOS X<br>> 58ba49a virsh: change wexitstatus order to allow compilation on mac osx<br>> 63d1b07 libvirtd: improve the error message displayed on tls client <br>> auth failure<br>> 8a93daf maint: silence warning from libtool<br>> 38ba6e1 Rebuild network filter for UML guests on updates<br>> <br>> I'm not a git expert, it's just something I'm learning from necessity. :)<br>> <br>> Regards and best wishes,<br>> <br>> Justin Clift<br>> <br>> <br>> ------------------------------<br>> <br>> Message: 2<br>> Date: Fri, 17 Sep 2010 10:27:12 -0300<br>> From: daniel cabrera <logan@fedoraproject.org><br>> Subject: Re: Docs site<br>> To: For participants of the Documentation Project<br>> <docs@lists.fedoraproject.org><br>> Message-ID: <1284730032.27493.17.camel@ulysses><br>> Content-Type: text/plain; charset="utf-8"<br>> <br>> On Fri, 2010-09-17 at 08:24 +0200, Piotr Dr?g wrote:<br>> > 2010/9/17 daniel cabrera <logan@fedoraproject.org>:<br>> > > On Thu, 2010-09-16 at 21:59 -0500, Mike McGrath wrote:<br>> > >> can you revert it?<br>> > >><br>> > > I think so, but I'd like some guidance... I don't want to make things<br>> > > worse.<br>> > > I'm on the IRC.<br>> > ><br>> > <br>> > I'm very sorry, it appears I've noticed the problem and reverted this<br>> > commit before I've read your e-mails. I hope I didn't get in your way<br>> > or something.<br>> > <br>> > Anyway, reverting a bad commit is easy, basically it's "git revert<br>> > commit_hash". Commit hash can be obtained from some git command I<br>> > don't know or from my favorite gitweb. :)<br>> > <br>> > -- <br>> > Piotr Dr?g<br>> <br>> Well, I guess everything is back to normal.<br>> Nick and Piotr, thank you very much for helping me to clean up my mess.<br>> Now I know what was my mistake and it won't happen again.<br>> See you around, logan.<br>> -------------- next part --------------<br>> A non-text attachment was scrubbed...<br>> Name: not available<br>> Type: application/pgp-signature<br>> Size: 490 bytes<br>> Desc: This is a digitally signed message part<br>> Url : http://lists.fedoraproject.org/pipermail/docs/attachments/20100917/8e5f2a39/attachment-0001.bin <br>> <br>> ------------------------------<br>> <br>> Message: 3<br>> Date: Fri, 17 Sep 2010 13:13:45 -0500 (CDT)<br>> From: Mike McGrath <mmcgrath@redhat.com><br>> Subject: Re: Docs site<br>> To: For participants of the Documentation Project<br>> <docs@lists.fedoraproject.org><br>> Message-ID: <alpine.LFD.2.00.1009171313220.2351@laptop1.mmcgrath.net><br>> Content-Type: text/plain; charset="utf-8"<br>> <br>> On Fri, 17 Sep 2010, daniel cabrera wrote:<br>> <br>> > On Fri, 2010-09-17 at 08:24 +0200, Piotr Dr?g wrote:<br>> > > 2010/9/17 daniel cabrera <logan@fedoraproject.org>:<br>> > > > On Thu, 2010-09-16 at 21:59 -0500, Mike McGrath wrote:<br>> > > >> can you revert it?<br>> > > >><br>> > > > I think so, but I'd like some guidance... I don't want to make things<br>> > > > worse.<br>> > > > I'm on the IRC.<br>> > > ><br>> > ><br>> > > I'm very sorry, it appears I've noticed the problem and reverted this<br>> > > commit before I've read your e-mails. I hope I didn't get in your way<br>> > > or something.<br>> > ><br>> > > Anyway, reverting a bad commit is easy, basically it's "git revert<br>> > > commit_hash". Commit hash can be obtained from some git command I<br>> > > don't know or from my favorite gitweb. :)<br>> > ><br>> > > --<br>> > > Piotr Dr?g<br>> ><br>> > Well, I guess everything is back to normal.<br>> > Nick and Piotr, thank you very much for helping me to clean up my mess.<br>> > Now I know what was my mistake and it won't happen again.<br>> > See you around, logan.<br>> ><br>> <br>> I just realized I never sent a note to the list, yes everything is back to<br>> normal. Thanks to everyone for the quick response.<br>> <br>> -Mike<br>> <br>> ------------------------------<br>> <br>> Message: 4<br>> Date: Fri, 17 Sep 2010 13:32:46 -0700<br>> From: Karsten Wade <kwade@redhat.com><br>> Subject: Re: Fwd: SE Linux docs<br>> To: docs@lists.fedoraproject.org<br>> Message-ID: <20100917203246.GA31949@calliope.phig.org><br>> Content-Type: text/plain; charset="us-ascii"<br>> <br>> On Mon, Sep 13, 2010 at 08:00:18PM -0400, Paul Frields wrote:<br>> > Hello Docs team and Publican knowledge-meisters,<br>> > <br>> > I received this email from a contributor and tested his results. This<br>> > appears to be a valid bug. How can we properly link to the interior of<br>> > a document on the docs.fedoraproject.org site? All targets seem to<br>> > take one to the top of a document, which is not only unhelpful, but<br>> > breaks the simple principle of least surprise.<br>> <br>> We might also want to have SELinux Troubleshooter point to a wiki<br>> page, and we can update that wiki page with links to the latest guide<br>> or FAQ.<br>> <br>> It's a bit unclear to me where the bug lies. I see:<br>> <br>> 1. SELinux Troubleshooter is deep linking when maybe it should go to a<br>> wiki page.<br>> <br>> 2. The SELinux FAQ has a section without an ID tag.<br>> <br>> 3. The SELinux FAQ has a broken link to itself.<br>> <br>> - Karsten<br>> <br>> > Paul<br>> > <br>> > <br>> > ---------- Forwarded message ----------<br>> > From: Dan Haskell <geekus.org@gmail.com><br>> > Date: Mon, Sep 13, 2010 at 2:00 PM<br>> > Subject: SE Linux docs<br>> > <br>> > <br>> > Clicked on the link in the SELinux Security Alerts screen that says<br>> > "You can generate a local policy module to allow this access - see<br>> > FAQ" and it takes me to:<br>> > <br>> > http://docs.fedoraproject.org/en-US/Fedora/13/html/SELinux_FAQ/#id2961385<br>> > <br>> > Which is the top of the whole document. :(<br>> > <br>> > So, I find the link there that says "To see how to write a simple<br>> > policy module, check out Local Policy Customizations. " and it takes<br>> > me to:<br>> > <br>> > http://docs.fedoraproject.org/en-US/Fedora/13/html/SELinux_FAQ/index.html#faq-entry-local.te<br>> > <br>> > Which, again, is the top of the whole document. Sigh.<br>> > <br>> > Please don't respond with a link to the correct document. Someone<br>> > needs to fix this. People hate SELinux enough already...<br>> > <br>> > Dan<br>> > -- <br>> > docs mailing list<br>> > docs@lists.fedoraproject.org<br>> > To unsubscribe: <br>> > https://admin.fedoraproject.org/mailman/listinfo/docs<br>> <br>> -- <br>> name: Karsten 'quaid' Wade, Sr. Community Gardener<br>> team: Red Hat Community Architecture <br>> uri: http://TheOpenSourceWay.org/wiki<br>> gpg: AD0E0C41<br>> -------------- next part --------------<br>> A non-text attachment was scrubbed...<br>> Name: not available<br>> Type: application/pgp-signature<br>> Size: 189 bytes<br>> Desc: not available<br>> Url : http://lists.fedoraproject.org/pipermail/docs/attachments/20100917/9459ca0c/attachment-0001.bin <br>> <br>> ------------------------------<br>> <br>> Message: 5<br>> Date: Fri, 17 Sep 2010 17:21:03 -0400<br>> From: "John J. McDonough" <wb8rcr@arrl.net><br>> Subject: Re: Fwd: SE Linux docs<br>> To: For participants of the Documentation Project<br>> <docs@lists.fedoraproject.org><br>> Message-ID: <1284758463.7672.9.camel@Aidan><br>> Content-Type: text/plain; charset="UTF-8"<br>> <br>> On Fri, 2010-09-17 at 13:32 -0700, Karsten Wade wrote:<br>> > On Mon, Sep 13, 2010 at 08:00:18PM -0400, Paul Frields wrote:<br>> > > Hello Docs team and Publican knowledge-meisters,<br>> > > <br>> > > I received this email from a contributor and tested his results. This<br>> > > appears to be a valid bug. How can we properly link to the interior of<br>> > > a document on the docs.fedoraproject.org site? All targets seem to<br>> > > take one to the top of a document, which is not only unhelpful, but<br>> > > breaks the simple principle of least surprise.<br>> > <br>> > We might also want to have SELinux Troubleshooter point to a wiki<br>> > page, and we can update that wiki page with links to the latest guide<br>> > or FAQ.<br>> > <br>> > It's a bit unclear to me where the bug lies. I see:<br>> > <br>> > 1. SELinux Troubleshooter is deep linking when maybe it should go to a<br>> > wiki page.<br>> > <br>> > 2. The SELinux FAQ has a section without an ID tag.<br>> > <br>> > 3. The SELinux FAQ has a broken link to itself.<br>> > <br>> > - Karsten<br>> > <br>> > > Paul<br>> > > <br>> > > <br>> > > ---------- Forwarded message ----------<br>> > > From: Dan Haskell <geekus.org@gmail.com><br>> > > Date: Mon, Sep 13, 2010 at 2:00 PM<br>> > > Subject: SE Linux docs<br>> > > <br>> > > <br>> > > Clicked on the link in the SELinux Security Alerts screen that says<br>> > > "You can generate a local policy module to allow this access - see<br>> > > FAQ" and it takes me to:<br>> > > <br>> > > http://docs.fedoraproject.org/en-US/Fedora/13/html/SELinux_FAQ/#id2961385<br>> > > <br>> > > Which is the top of the whole document. :(<br>> > > <br>> > > So, I find the link there that says "To see how to write a simple<br>> > > policy module, check out Local Policy Customizations. " and it takes<br>> > > me to:<br>> > > <br>> > > http://docs.fedoraproject.org/en-US/Fedora/13/html/SELinux_FAQ/index.html#faq-entry-local.te<br>> > > <br>> > > Which, again, is the top of the whole document. Sigh.<br>> > > <br>> > > Please don't respond with a link to the correct document. Someone<br>> > > needs to fix this. People hate SELinux enough already...<br>> > > <br>> > > Dan<br>> > > -- <br>> <br>> This is a tad confusing because there are multiple things going on. We<br>> (relatively) recently reorganized docs.fp.o to support Publican<br>> publishing and managing the site with git. As a result, a lot of links<br>> in old documents were broken. Sometimes new documents simply replaced<br>> f12 with f13, which means even some new documents don't point to the<br>> right place. I believe the site essentially redirects 404's to the top<br>> of the site.<br>> <br>> However, this specific document has some rather peculiar behavior, which<br>> makes me wonder just how it was produced. Even the table of contents<br>> doesn't work reliably, something that is not evident on other documents.<br>> <br>> In addition, some things on docs.fp.o seem not quite right. We had an<br>> event last night where over 150,000 pages were committed and I'm not<br>> sure we have totally recovered from that event.<br>> <br>> But, I do think there is something peculiar about this particular<br>> document, and it might be helpful to rebuild and republish it.<br>> <br>> Since you are the author, did you test it before publishing? Does this<br>> behavior exist on a local copy? Is the copy on docs.fp.o actually the<br>> same as the one you committed?<br>> <br>> --McD<br>> <br>> <br>> <br>> <br>> ------------------------------<br>> <br>> Message: 6<br>> Date: Fri, 17 Sep 2010 17:39:50 -0400<br>> From: "Paul W. Frields" <stickster@gmail.com><br>> Subject: Re: Fwd: SE Linux docs<br>> To: docs@lists.fedoraproject.org<br>> Message-ID: <20100917213950.GQ3855@victoria.internal.frields.org><br>> Content-Type: text/plain; charset=us-ascii<br>> <br>> On Fri, Sep 17, 2010 at 01:32:46PM -0700, Karsten Wade wrote:<br>> > On Mon, Sep 13, 2010 at 08:00:18PM -0400, Paul Frields wrote:<br>> > > Hello Docs team and Publican knowledge-meisters,<br>> > > <br>> > > I received this email from a contributor and tested his results. This<br>> > > appears to be a valid bug. How can we properly link to the interior of<br>> > > a document on the docs.fedoraproject.org site? All targets seem to<br>> > > take one to the top of a document, which is not only unhelpful, but<br>> > > breaks the simple principle of least surprise.<br>> > <br>> > We might also want to have SELinux Troubleshooter point to a wiki<br>> > page, and we can update that wiki page with links to the latest guide<br>> > or FAQ.<br>> > <br>> > It's a bit unclear to me where the bug lies. I see:<br>> > <br>> > 1. SELinux Troubleshooter is deep linking when maybe it should go to a<br>> > wiki page.<br>> > <br>> > 2. The SELinux FAQ has a section without an ID tag.<br>> > <br>> > 3. The SELinux FAQ has a broken link to itself.<br>> <br>> Possibly:<br>> <br>> 4. The subject matter is now explored so widely that the SELinux Guide<br>> is where we should collect all the material, and then link to the<br>> appropriate section which has an relatively unchanging URL.<br>> <br>> -- <br>> Paul W. Frields http://paul.frields.org/<br>> gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717<br>> http://redhat.com/ - - - - http://pfrields.fedorapeople.org/<br>> Where open source multiplies: http://opensource.com<br>> <br>> <br>> ------------------------------<br>> <br>> --<br>> docs mailing list<br>> docs@lists.fedoraproject.org<br>> https://admin.fedoraproject.org/mailman/listinfo/docs<br>> <br>> End of docs Digest, Vol 79, Issue 15<br>> ************************************<br></div> </body>
</html>