Re: [LFS Trac] #5808: alignment/spacing - lfs - r12.4-33-systemd

"LFS Trac" ([email protected] via lfs-book Mailing List) <[email protected]>
Newsgroups gmane.linux.lfs.book
Message-ID <[email protected]>
#5808: alignment/spacing - lfs - r12.4-33-systemd
---------------------------+-----------------------
 Reporter:  rhubarbpieguy  |       Owner:  lfs-book
     Type:  defect         |      Status:  closed
 Priority:  normal         |   Milestone:  12.5
Component:  Book           |     Version:  git
 Severity:  normal         |  Resolution:  fixed
 Keywords:                 |
---------------------------+-----------------------
Comment (by rhubarbpieguy):

 I waited several weeks after seeing this was coded as fixed but not
 changed in the documentation.  If I remember correctly, when the release
 version changed I thought it was coded fixed but the actual change was not
 done.  I assumed it was simply dropped by error.

 I'm not privy to the inner working of the documentation.  Not correcting
 "# Begin /lib/lsb/init-funtions" makes no sense to me, but while it's easy
 to say "Hey, do this" I realize execution may be more complicated when
 push comes to shove.  I don't mean to be pushy.  I'm just trying to help.

 I was planning to submit several alignment issues on the SysV side next
 week.  Is it preferred I wait until the freeze period before the next
 release?

 I usually check the documentation weekly.  Typos I report immediately, but
 unless a 404 error I wait at least a month before reporting bad links.
 Links I report through blfs-dev.  I reported two typos on the BLFS side
 this morning.  Should I report typos immediately?
-- 
Ticket URL: <https://wiki.linuxfromscratch.org/lfs/ticket/5808#comment:9>
LFS Trac <https://wiki.linuxfromscratch.org/lfs/>
Linux From Scratch: Your Distro, Your Rules.

-- 
http://lists.linuxfromscratch.org/sympa/info/lfs-book
Unsubscribe: See the above information page
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.