From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH 03/10] Localize floatrow.sty
Date: Mon, 31 Jul 2017 05:45:54 -0700 [thread overview]
Message-ID: <20170731124554.GZ3730@linux.vnet.ibm.com> (raw)
In-Reply-To: <FA1EBFD0-3BFE-4D77-9BED-87EDC03397C4@gmail.com>
On Mon, Jul 31, 2017 at 02:01:55PM +0900, Akira Yokosawa wrote:
> 2017/07/31 13:05、Akira Yokosawa <akiyks@gmail.com> のメッセージ:
>
> >
> >
> >
> >
> > 2017/07/31 12:26、Paul E. McKenney <paulmck@linux.vnet.ibm.com> のメッセージ:
> >
> >> On Fri, Jul 28, 2017 at 06:58:07PM +0900, Akira Yokosawa wrote:
> >>>> From 53ff86011be07a62dba37a5bef56f04f25531dd1 Mon Sep 17 00:00:00 2001
> >>> From: Akira Yokosawa <akiyks@gmail.com>
> >>> Date: Thu, 20 Jul 2017 23:34:58 +0900
> >>> Subject: [PATCH 03/10] Localize floatrow.sty
> >>>
> >>> The "floatrow" package conflicts with two-column layout.
> >>> A possible workaround was posted at [1] and it seems to work
> >>> in perfbook. Before the change, import the style file as of v0.3b
> >>> with trailing white spaces removed.
> >>>
> >>> [1] https://tex.stackexchange.com/questions/133127/
> >>
> >> If I understand the license correctly, we have to use a different name
> >> due to having modified the file.
> >
> > Yes.
> > I did the rename in the next commit. By splitting them,
> > it would be easier to see the workaround.
>
> Ah, now I see your point.
> This patch should have used the renamed file name.
> Then the following diff would have been much smaller.
>
> I'll respin later.
Very good, thank you!
Thanx, Paul
> Thanks, Akira
> (from mobile, might be QP encoded)
>
> >
> > Or, do we need to keep the trailing blanks at this point?
> >
> >> Or has this change (commenting out
> >> \textwidth\columnwidth) been applied upstream?
> >
> > No, the workaround looks like only a hint.
> > Again, two-column layout tend to have little attention.
> >
> >> Or does changing the
> >> name mean that the fix is ineffective?
> >
> > It is effective for perfbook AFAICS.
> >
> > Thanks, Akira
> > (from mobile, might be QP encoded)
> >>
> >> (I applied the first two, thank you!)
> >>
> >> Thanx, Paul
>
> [...]--
> To unsubscribe from this list: send the line "unsubscribe perfbook" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2017-07-31 12:45 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 9:53 [PATCH 00/10] Add style guide Akira Yokosawa
2017-07-28 9:55 ` [PATCH 01/10] appendix: " Akira Yokosawa
2017-07-28 9:57 ` [PATCH 02/10] Specify required revision of 'verbatimbox' Akira Yokosawa
2017-07-28 9:58 ` [PATCH 03/10] Localize floatrow.sty Akira Yokosawa
2017-07-31 3:26 ` Paul E. McKenney
2017-07-31 4:05 ` Akira Yokosawa
2017-07-31 5:01 ` Akira Yokosawa
2017-07-31 12:45 ` Paul E. McKenney [this message]
2017-07-28 10:00 ` [PATCH 04/10] Apply workaround to floatrow.sty and rename it floatrowpf.sty Akira Yokosawa
2017-07-28 10:01 ` [PATCH 05/10] Define 'listing' environment for style guide Akira Yokosawa
2017-07-28 10:02 ` [PATCH 06/10] styleguide: Add listing environment examples Akira Yokosawa
2017-07-28 10:03 ` [PATCH 07/10] Disable 'floatrow' layout in manually aligned code snippets Akira Yokosawa
2017-07-28 10:04 ` [PATCH 08/10] styleguide: Add example of grouping " Akira Yokosawa
2017-07-28 10:05 ` [PATCH 09/10] styleguide: Add example of preferred table layout using 'booktabs' Akira Yokosawa
2017-07-28 10:06 ` [PATCH 10/10] styleguide: Tweak layout of 'Limitation' table Akira Yokosawa
2017-07-31 14:43 ` [PATCH v2 0/8] Add style guide Akira Yokosawa
2017-07-31 14:44 ` [PATCH v2 1/8] Localize floatrow.sty as floatrowpf.sty Akira Yokosawa
2017-07-31 14:46 ` [PATCH v2 2/8] Apply workaround to floatrowpf.sty Akira Yokosawa
2017-07-31 14:47 ` [PATCH v2 3/8] Define 'listing' environment for style guide Akira Yokosawa
2017-07-31 14:49 ` [PATCH v2 4/8] styleguide: Add listing environment examples Akira Yokosawa
2017-07-31 14:50 ` [PATCH v2 5/8] Disable 'floatrow' layout in manually aligned code snippets Akira Yokosawa
2017-07-31 14:51 ` [PATCH v2 6/8] styleguide: Add example of grouping " Akira Yokosawa
2017-07-31 14:52 ` [PATCH v2 7/8] styleguide: Add example of preferred table layout using 'booktabs' Akira Yokosawa
2017-07-31 14:52 ` [PATCH v2 8/8] styleguide: Tweak layout of 'Limitation' table Akira Yokosawa
2017-07-31 15:24 ` [PATCH v2 0/8] Add style guide Akira Yokosawa
2017-07-31 15:55 ` Paul E. McKenney
2017-07-31 15:57 ` Paul E. McKenney
2017-08-01 20:40 ` Paul E. McKenney
2017-08-02 14:57 ` Akira Yokosawa
2017-08-02 16:29 ` Paul E. McKenney
2017-08-02 22:22 ` Akira Yokosawa
2017-08-02 22:48 ` Paul E. McKenney
2017-08-05 2:09 ` Akira Yokosawa
2017-08-05 3:41 ` [PATCH 0/3] Employ auto-numbering in litmus tests Akira Yokosawa
2017-08-05 3:43 ` [PATCH 1/3] Revert commits after "Localize floatrow.sty as floatrowpf.sty" Akira Yokosawa
2017-08-05 3:44 ` [PATCH 2/3] advsync: Employ auto-numbering in litmus tests Akira Yokosawa
2017-08-05 3:46 ` [PATCH 3/3] styleguide: Remove references to 'floatrow' and adjust context Akira Yokosawa
2017-08-05 15:09 ` [PATCH 0/3] Employ auto-numbering in litmus tests Paul E. McKenney
2017-08-05 15:35 ` Akira Yokosawa
2017-08-05 15:50 ` Paul E. McKenney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170731124554.GZ3730@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akiyks@gmail.com \
--cc=perfbook@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox