On Thu, 12 Dec 2013, Taras Korenko wrote:
On Thu, Dec 12, 2013 at 08:31:58AM -0700, Warren Block wrote:
On Thu, 12 Dec 2013, Taras Korenko wrote:
...
Could anyone review that?
...
...
@@ -637,7 +639,7 @@
&os; provides a variety of different commands to manage
On Sat, 14 Dec 2013, Steven Kreuzer wrote:
Hello-
If someone has some free time, would you be able to review this patch for me?
http://clamps.exit2shell.com/~skreuzer/patches/nve-counter.patch
It adds manual page entities for nvme(4), nvd(4), nvmecontrol(8) and
counter(9) which are new for Fr
Most obsessive/pedantic/picky PR of the year goes to me, with:
The man page for diff3(1) refers to 'info diff' instead of
'info diff3'
How-To-Repeat:
% man diff3
Compare the similarity of the end of this page with the end of the
'man diff' page.
Both refer to 'info diff' for more informati
The following reply was made to PR docs/184791; it has been noted by GNATS.
From: Warren Block
To: Jamie Landeg Jones
Cc: freebsd-gnats-sub...@freebsd.org, freebsd-doc@FreeBSD.org
Subject: Re: docs/184791: [patch] man page for 'diff3' references 'info diff'
instead of &#
On Tue, 17 Dec 2013, Jamie Landeg Jones wrote:
Agreed. However, this is "contrib" software from an external source,
and we generally prefer to get them patched upstream to avoid having to
maintain local patches. I think this is the project page:
http://www.gnu.org/software/diffutils/
It's not
The following reply was made to PR docs/184791; it has been noted by GNATS.
From: Warren Block
To: Jamie Landeg Jones
Cc: freebsd-gnats-sub...@freebsd.org, freebsd-doc@freebsd.org
Subject: Re: docs/184791: [patch] man page for 'diff3' references 'info diff'
instead of &#
In recent discussion on the -current mailing list, it was pointed out
that using lagg(4) for failover from wired to wireless networking is not
fully functional:
http://lists.freebsd.org/pipermail/freebsd-current/2013-December/047259.html
I know that Dru told me she'd always had problems with it
eywords:
>Date-Required:
>Class: doc-bug
>Submitter-Id: current-users
>Arrival-Date: Fri Dec 20 18:00:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator: Warren Block
>Release:10-STABLE
>Organization:
>Environment:
FreeBSD lightning 10.
The following reply was made to PR docs/185041; it has been noted by GNATS.
From: Warren Block
To: bug-follo...@freebsd.org, wbl...@freebsd.org
Cc:
Subject: Re: docs/185041: HTML rendering: replaceable elements are not
distinguished
Date: Fri, 20 Dec 2013 18:13:20 -0700 (MST)
Further info
On Fri, 3 Jan 2014, Jamie Landeg Jones wrote:
The man page for diff3(1) refers to 'info diff' instead of
'info diff3'
Thanks guys for your responses and help. I followed this up,
and it's been corrected in the latest version of diffutils.
How readily would Freebsd accept a port/merge/update o
The following reply was made to PR docs/184791; it has been noted by GNATS.
From: Warren Block
To: Jamie Landeg Jones
Cc: r...@ringlet.net, freebsd-gnats-sub...@freebsd.org,
freebsd-doc@FreeBSD.org
Subject: Re: docs/184791: [patch] man page for 'diff3' references 'info di
On Sun, 5 Jan 2014, Jamie Landeg Jones wrote:
Normally, it would come in when the local diffutils are updated to the
latest upstream version. I don't know when that will be or who would
handle it.
Yeah, that's what I meant. I'd be willing to have a look at it myself
if I knew they were open
On Sun, 12 Jan 2014, free...@nagilum.org wrote:
as Edwin pointed out to me recently
(http://www.freebsd.org/cgi/query-pr.cgi?pr=185680) the "Class:" of a new
port should be "change-request". It would be good to mention this on
"porters-handbook/porting-submitting.html".
But it already says t
On Sun, 12 Jan 2014, Warren Block wrote:
On Sun, 12 Jan 2014, free...@nagilum.org wrote:
as Edwin pointed out to me recently
(http://www.freebsd.org/cgi/query-pr.cgi?pr=185680) the "Class:" of a new
port should be "change-request". It would be good to mention this o
On Tue, 14 Jan 2014, Sergio Andrés Gómez del Real wrote:
I started studying the FreeBSD boot system and found that the documentation
is limited and, in some cases, not true; for example it doesn't address
appropriately the boot1 stage, stating erroneously that it is limited for
booting with a fl
On Wed, 15 Jan 2014, Paul Hoffman wrote:
It now seems like the normal workflow for people who want to use "pkg" is:
- Hear about pkg
- Find the information in the Handbook at
http://www.freebsd.org/doc/handbook/pkgng-intro.html
- Install following those directions
- Get mysterious messages whi
On Wed, 15 Jan 2014, Paul Hoffman wrote:
On Jan 15, 2014, at 12:24 PM, Warren Block wrote:
The mysterious messages were due to a a default configuration file which I
think is not installed with the latest version of pkg.
It was in the "pkg" I got this morning, which reminded
On Mon, 20 Jan 2014, Charlie wrote:
Greetings all,
First, I want to say "hi," and that I am excited to be part of the FreeBSD
community. I am not much of a developer, but I have been wanting to help out
with the project for a few months now, so I figured I could probably try
helping with do
On Tue, 21 Jan 2014, Gábor Kövesdán wrote:
in the pdf version of the documentation we have rendered line wrap indicators
that show the reader when a long line has been wrapped into multiple lines so
that it can be rendered. In the HTML version we have scrollable
programlistings, which is not s
On Fri, 17 Jan 2014, Alexey Dokuchaev wrote:
On Fri, Jan 17, 2014 at 10:50:21AM +0100, Pietro Cerutti wrote:
On 2014-Jan-17, 09:35, Alexey Dokuchaev wrote:
If possible, particular make(1) implementation should not be referenced in
port's Makefile. If you need to call "correct" make(1), use ${
On Fri, 24 Jan 2014, Warren Block wrote:
On Fri, 17 Jan 2014, Alexey Dokuchaev wrote:
Please consider attached patch. It is not a polished gem, and most likely
would need a review and wordsmithing from doc@ guys.
While here I've also standardized the spelling of "okay", and
On Mon, 27 Jan 2014, Alexey Dokuchaev wrote:
On Sat, Jan 25, 2014 at 05:38:11PM -0700, Warren Block wrote:
I would like to be more specific in this part:
Quite often, a specific implementation is required, like GNU make, or
legacy FreeBSD make.
I think that should say:
Quite often, a
Based on a discussion on IRC, we'd like to ask for comments from people
who have authored or contributed to documentation.
At present, authors add their name and sometimes a description of their
work like "Contributed by" or "Rewritten by".
These author attributions are often quickly outdated
The attached patch, created with the help of Allan Jude, tightens up the
spacing in HTML callout lists, making them easier to read.
After applying it, I did not see any problems with the callout lists in
the Handbook.
Unless problems are reported, I'll commit it in a day or two.Index: share/m
On Mon, 3 Feb 2014, Dru Lavigne wrote:
This section:
23.4. Updating the Documentation Set
really belongs (and is already mostly duplicated in):
http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/overview.html#overview-doc
Any objections to me doing the following?
1. remove "23.4. U
On Sun, 2 Feb 2014, Warren Block wrote:
The attached patch, created with the help of Allan Jude, tightens up the
spacing in HTML callout lists, making them easier to read.
After applying it, I did not see any problems with the callout lists in the
Handbook.
Unless problems are reported
On Mon, 3 Feb 2014, Warren Block wrote:
Building the Handbook copies doc/share/misc/docbook.css into the Handbook
directory. So patch the original, do a 'make clean' for the Handbook, then
refresh the browser to view the new version.
Which assumes you are looking at a local copy r
tions, suggestions and other kinds of reviewing are
welcome. Patches and pull requests are very welcome!
Many thanks to Warren Block for the initial review and many fixes.
One fix for the gptzfsboot man page would be to mention that
gptzfsboot is installed into a GPT partition of type freebsd-boot
On Tue, 4 Feb 2014, Taras Korenko wrote:
Good morning, doc@ folks.
The following notes were made while working on russian translation
of kernelconfig chapter. I hope some parts of the following diff
might be useful.
So, could anyone review that diff?
Notes below prefixed with "WB:".
Ind
On Tue, 4 Feb 2014, nemysis wrote:
Index: en_US.ISO8859-1/books/porters-handbook/book.xml
===
--- en_US.ISO8859-1/books/porters-handbook/book.xml (revision 43779)
+++ en_US.ISO8859-1/books/porters-handbook/book.xml (working
On Wed, 5 Feb 2014, Sergey Kandaurov wrote:
The rest looks good to me, given that you will split the changes into
markup and content changes :).
If you are talking about that whitespace change inside the
programlisting, that can be considered a content change because it will
be visible in th
Thanks to everyone for their kind thoughts!
___
freebsd-doc@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-doc
To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
On Sat, 8 Feb 2014, Tom Rhodes wrote:
Hi,
So - today I spent a few moments (and a few for loops) splitting
up the porters-handbook into several sections. Here is the WIP
patch:
http://people.freebsd.org/~trhodes/NEW-PH.diff
Please note it DOES NOT BUILD just yet. Before I actually go
throug
On Sun, 9 Feb 2014, Allan Jude wrote:
Attached find a giant white space patch, fixes every igor warning, and
updates a lot of markup (acronym, application, using option instead of
literal) etc.
Committed with a note about how it is not necessary to separate
whitespace and content patches on t
On Mon, 17 Feb 2014, Xin Li wrote:
(redirecting to freebsd-doc@)
Subject changed.
On 2/17/14, 7:10 PM, Warren Block wrote:
I'm sorry, these multiple whitespace changes were my fault due to
a mixup with Allan Jude's original patch. Normally, it would have
been a single
On Tue, 18 Feb 2014, Remko Lodder wrote:
My project at work is not able to keep up with the ?content spree? that Dru is
doing to make things better. Good work, but a drama for translation teams that
need to be in sync first (and with a train that moves so fast, it will remain
out of date).
May
On Tue, 18 Feb 2014, Benedict Reuschling wrote:
Another tool is textproc/po4a that Thomas Abthorpe showed me on one of
the hacker lounges two years ago in Canada. He set up a test project
for a translation into en_GB to see how these tools fit our toolchain.
He send me the following mini-howto,
On Thu, 20 Feb 2014, Hiroki Sato wrote:
Allan Jude wrote
in <5305a9a4.1010...@allanjude.com>:
fr> It also fixes a paragraph that someone else wrote, that Warren had
fr> pointed out made no sense.
fr>
fr> Also adds some missing tags, and replace all of the
fr> tags that are actually commands
On Thu, 20 Feb 2014, Allan Jude wrote:
I've quickly switch those back to
I used simple logic, if talking about a command in a paragraph, use
, when doing it in a use , as in a
paragraph it is usually never more than a subcommand like zfs
send
That's correct, IMO. Semantically, command tags
On Mon, 24 Feb 2014, Remko Lodder wrote:
On 24 Feb 2014, at 19:30, Allan Jude wrote:
The following reply was made to PR www/175685; it has been noted by GNATS.
From: Allan Jude
To: bug-follo...@freebsd.org
Cc:
Subject: Re: www/175685: HTTPS does not follow visitor among FreeBSD.org
sub-do
On Thu, 27 Feb 2014, Joe wrote:
Builds which do not have the -p suffix in their release string do not have a
patch level.
Or maybe it's more accurate to say "If your release string does not contain the -p suffix, your build is not from the patched security branch"?
??
I'm sure you know bett
On Fri, 28 Feb 2014, Jack-Benny Persson wrote:
Hi,
I'm just wondering what the correct way is to send updates and patches
to the FreeBSD Handbook? I've read (and heard) of both sending them to
this list as well as using send-pr. I was recommended to send them here
to the list so I've sent a sma
On Sun, 2 Mar 2014, Thomas Hoffmann wrote:
On Sat, Mar 1, 2014 at 4:10 PM, daniel dallmann wrote:
I was wondering if the output from top was displayed with two headers on
purpose?
http://www.za.freebsd.org/doc/handbook/basics-processes.html
I'm guessing yes. The first is without ZFS stats
On Sun, 2 Mar 2014, Warren Block wrote:
On Sun, 2 Mar 2014, Thomas Hoffmann wrote:
On Sat, Mar 1, 2014 at 4:10 PM, daniel dallmann
wrote:
I was wondering if the output from top was displayed with two headers on
purpose?
http://www.za.freebsd.org/doc/handbook/basics-processes.html
I&#
On Tue, 4 Mar 2014, James Riggs wrote:
looks like there is a small problem here
https://www.freebsd.org/doc/handbook/x-config.html
section 6.4.2
on the lines
hald_enable="YES"
dbus_enable="YES"
the underscores are not visible on my browser (chrome on windows)
not sure if this is an issue with
http://www.hemingwayapp.com/ shows an interesting way of examining and
making suggestions on improving text quality.
Ultimately, it would be really nice to see textproc/igor integrated with
an editor.
___
freebsd-doc@freebsd.org mailing list
http://l
On Sat, 8 Mar 2014, Julian Elischer wrote:
On 3/8/14, 5:26 AM, Eduardo Morras wrote:
On Sat, 8 Mar 2014 14:36:16 +0800
by wrote:
Hello,
I use FreeBSD 10.0 RELEASE now, and I just install the base system,
but I add doc when I install FreeBSD, so there are some docs in my
system, and they are
During the DocBook 5 conversion, some tags were lost from
the XML source.
I've written a script to help check which files contained replaceable
tags and show the counts before and after the conversion, along with the
current count.
Instructions and suggestions on using devel/diffuse to repl
eywords:
>Date-Required:
>Class: doc-bug
>Submitter-Id: current-users
>Arrival-Date: Thu Mar 13 00:40:00 UTC 2014
>Closed-Date:
>Last-Modified:
>Originator: Warren Block
>Release:10-IRRELEVANT
>Organization:
>Environment:
FreeBSD nomatter
The following reply was made to PR docs/187515; it has been noted by GNATS.
From: Warren Block
To: bug-follo...@freebsd.org, wbl...@freebsd.org
Cc:
Subject: Re: docs/187515: userinput inside screen elements is not rendered
differently
Date: Wed, 12 Mar 2014 18:50:48 -0600 (MDT)
elements
On Thu, 3 Apr 2014, Torbjorn Granlund wrote:
I notice that you seriously downplay the filesystem malfunctioning issue
of FreeBSD/i386 10.0 (and its many betas).
Do we? What should it say? Please be specific, preferably in the form
of a PR. Is this really a doc problem?
http://www.freebs
On Thu, 3 Apr 2014, Torbjorn Granlund wrote:
Warren Block writes:
Do we? What should it say? Please be specific, preferably in the
form of a PR. Is this really a doc problem?
Full disclosure. Don't downplay. Both the scope and the gravity of the
issue is grossly downplayed her
The existing Handbook printing chapter has many weaknesses:
It does not cover simple setup well.
It does not cover current devices well.
It uses some confusing terminology and shows examples for uncommon
situations.
I've complained about these problems before, but a few months ago, Dru
a
On Mon, 7 Apr 2014, Brad Davis wrote:
Hi Everyone,
I am slowly working on moderinzing the DNS chapter. One of the first
things I need to fix is to put all the BIND content into its own sub
section. If I do that, the indentation of almost the entire chapter will
need to shift in one level. So I
On Mon, 21 Apr 2014, Polytropon wrote:
On Mon, 21 Apr 2014 13:40:02 +0800, wipedrivepro wipedrivepro wrote:
eg in .doc or .pdf format of
https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/bsdinstall.html#bsdinstall-synopsis
it's hard to download it one by one
You can download the ful
On Mon, 26 May 2014, Ryan Stone wrote:
These patches either update existing manual pages or introduce new
ones to document the new PCI SR-IOV infrastructure. Any review of
this would be greatly appreciated, as I've never written manual pages
before so no doubt I've made silly mistakes. Thanks
On Mon, 26 May 2014, Ryan Stone wrote:
On Mon, May 26, 2014 at 10:27 PM, Warren Block wrote:
Have you tried phabricator.freebsd.org? It makes review of this type of
thing somewhat easier. (And I say that despite fighting with the user
interface today.)
As an example, here is a man page
For iovctl.8, I see is the use of "your". We try to avoid using "you"
and "your", which is an informal style:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/book.html#writing-style-tips
See the manual page for your PF driver for documentation of
configuration parameters that ar
The Committer's Guide has a confusing and difficult to follow set of
steps for new committers:
http://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/conventions.html
I propose this set of changes:
https://phabric.freebsd.org/D129
Rendered version:
http://www.wonkity.com/~wblock/c
On Sat, 31 May 2014, Warren Block wrote:
The Committer's Guide has a confusing and difficult to follow set of steps
for new committers:
http://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/conventions.html
New version: http://www.wonkity.com/~wblock/commi
On Mon, 9 Jun 2014, Sevan / Venture37 wrote:
On 08/06/2014 23:20, Mark Linimon wrote:
See "New Accounts" underhttps://wiki.freebsd.org/AboutWiki . That
should help.
Following the cookbook version I visit UserPreferences page, click "Create
New Page" and get "You are not allowed to edit thi
On Wed, 18 Jun 2014, Anders Jensen-Waud wrote:
Hello,
I am a long-time avid FreeBSD user (from memory since FreeBSD 4.0). I have for
very
long been interested in contributing back to the FreeBSD community.
I was wondering what the current needs are in terms of improving
documentation and gaps
The current CSS makes elements appear in bold text in
XHTML. For example:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/desktop-browsers.html
This repeated use of bold makes for uncomfortable and fatiguing reading.
Allan and I have searched for less severe forms of highlighting.
Erich Dollansky wrote:
I would keep it and I would keep it as bold. I would only recommend a
consequent use of it. Using bold helps to find important locations a
bit faster without reading the whole sentence.
...
The moment the highlighting will only be used for the application and
not for the
On Tue, 1 Jul 2014, Eitan Adler wrote:
Is there a way to signify good example code and bad example code?
For example the latter has a light red background, and clearly says
"don't do this" while the former has a light green background with a
big checkmark?
I don't know if we have a way to do
The phabricator instance has shown that some review can be done more
easily.
We've talked before about having periodic reviews of parts of the
documentation. It turns out that experts rarely read the docs on things
they know about, but are the ones that can produce very valuable
feedback.
On Sun, 6 Jul 2014, Adrian Chadd wrote:
I'm looking for some help to document the new RSS stuff.
I'm happy writing up some text documentation - shall I just email out
the bits here so I can get some help with markup and such?
Is this for a man page or book or article?
Mailing list threads ca
On Sun, 6 Jul 2014, Adrian Chadd wrote:
On 6 July 2014 12:46, Warren Block wrote:
On Sun, 6 Jul 2014, Adrian Chadd wrote:
I'm looking for some help to document the new RSS stuff.
I'm happy writing up some text documentation - shall I just email out
the bits here so I can get some
On Wed, 9 Jul 2014, Patrick Powell wrote:
I notice that Section 5.3 - Finding Software describes how to search for
software but there are a couple
of steps left out that might confuse a newbie.
...
Note: I think pkg is a GREAT improvement over the old pkg_add, but the
legacy documentation
On Thu, 10 Jul 2014, Gavin Atkinson wrote:
On Fri, 4 Jul 2014, Warren Block wrote:
We've talked before about having periodic reviews of parts of the
documentation. It turns out that experts rarely read the docs on things they
know about, but are the ones that can produce very val
On Fri, 25 Jul 2014, Craig Rodrigues wrote:
What I'd like to see is an article on freebsd.org either on the wiki
or in the handbook, which compares using apt, yum, rpm, whatever
to pkg. Is anyone interested in working on an article like this?
I don't have the bandwidth right now.
A person to
Draft version of an ezjail section for the Handbook Jails chapter:
http://www.wonkity.com/~wblock/jails/jails-ezjail.html
This includes a complete setup at the end for running BIND in a jail.
In addition to a complete jail example, it can also serve as an example
of how to set up BIND now that t
The existing /etc/motd breaks many of our document rules and has some
weird language constructs. The current version in HEAD:
http://svnweb.freebsd.org/base/head/etc/motd?view=co
Here is a rewrite. URLs are now the only thing on a line, instead of
inline and hard to locate. No contractions a
On Wed, 13 Aug 2014, Brooks Davis wrote:
On Wed, Aug 13, 2014 at 02:23:00PM -0600, Warren Block wrote:
The existing /etc/motd breaks many of our document rules and has some
weird language constructs. The current version in HEAD:
http://svnweb.freebsd.org/base/head/etc/motd?view=co
Here is a
On Mon, 4 Aug 2014, Warren Block wrote:
Draft version of an ezjail section for the Handbook Jails chapter:
http://www.wonkity.com/~wblock/jails/jails-ezjail.html
This includes a complete setup at the end for running BIND in a jail.
In addition to a complete jail example, it can also serve as
On Wed, 20 Aug 2014, John Baldwin wrote:
On Tuesday, August 19, 2014 6:01:54 pm Warren Block wrote:
On Mon, 4 Aug 2014, Warren Block wrote:
Draft version of an ezjail section for the Handbook Jails chapter:
http://www.wonkity.com/~wblock/jails/jails-ezjail.html
This includes a complete
On Wed, 20 Aug 2014, Warren Block wrote:
On Wed, 20 Aug 2014, John Baldwin wrote:
On Tuesday, August 19, 2014 6:01:54 pm Warren Block wrote:
On Mon, 4 Aug 2014, Warren Block wrote:
Draft version of an ezjail section for the Handbook Jails chapter:
http://www.wonkity.com/~wblock/jails/jails
On Mon, 25 Aug 2014, John Baldwin wrote:
On Wednesday, August 20, 2014 05:30:12 PM Warren Block wrote:
On Wed, 20 Aug 2014, Warren Block wrote:
On Wed, 20 Aug 2014, John Baldwin wrote:
On Tuesday, August 19, 2014 6:01:54 pm Warren Block wrote:
On Mon, 4 Aug 2014, Warren Block wrote:
Draft
On Thu, 14 Aug 2014, Benjamin Kaduk wrote:
I think that "Before seeking technical support, please use these
resources" remains an awkward phrase. The intent is to have the user
attempt to help themself before resorting to flailing and asking for help
on the internet, but not all of the listed r
On Fri, 5 Sep 2014, Warren Block wrote:
http://www.wonkity.com/~wblock/motd/motd
http://www.wonkity.com/~wblock/motd/motd.diff
And an experimental version that uses VT100/ANSI escape sequences to
remove the in-band quote marks that many readers will type, and
highlight those sections with
Based on feedback from -arch, now there is a version that uses only
harmless, inoffensive ASCII whitespace to delimit the commands:
http://www.wonkity.com/~wblock/motd/motd.whitespace
___
freebsd-doc@freebsd.org mailing list
http://lists.freebsd.org/ma
On Sun, 7 Sep 2014, Royce Williams wrote:
On Sun, Sep 7, 2014 at 5:49 AM, Warren Block wrote:
Based on feedback from -arch, now there is a version that uses only harmless,
inoffensive ASCII whitespace to delimit the commands:
http://www.wonkity.com/~wblock/motd/motd.whitespace
Not to
On Mon, 8 Sep 2014, Benjamin Kaduk wrote:
On Fri, 5 Sep 2014, Warren Block wrote:
Agreed. Updated, shorter version:
http://www.wonkity.com/~wblock/motd/motd
http://www.wonkity.com/~wblock/motd/motd.diff
% o Documents installed with the system are in /usr/local/share/doc/freebsd.
That
On Tue, 23 Sep 2014, Mark Corbett Wilson wrote:
On the FreeBSD Handbook Preface page (
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/book-preface.html)
under Typographic Conventions, shouldn't the *Bold* sentence read; "A *bold*
font is used for applications, commands, and keys."?
On Tue, 30 Sep 2014, Joe Marcus Clarke wrote:
Can someone with a doc bit look this patch over and commit it if they like
it? We had a change on our SVN server. Thanks.
Done. Thanks!
___
freebsd-doc@freebsd.org mailing list
http://lists.freebsd.org
On Wed, 1 Oct 2014, Allan Jude wrote:
I was under the impression svnlite was slated to go away.
Do we have an actual plan here, to keep it or kill it for 11?
As far as documentation is concerned, remember that svnlite is not
present before 10.x.
To my knowledge, svnlite's presence or futur
On Tue, 7 Oct 2014, Jason Helfman wrote:
Has anyone had time to look at this diff I sent in for GNOME, as well?
Additionally,
I do not know if parts of this diff were committed.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=179246
I don't recall seeing this before. At first glance, it
On Wed, 22 Oct 2014, Daniel Schuler wrote:
By the way, I?m currently getting into FreeBSD (from a long Linux
background), and am really enjoying it. I wish I?d started working
with FreeBSD sooner. If you could point me to an active community or
other resource where I could contribute in some w
On Mon, 3 Nov 2014, Wesley Ellis wrote:
I was reading through the Handbook in preparation to install and found that
the named(8) link returned no entries.
This can be found at:
https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/dirstructure.html
The link in question is:
http://www.Free
On Thu, 6 Nov 2014, Waldemar Antonik wrote:
hi,
i still haven't got any reply from you.
can you add me to the distribution list of people who translate FreeBSD
documentation from English to Polish. please also contact me with the
Polish Translation Project, as I was unsuccessful.
My apologies
On Sun, 23 Nov 2014, Remko Lodder wrote:
On 23 Nov 2014, at 20:10, Baptiste Daroussin wrote:
Hi all,
I would like to move the troff documentation which is not very useful anymore on
a recent FreeBSD system but still part of history into the doc repository, a
dedicated branch will probably fit
A new automated test of the documentation is available through the
FreeBSD testing project. See the results at:
https://jenkins.freebsd.org/job/FreeBSD_Doc-igor/
Click "Checkstyle Warnings" at the upper left to see a list of all
warnings by file. Click on a file and the Details tab to see th
On Sun, 30 Nov 2014, Benedict Reuschling wrote:
Am 30.11.14 um 18:42 schrieb Warren Block:
A new automated test of the documentation is available through the
FreeBSD testing project. See the results at:
https://jenkins.freebsd.org/job/FreeBSD_Doc-igor/
Click "Checkstyle Warnings&qu
On Tue, 2 Dec 2014, bu...@jameswhitby.org wrote:
At the bottom of section 31.8.2. Configuring the DHCP Server, just above
section 31.8.3. Debugging PXE Problems, the text reads:
Once the edits are saved, enable NFS at boot time by adding the following
line to /etc/rc.conf:
dhcpd_enable="YES"
A new mailing list, freebsd-translators@, has been set up to discuss
translation tools and processes. Everyone with any interest in
translations is encouraged to subscribe:
https://lists.freebsd.org/mailman/listinfo/freebsd-translators
Description:
A discussion list where translators of FreeBSD
On Sat, 27 Dec 2014, Chris Van Steenlandt wrote:
Hello,
if I'm posting this in the wrong mailing list, please forward this.
During a fresh install of 10.1, I wanted to consult the man page of pkg from
the FreeBSD web site;
There I was directed to pkg section 7 man page.
That is the "stub"
On Tue, 10 Feb 2015, R0B_ROD wrote:
Hey everyone.
I want to help with documentation and code (in the far future).
For a start, please look at the FDP Primer:
https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/
That describes how the existing documentation is marked up and built,
an
On Tue, 17 Mar 2015, Raphael Abreu wrote:
Hello everyone,
This is the first time I am sumbitting an e-mail to this list so sorry if I
break any protocols.
I would like to propose an improvement to the LOGGER(1) entry:
https://www.freebsd.org/cgi/man.cgi?query=logger%281%29
Where it reads:
*
On Fri, 3 Apr 2015, Benjamin Kaduk wrote:
On Thu, 2 Apr 2015, Kaio Rafael wrote:
Hello,
I am following Chapter 6. The X Window System [1] to install Xorg into my box.
I have installed the xorg package with "pkg install xorg" as the
handbook explains, but HAL service procedure is giving error
On Wed, 25 Mar 2015, In-Ho Yi via freebsd-doc wrote:
Hi all,
I've been looking through project ideas as I want to start participating in
FreeBSD development. I found the export to EPUB idea, and I thought this
would be a good project to take.
I wonder if anyone has started working on this proj
101 - 200 of 270 matches
Mail list logo
