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