Your message dated Sat, 31 Jul 2021 23:55:22 +0200
with message-id <[email protected]>
and subject line Re: Bug#807458: <standard input>:807: warning [p 10, 2.8i, div 
`3tbd1, 1', 1.2i]: can't break line
has caused the Debian Bug report #807458,
regarding <standard input>:807: warning [p 10, 2.8i, div `3tbd1,1', 1.2i]: 
can't break line
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
807458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807458
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 228-2
Severity: wishlist
File: /usr/share/man/man1/systemctl.1.gz

$ man systemctl # seen with emacs' M-x man:

...        ConsistsOf=, Wants=, BindsTo= dependencies. If no unit is
           specified, default.target is implied.

           By default, only target units are recursively expanded. When --all
           is passed, all oth<standard input>:807: warning [p 10, 2.8i, div 
`3tbd1,1', 0.8i]: can't break line
<standard input>:807: warning [p 10, 2.8i, div `3tbd1,1', 1.2i]: can't break 
line
<standard input>:817: warning [p 10, 2.8i, div `3tbd3,1', 1.0i]: can't break 
line
<standard input>:827: warning [p 10, 2.8i, div `3tbd5,1', 1.0i]: can't break 
line
er units are recursively expanded as well.

           Options --reverse, --after, --before may be used to change what

--- End Message ---
--- Begin Message ---
On Sat, 30 Jan 2016 10:24:47 +0800 =?utf-8?B?56mN5Li55bC8?= Dan Jacobson
<[email protected]> wrote:
> >>>>> "ZJ" == Zbigniew Jędrzejewski-Szmek <[email protected]> writes:
> ZJ> On Sat, Jan 30, 2016 at 08:36:04AM +0800, 積丹尼 Dan Jacobson wrote:
> >> It would be best to just reengineer your table not to generate the
errors.
> 
> ZJ> It's the output of an actual command, and the values in the
> ZJ> columns simply need that much space.
> 

Right. let's just close this issue.
If Dan wants to provide a patch which reworks those tables, I'll reopen the
bug report and forward the patch upstream.




Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---

Reply via email to