[Bug 253453] Contemporary IPv6 howto for handbook
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253453 Bug ID: 253453 Summary: Contemporary IPv6 howto for handbook Product: Documentation Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Documentation Assignee: d...@freebsd.org Reporter: p...@freebsd.org Created attachment 222384 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=222384&action=edit Raw text about native IPv6 setup The IPv6 stuff in the handbook is no help in setting up an actual IPv6 connection to an ISP supporting that. Attached some text describing what I ended up doing. It would be prudent to have people with /etc/rc.d and IPv6 clue review it, because I have neither. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
[Bug 253453] Contemporary IPv6 howto for handbook
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253453 Daniel Ebdrup Jensen changed: What|Removed |Added CC||debd...@freebsd.org --- Comment #1 from Daniel Ebdrup Jensen --- Is there a reason why you're submitting a plaintext file over putting a review on Phabricator? I'll be happy to review and approve if you wanna write it up. The relevant file is doc/documentation/content/en/books/handbook/config/_index.adoc on line 321 starting with [[config-network-setup]] AsciiDoctor is almost the same as plaintext, there's just a tiny bit of formatting that should be self-explanatory if you reference the examples in that section of the file. Everything needed is mentioned on https://docs.freebsd.org/en/books/fdp-primer/#overview-quick-start -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: Regarding AsciiDoctor and long lines
Le 10.02.2021 17:03, Daniel Ebdrup Jensen a écrit : > Yeah, I'm perfectly fine with doing it like how manual pages work, ie. > the one-sentence-per-line workflow, if I understand it. > One sentence per line makes the read of diff/commit logs really difficult. I gave up reading the commit logs because of that. It's really a pain to find what changed without even talking about the edition of a long non-wrapped line in an editor. Some languages are very verbose, so we would end with very long lines. For a such change seems so backward. > I'll be re-working the handbook/x11 chapter to that at some point. :) > Please don't. -- Marc signature.asc Description: PGP signature
[Bug 253453] Contemporary IPv6 howto for handbook
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253453 --- Comment #2 from Poul-Henning Kamp --- To be brutally honest: If I put that on my TODO list, I'll never get around to it. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
[Bug 253456] Fix typo in the FAQ
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253456 Bug ID: 253456 Summary: Fix typo in the FAQ Product: Documentation Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Documentation Assignee: d...@freebsd.org Reporter: c...@submonkey.net Created attachment 222389 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=222389&action=edit Patch to correct spelling error Spelling error of "without" -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: Regarding AsciiDoctor and long lines
On Fri, 12 Feb 2021 at 13:45, Marc Fonvieille wrote: > Le 10.02.2021 17:03, Daniel Ebdrup Jensen a écrit : > > Yeah, I'm perfectly fine with doing it like how manual pages work, ie. > > the one-sentence-per-line workflow, if I understand it. > > > > One sentence per line makes the read of diff/commit logs really > difficult. I gave up reading the commit logs because of that. > It's really a pain to find what changed without even talking about the > edition of a long non-wrapped line in an editor. > Some languages are very verbose, so we would end with very long lines. > For a such change seems so backward. > > > I'll be re-working the handbook/x11 chapter to that at some point. :) > > > > Please don't. > > -- > Marc > Hi, I know that this approach it’s causing some confusion with the diffs tools. But instead of using a different way that recommended from the AsciiDoctor team I think we should try to focus on getting a solution in the diff tools. Maybe we can talk with the AsciiDoctor team. Bye. ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
[Bug 253458] Typos in handbook
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253458 Bug ID: 253458 Summary: Typos in handbook Product: Documentation Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Documentation Assignee: d...@freebsd.org Reporter: c...@submonkey.net Created attachment 222391 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=222391&action=edit patch for typos. Fix some minor typos in the handbook, one of which leads to a non-working example. "ApacheHTTPD" -> "Apache HTTPD" theDNS -> "the DNS" lapd_enable -> slapd_enable -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
[Bug 253453] Contemporary IPv6 howto for handbook
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253453 Daniel Ebdrup Jensen changed: What|Removed |Added Assignee|d...@freebsd.org |debd...@freebsd.org Status|New |In Progress --- Comment #3 from Daniel Ebdrup Jensen --- Maybe it'll do better on mine. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: Regarding AsciiDoctor and long lines
On Fri, Feb 12, 2021 at 03:09:35PM +0100, Sergio Carlavilla wrote: On Fri, 12 Feb 2021 at 13:45, Marc Fonvieille wrote: Le 10.02.2021 17:03, Daniel Ebdrup Jensen a écrit : > Yeah, I'm perfectly fine with doing it like how manual pages work, ie. > the one-sentence-per-line workflow, if I understand it. > One sentence per line makes the read of diff/commit logs really difficult. I gave up reading the commit logs because of that. It's really a pain to find what changed without even talking about the edition of a long non-wrapped line in an editor. Some languages are very verbose, so we would end with very long lines. For a such change seems so backward. > I'll be re-working the handbook/x11 chapter to that at some point. :) > Please don't. -- Marc Hi, I know that this approach it’s causing some confusion with the diffs tools. But instead of using a different way that recommended from the AsciiDoctor team I think we should try to focus on getting a solution in the diff tools. Maybe we can talk with the AsciiDoctor team. Bye. Hi folks, Marc does have a point, which I think is quite valid. A lot of people do reviews of code in the email they're sent, where - at least for the commits, it's inlined - and pursuant to discussions about this elsewhere, that doesn't seem likely to be changing any time soon. If diffs were attachments with the text/x-patch or text/x-diff mime-type, it'd be up to peoples MUA and possibly their .mailcap as to how it should be opened, but that's not something that's doable with the current setup. So I do think wrapping to 72 columns is the better option here, if we want to retain the broadest review possibilities. Yours, Daniel Ebdrup Jensen signature.asc Description: PGP signature
[Bug 253456] Fix typo in the FAQ
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253456 Gordon Bergling changed: What|Removed |Added Status|New |In Progress CC||g...@freebsd.org Keywords||patch Assignee|d...@freebsd.org |g...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
[Bug 253458] Typos in handbook
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253458 Gordon Bergling changed: What|Removed |Added Status|New |In Progress Assignee|d...@freebsd.org |g...@freebsd.org CC||g...@freebsd.org Keywords||patch -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: Regarding AsciiDoctor and long lines
On Fri, 12 Feb 2021 at 18:09, Daniel Ebdrup Jensen wrote: > On Fri, Feb 12, 2021 at 03:09:35PM +0100, Sergio Carlavilla wrote: > >On Fri, 12 Feb 2021 at 13:45, Marc Fonvieille > wrote: > > > >> Le 10.02.2021 17:03, Daniel Ebdrup Jensen a écrit : > >> > Yeah, I'm perfectly fine with doing it like how manual pages work, ie. > >> > the one-sentence-per-line workflow, if I understand it. > >> > > >> > >> One sentence per line makes the read of diff/commit logs really > >> difficult. I gave up reading the commit logs because of that. > >> It's really a pain to find what changed without even talking about the > >> edition of a long non-wrapped line in an editor. > >> Some languages are very verbose, so we would end with very long lines. > >> For a such change seems so backward. > >> > >> > I'll be re-working the handbook/x11 chapter to that at some point. :) > >> > > >> > >> Please don't. > >> > >> -- > >> Marc > >> > >Hi, > > > >I know that this approach it’s causing some confusion with the diffs > tools. > >But instead of using a different way that recommended from the AsciiDoctor > >team I think we should try to focus on getting a solution in the diff > tools. > > > >Maybe we can talk with the AsciiDoctor team. > > > >Bye. > > Hi folks, > > Marc does have a point, which I think is quite valid. A lot of people do > reviews of code in the email they're sent, where - at least for the > commits, it's inlined - and pursuant to discussions about this > elsewhere, that doesn't seem likely to be changing any time soon. > > If diffs were attachments with the text/x-patch or text/x-diff > mime-type, it'd be up to peoples MUA and possibly their .mailcap as to > how it should be opened, but that's not something that's doable with the > current setup. > > So I do think wrapping to 72 columns is the better option here, if we > want to retain the broadest review possibilities. > > Yours, > Daniel Ebdrup Jensen > Hi, Ok, if we use this approach. What are we gonna do with: Headings Unordered list Ordered list Images Include macro AsciiDoc variables Custom macros And I need to test classes and links. Bye. ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: Regarding AsciiDoctor and long lines
On Fri, Feb 12, 2021 at 06:16:30PM +0100, Sergio Carlavilla wrote: On Fri, 12 Feb 2021 at 18:09, Daniel Ebdrup Jensen wrote: On Fri, Feb 12, 2021 at 03:09:35PM +0100, Sergio Carlavilla wrote: >On Fri, 12 Feb 2021 at 13:45, Marc Fonvieille wrote: > >> Le 10.02.2021 17:03, Daniel Ebdrup Jensen a écrit : >> > Yeah, I'm perfectly fine with doing it like how manual pages work, ie. >> > the one-sentence-per-line workflow, if I understand it. >> > >> >> One sentence per line makes the read of diff/commit logs really >> difficult. I gave up reading the commit logs because of that. >> It's really a pain to find what changed without even talking about the >> edition of a long non-wrapped line in an editor. >> Some languages are very verbose, so we would end with very long lines. >> For a such change seems so backward. >> >> > I'll be re-working the handbook/x11 chapter to that at some point. :) >> > >> >> Please don't. >> >> -- >> Marc >> >Hi, > >I know that this approach it’s causing some confusion with the diffs tools. >But instead of using a different way that recommended from the AsciiDoctor >team I think we should try to focus on getting a solution in the diff tools. > >Maybe we can talk with the AsciiDoctor team. > >Bye. Hi folks, Marc does have a point, which I think is quite valid. A lot of people do reviews of code in the email they're sent, where - at least for the commits, it's inlined - and pursuant to discussions about this elsewhere, that doesn't seem likely to be changing any time soon. If diffs were attachments with the text/x-patch or text/x-diff mime-type, it'd be up to peoples MUA and possibly their .mailcap as to how it should be opened, but that's not something that's doable with the current setup. So I do think wrapping to 72 columns is the better option here, if we want to retain the broadest review possibilities. Yours, Daniel Ebdrup Jensen Hi, Ok, if we use this approach. What are we gonna do with: Headings Unordered list Ordered list Images Include macro AsciiDoc variables Custom macros And I need to test classes and links. Bye. Hi folks, That's what we, in the business, call a good question. Won't the + syntax work for all of those markups? Yours, Daniel Ebdrup Jensen P.S. The business in question is the one for people with just a tiny clue stick. ;) signature.asc Description: PGP signature
Re: Regarding AsciiDoctor and long lines
On Fri, 12 Feb 2021 at 18:16, Sergio Carlavilla wrote: > On Fri, 12 Feb 2021 at 18:09, Daniel Ebdrup Jensen > wrote: > >> On Fri, Feb 12, 2021 at 03:09:35PM +0100, Sergio Carlavilla wrote: >> >On Fri, 12 Feb 2021 at 13:45, Marc Fonvieille >> wrote: >> > >> >> Le 10.02.2021 17:03, Daniel Ebdrup Jensen a écrit : >> >> > Yeah, I'm perfectly fine with doing it like how manual pages work, >> ie. >> >> > the one-sentence-per-line workflow, if I understand it. >> >> > >> >> >> >> One sentence per line makes the read of diff/commit logs really >> >> difficult. I gave up reading the commit logs because of that. >> >> It's really a pain to find what changed without even talking about the >> >> edition of a long non-wrapped line in an editor. >> >> Some languages are very verbose, so we would end with very long lines. >> >> For a such change seems so backward. >> >> >> >> > I'll be re-working the handbook/x11 chapter to that at some point. :) >> >> > >> >> >> >> Please don't. >> >> >> >> -- >> >> Marc >> >> >> >Hi, >> > >> >I know that this approach it’s causing some confusion with the diffs >> tools. >> >But instead of using a different way that recommended from the >> AsciiDoctor >> >team I think we should try to focus on getting a solution in the diff >> tools. >> > >> >Maybe we can talk with the AsciiDoctor team. >> > >> >Bye. >> >> Hi folks, >> >> Marc does have a point, which I think is quite valid. A lot of people do >> reviews of code in the email they're sent, where - at least for the >> commits, it's inlined - and pursuant to discussions about this >> elsewhere, that doesn't seem likely to be changing any time soon. >> >> If diffs were attachments with the text/x-patch or text/x-diff >> mime-type, it'd be up to peoples MUA and possibly their .mailcap as to >> how it should be opened, but that's not something that's doable with the >> current setup. >> >> So I do think wrapping to 72 columns is the better option here, if we >> want to retain the broadest review possibilities. >> >> Yours, >> Daniel Ebdrup Jensen >> > Hi, > > Ok, if we use this approach. > > What are we gonna do with: > > Headings > Unordered list > Ordered list > Images > Include macro > AsciiDoc variables > Custom macros > > And I need to test classes and links. > > Bye. > > Hi, I think the doceng team should pronounce about this. IMHO, use the 72 characters per line would be a problem in the future. Bye. ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: Regarding AsciiDoctor and long lines
On Fri, 12 Feb 2021 at 18:23, Daniel Ebdrup Jensen wrote: > On Fri, Feb 12, 2021 at 06:16:30PM +0100, Sergio Carlavilla wrote: > >On Fri, 12 Feb 2021 at 18:09, Daniel Ebdrup Jensen > >wrote: > > > >> On Fri, Feb 12, 2021 at 03:09:35PM +0100, Sergio Carlavilla wrote: > >> >On Fri, 12 Feb 2021 at 13:45, Marc Fonvieille > >> wrote: > >> > > >> >> Le 10.02.2021 17:03, Daniel Ebdrup Jensen a écrit : > >> >> > Yeah, I'm perfectly fine with doing it like how manual pages work, > ie. > >> >> > the one-sentence-per-line workflow, if I understand it. > >> >> > > >> >> > >> >> One sentence per line makes the read of diff/commit logs really > >> >> difficult. I gave up reading the commit logs because of that. > >> >> It's really a pain to find what changed without even talking about > the > >> >> edition of a long non-wrapped line in an editor. > >> >> Some languages are very verbose, so we would end with very long > lines. > >> >> For a such change seems so backward. > >> >> > >> >> > I'll be re-working the handbook/x11 chapter to that at some point. > :) > >> >> > > >> >> > >> >> Please don't. > >> >> > >> >> -- > >> >> Marc > >> >> > >> >Hi, > >> > > >> >I know that this approach it’s causing some confusion with the diffs > >> tools. > >> >But instead of using a different way that recommended from the > AsciiDoctor > >> >team I think we should try to focus on getting a solution in the diff > >> tools. > >> > > >> >Maybe we can talk with the AsciiDoctor team. > >> > > >> >Bye. > >> > >> Hi folks, > >> > >> Marc does have a point, which I think is quite valid. A lot of people do > >> reviews of code in the email they're sent, where - at least for the > >> commits, it's inlined - and pursuant to discussions about this > >> elsewhere, that doesn't seem likely to be changing any time soon. > >> > >> If diffs were attachments with the text/x-patch or text/x-diff > >> mime-type, it'd be up to peoples MUA and possibly their .mailcap as to > >> how it should be opened, but that's not something that's doable with the > >> current setup. > >> > >> So I do think wrapping to 72 columns is the better option here, if we > >> want to retain the broadest review possibilities. > >> > >> Yours, > >> Daniel Ebdrup Jensen > >> > >Hi, > > > >Ok, if we use this approach. > > > >What are we gonna do with: > > > >Headings > >Unordered list > >Ordered list > >Images > >Include macro > >AsciiDoc variables > >Custom macros > > > >And I need to test classes and links. > > > >Bye. > > Hi folks, > > That's what we, in the business, call a good question. > > Won't the + syntax work for all of those markups? > > Yours, > Daniel Ebdrup Jensen > > P.S. The business in question is the one for people with just a tiny > clue stick. ;) > Hi, No, the + character is only for paragraphs. Bye. ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
[Bug 253467] FDP changes
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253467 Bug ID: 253467 Summary: FDP changes Product: Documentation Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Documentation Assignee: d...@freebsd.org Reporter: c...@submonkey.net Created attachment 222396 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=222396&action=edit biggish patch Correct some grammar, some factual information and a misrepresentation of that the "word list" is. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
[Bug 253467] FDP changes
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253467 Daniel Ebdrup Jensen changed: What|Removed |Added CC||debd...@freebsd.org Assignee|d...@freebsd.org |debd...@freebsd.org Status|New |Open --- Comment #1 from Daniel Ebdrup Jensen --- Yoink. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
[Bug 253470] documentation/content/en/books/fdp-primer/tools/chapter.adoc: Fix package name
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253470
Bug ID: 253470
Summary: documentation/content/en/books/fdp-primer/tools/chapte
r.adoc: Fix package name
Product: Documentation
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Documentation
Assignee: d...@freebsd.org
Reporter: y...@utahime.org
Created attachment 222398
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=222398&action=edit
Patch file
As the package name 'hugo' refers to 'emulators/hugo', PC Engine (TurboGrafx
16) emulator. 'Hugo' that is required by new framework is 'gohugo'
('www/gohugo'). Similarly package name of Asciidoctor is 'rubygem-asciidoctor'.
Therefore fix package names so they refer to proper ones.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-doc@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-doc
To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
[Bug 253470] documentation/content/en/books/fdp-primer/tools/chapter.adoc: Fix package name
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253470 Daniel Ebdrup Jensen changed: What|Removed |Added Assignee|d...@freebsd.org |debd...@freebsd.org Status|New |Open CC||debd...@freebsd.org --- Comment #1 from Daniel Ebdrup Jensen --- I'll take this. Are you okay with being credited via --author="Yasuhiro Kimura " ? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
