[PATCH 0/2] Enable inlinelinks of alphapf.bst for 1c

[PATCH 0/2] Enable inlinelinks of alphapf.bst for 1c

[Akira Yokosawa]

From 3f4f73d738b77422bd074322f3ac67f644a8d580 Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <akiyks@gmail.com>
Date: Wed, 28 Dec 2016 00:10:28 +0900
Subject: [PATCH 0/2] Enable inlinelinks of alphapf.bst for 1c

Hi Paul,

On 2016/12/26 16:39:52 -0800, Paul E. McKenney wrote:
> On Mon, Dec 26, 2016 at 11:52:40PM +0900, Akira Yokosawa wrote:
[snip]
>> One idea is to use alphapf.bst only for 1c with inlinelinks enabled. 
>>
>> Thoughts?
>
> I am good with enabling alphaph.bst inlinelinks only for 1c!

So, this patch set does the change.
For 2c, we reverted to the original alpha bibliography style for the
moment.
And I'll keep polishing the band-aid script to shorten the href-ed part
in titles. You might want to try it for 2c when you do a release.

                                                  Thanks, Akira
--
Akira Yokosawa (2):
  Makefile: Fix .bbl dependency
  Enable 'inlinelinks' option of alphapf.bst for 1c layout

 Makefile              | 4 ++--
 alphapf.bst           | 2 +-
 appendix/appendix.tex | 6 +++++-
 3 files changed, 8 insertions(+), 4 deletions(-)

-- 
2.7.4

[PATCH 1/2] Makefile: Fix .bbl dependency

[Akira Yokosawa]

From 842d6a4951c24e01a905c28babe9b127e197ae19 Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <akiyks@gmail.com>
Date: Wed, 28 Dec 2016 00:00:44 +0900
Subject: [PATCH 1/2] Makefile: Fix .bbl dependency

BiBTeX didn't run properly after update of alphapf.bst.
$(BIBSOURCES) should have been in the dependency of ".bbl".

Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
---
 Makefile | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Makefile b/Makefile
index f0944f0..f446a66 100644
--- a/Makefile
+++ b/Makefile
@@ -68,10 +68,10 @@ all: $(targ)
 $(PDFTARGETS): %.pdf: %.tex %.bbl
 	sh utilities/runlatex.sh $(basename $@)

-$(PDFTARGETS:.pdf=.bbl): %.bbl: %.aux
+$(PDFTARGETS:.pdf=.bbl): %.bbl: %.aux $(BIBSOURCES)
 	bibtex $(basename $@)

-$(PDFTARGETS:.pdf=.aux): $(LATEXSOURCES) $(LATEXGENERATED) $(BIBSOURCES)
+$(PDFTARGETS:.pdf=.aux): $(LATEXSOURCES) $(LATEXGENERATED)
 	sh utilities/runfirstlatex.sh $(basename $@)

 perfbook_flat.tex: perfbook.tex $(LATEXSOURCES) $(PDFTARGETS_OF_EPS) $(PDFTARGETS_OF_SVG)
-- 
2.7.4

[PATCH 2/2] Enable 'inlinelinks' option of alphapf.bst for 1c layout

[Akira Yokosawa]

From 3f4f73d738b77422bd074322f3ac67f644a8d580 Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <akiyks@gmail.com>
Date: Wed, 28 Dec 2016 00:06:04 +0900
Subject: [PATCH 2/2] Enable 'inlinelinks' option of alphapf.bst for 1c layout

The "hyperref" package has an issue when a link crosses a page
or column boundary in two column layout.

See:
  http://tex.stackexchange.com/questions/1522/
  http://tex.stackexchange.com/questions/249579/

To avoid this issue, this commit enables "inlinelinks" option only
for one column layout.
For two column layout, original alpha style is selected for the
moment.

Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
---
 alphapf.bst           | 2 +-
 appendix/appendix.tex | 6 +++++-
 2 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/alphapf.bst b/alphapf.bst
index 498e0ee..6a9ec4d 100644
--- a/alphapf.bst
+++ b/alphapf.bst
@@ -69,7 +69,7 @@ FUNCTION {init.urlbst.variables}
   #1 'adddoiresolver :=     % 0=no DOI resolver; 1=include it
   #1 'addpubmedresolver :=     % 0=no PUBMED resolver; 1=include it
   #2 'hrefform :=           % 0=no crossrefs; 1=hypertex xrefs; 2=hyperref refs
-  #0 'inlinelinks :=        % 0=URLs explicit; 1=URLs attached to titles
+  #1 'inlinelinks :=        % 0=URLs explicit; 1=URLs attached to titles

   % String constants, which you _might_ want to tweak.
   "URL: " 'urlintro := % prefix before URL; typically "Available from:" or "URL":
diff --git a/appendix/appendix.tex b/appendix/appendix.tex
index 53abf2b..e94fd28 100644
--- a/appendix/appendix.tex
+++ b/appendix/appendix.tex
@@ -5,6 +5,10 @@
 \include{appendix/whymb/whymemorybarriers}
 \QuickQuizAnswers
 \input{glossary.tex}
-\bibliographystyle{alphapf} % use alpha style customized by urlbst with --inlinelinks option
+\IfTwoColumn{
+\bibliographystyle{alpha}   % Use genuine alpha style
+}{
+\bibliographystyle{alphapf} % Use alpha style customized by urlbst with --inlinelinks option
+}
 \bibliography{bib/RCU,bib/WFS,bib/hw,bib/os,bib/parallelsys,bib/patterns,bib/perfmeas,bib/refs,bib/syncrefs,bib/search,bib/swtools,bib/realtime,bib/TM,bib/standards,bib/OSS,bib/maze,bib/energy}
 \include{appendix/ack/ack}
-- 
2.7.4

Re: [PATCH 0/2] Enable inlinelinks of alphapf.bst for 1c

[Paul E. McKenney]

On Wed, Dec 28, 2016 at 12:25:48AM +0900, Akira Yokosawa wrote:
> >From 3f4f73d738b77422bd074322f3ac67f644a8d580 Mon Sep 17 00:00:00 2001
> From: Akira Yokosawa <akiyks@gmail.com>
> Date: Wed, 28 Dec 2016 00:10:28 +0900
> Subject: [PATCH 0/2] Enable inlinelinks of alphapf.bst for 1c
> 
> Hi Paul,
> 
> On 2016/12/26 16:39:52 -0800, Paul E. McKenney wrote:
> > On Mon, Dec 26, 2016 at 11:52:40PM +0900, Akira Yokosawa wrote:
> [snip]
> >> One idea is to use alphapf.bst only for 1c with inlinelinks enabled. 
> >>
> >> Thoughts?
> >
> > I am good with enabling alphaph.bst inlinelinks only for 1c!
> 
> So, this patch set does the change.
> For 2c, we reverted to the original alpha bibliography style for the
> moment.
> And I'll keep polishing the band-aid script to shorten the href-ed part
> in titles. You might want to try it for 2c when you do a release.

Applied and pushed, thank you!

Speaking of releases, for whatever it is worth, I expect to do one
in a few days.

							Thanx, Paul

>                                                   Thanks, Akira
> --
> Akira Yokosawa (2):
>   Makefile: Fix .bbl dependency
>   Enable 'inlinelinks' option of alphapf.bst for 1c layout
> 
>  Makefile              | 4 ++--
>  alphapf.bst           | 2 +-
>  appendix/appendix.tex | 6 +++++-
>  3 files changed, 8 insertions(+), 4 deletions(-)
> 
> -- 
> 2.7.4
> 

Re: [PATCH 0/2] Enable inlinelinks of alphapf.bst for 1c

[Akira Yokosawa]

On 2016/12/27 12:53:45 -0800, Paul E. McKenney wrote:
> On Wed, Dec 28, 2016 at 12:25:48AM +0900, Akira Yokosawa wrote:
>> >From 3f4f73d738b77422bd074322f3ac67f644a8d580 Mon Sep 17 00:00:00 2001
>> From: Akira Yokosawa <akiyks@gmail.com>
>> Date: Wed, 28 Dec 2016 00:10:28 +0900
>> Subject: [PATCH 0/2] Enable inlinelinks of alphapf.bst for 1c
>>
>> Hi Paul,
>>
>> On 2016/12/26 16:39:52 -0800, Paul E. McKenney wrote:
>>> On Mon, Dec 26, 2016 at 11:52:40PM +0900, Akira Yokosawa wrote:
>> [snip]
>>>> One idea is to use alphapf.bst only for 1c with inlinelinks enabled. 
>>>>
>>>> Thoughts?
>>>
>>> I am good with enabling alphaph.bst inlinelinks only for 1c!
>>
>> So, this patch set does the change.
>> For 2c, we reverted to the original alpha bibliography style for the
>> moment.
>> And I'll keep polishing the band-aid script to shorten the href-ed part
>> in titles. You might want to try it for 2c when you do a release.
> 
> Applied and pushed, thank you!
> 
> Speaking of releases, for whatever it is worth, I expect to do one
> in a few days.

Every 6 month!

At the current state of ongoing bibliography update, I don't think
it makes much difference if you try inlinelinks for 2c.
Or, will you apply the "bib-append-dio" series this time?
Then it might be worthwhile. You can replace the released .pdf with
inlinelinks enabled after the fact.

I have readied other branches of url updates of .bib files, but I thought
I should wait and send their pull request after the doi updates are applied.
If you are willing to apply the other (lot of) updates for the next release,
I can send the pull requests soon. But it is not urgent.

By the way, I want the "courier scaled" font to be default monospace
font for 2c and 1c builds. Have you tried the "mss" target lately?
If you are ok with it, I'll prepare a patch to do so.

                                                 Thanks, Akira

> 
> 							Thanx, Paul
> 
>>                                                   Thanks, Akira
>> --
>> Akira Yokosawa (2):
>>   Makefile: Fix .bbl dependency
>>   Enable 'inlinelinks' option of alphapf.bst for 1c layout
>>
>>  Makefile              | 4 ++--
>>  alphapf.bst           | 2 +-
>>  appendix/appendix.tex | 6 +++++-
>>  3 files changed, 8 insertions(+), 4 deletions(-)
>>
>> -- 
>> 2.7.4
>>
> 
> 

Re: [PATCH 0/2] Enable inlinelinks of alphapf.bst for 1c

[Paul E. McKenney]

On Wed, Dec 28, 2016 at 07:07:28AM +0900, Akira Yokosawa wrote:
> On 2016/12/27 12:53:45 -0800, Paul E. McKenney wrote:
> > On Wed, Dec 28, 2016 at 12:25:48AM +0900, Akira Yokosawa wrote:
> >> >From 3f4f73d738b77422bd074322f3ac67f644a8d580 Mon Sep 17 00:00:00 2001
> >> From: Akira Yokosawa <akiyks@gmail.com>
> >> Date: Wed, 28 Dec 2016 00:10:28 +0900
> >> Subject: [PATCH 0/2] Enable inlinelinks of alphapf.bst for 1c
> >>
> >> Hi Paul,
> >>
> >> On 2016/12/26 16:39:52 -0800, Paul E. McKenney wrote:
> >>> On Mon, Dec 26, 2016 at 11:52:40PM +0900, Akira Yokosawa wrote:
> >> [snip]
> >>>> One idea is to use alphapf.bst only for 1c with inlinelinks enabled. 
> >>>>
> >>>> Thoughts?
> >>>
> >>> I am good with enabling alphaph.bst inlinelinks only for 1c!
> >>
> >> So, this patch set does the change.
> >> For 2c, we reverted to the original alpha bibliography style for the
> >> moment.
> >> And I'll keep polishing the band-aid script to shorten the href-ed part
> >> in titles. You might want to try it for 2c when you do a release.
> > 
> > Applied and pushed, thank you!
> > 
> > Speaking of releases, for whatever it is worth, I expect to do one
> > in a few days.
> 
> Every 6 month!
> 
> At the current state of ongoing bibliography update, I don't think
> it makes much difference if you try inlinelinks for 2c.
> Or, will you apply the "bib-append-dio" series this time?
> Then it might be worthwhile. You can replace the released .pdf with
> inlinelinks enabled after the fact.
> 
> I have readied other branches of url updates of .bib files, but I thought
> I should wait and send their pull request after the doi updates are applied.
> If you are willing to apply the other (lot of) updates for the next release,
> I can send the pull requests soon. But it is not urgent.
> 
> By the way, I want the "courier scaled" font to be default monospace
> font for 2c and 1c builds. Have you tried the "mss" target lately?
> If you are ok with it, I'll prepare a patch to do so.

It does build, but what am I looking for?  Does it allow me to remove
the bogus "~" characters in some of the tables containing \co{}?

							Thanx, Paul

>                                                  Thanks, Akira
> 
> > 
> > 							Thanx, Paul
> > 
> >>                                                   Thanks, Akira
> >> --
> >> Akira Yokosawa (2):
> >>   Makefile: Fix .bbl dependency
> >>   Enable 'inlinelinks' option of alphapf.bst for 1c layout
> >>
> >>  Makefile              | 4 ++--
> >>  alphapf.bst           | 2 +-
> >>  appendix/appendix.tex | 6 +++++-
> >>  3 files changed, 8 insertions(+), 4 deletions(-)
> >>
> >> -- 
> >> 2.7.4
> >>
> > 
> > 
> 

Re: [PATCH 0/2] Enable inlinelinks of alphapf.bst for 1c

[Akira Yokosawa]

On 2016/12/28 19:56:03 -0800, Paul E. McKenney wrote:
> On Wed, Dec 28, 2016 at 07:07:28AM +0900, Akira Yokosawa wrote:
>> On 2016/12/27 12:53:45 -0800, Paul E. McKenney wrote:
>>> On Wed, Dec 28, 2016 at 12:25:48AM +0900, Akira Yokosawa wrote:
>>>> >From 3f4f73d738b77422bd074322f3ac67f644a8d580 Mon Sep 17 00:00:00 2001
>>>> From: Akira Yokosawa <akiyks@gmail.com>
>>>> Date: Wed, 28 Dec 2016 00:10:28 +0900
>>>> Subject: [PATCH 0/2] Enable inlinelinks of alphapf.bst for 1c
>>>>
>>>> Hi Paul,
>>>>
>>>> On 2016/12/26 16:39:52 -0800, Paul E. McKenney wrote:
>>>>> On Mon, Dec 26, 2016 at 11:52:40PM +0900, Akira Yokosawa wrote:
>>>> [snip]
>>>>>> One idea is to use alphapf.bst only for 1c with inlinelinks enabled. 
>>>>>>
>>>>>> Thoughts?
>>>>>
>>>>> I am good with enabling alphaph.bst inlinelinks only for 1c!
>>>>
>>>> So, this patch set does the change.
>>>> For 2c, we reverted to the original alpha bibliography style for the
>>>> moment.
>>>> And I'll keep polishing the band-aid script to shorten the href-ed part
>>>> in titles. You might want to try it for 2c when you do a release.
>>>
>>> Applied and pushed, thank you!
>>>
>>> Speaking of releases, for whatever it is worth, I expect to do one
>>> in a few days.
>>
>> Every 6 month!
>>
>> At the current state of ongoing bibliography update, I don't think
>> it makes much difference if you try inlinelinks for 2c.
>> Or, will you apply the "bib-append-dio" series this time?
>> Then it might be worthwhile. You can replace the released .pdf with
>> inlinelinks enabled after the fact.
>>
>> I have readied other branches of url updates of .bib files, but I thought
>> I should wait and send their pull request after the doi updates are applied.
>> If you are willing to apply the other (lot of) updates for the next release,
>> I can send the pull requests soon. But it is not urgent.
>>
>> By the way, I want the "courier scaled" font to be default monospace
>> font for 2c and 1c builds. Have you tried the "mss" target lately?
>> If you are ok with it, I'll prepare a patch to do so.
> 
> It does build, but what am I looking for?  Does it allow me to remove
> the bogus "~" characters in some of the tables containing \co{}?

Well, that may be possible, but for now, I want you to see if the
reduced height of the monospace font in the text is acceptable for you.

The direct effect of the change is that we can revert 2 commits
which manually specified smaller font sizes for code sample figures.

See commits bc0fd9d40035 ("after: Tweak font size of Figure A.2") and
c7c5e8a1829e ("formal/dyntickrcu: Adjust font size of sample code").

Undoing tweaks in Tables can be looked at once we switch the default font.

                                                   Thanks, Akira
> 
> 							Thanx, Paul
> 
>>                                                  Thanks, Akira
>>
>>>
>>> 							Thanx, Paul
>>>
>>>>                                                   Thanks, Akira
>>>> --
>>>> Akira Yokosawa (2):
>>>>   Makefile: Fix .bbl dependency
>>>>   Enable 'inlinelinks' option of alphapf.bst for 1c layout
>>>>
>>>>  Makefile              | 4 ++--
>>>>  alphapf.bst           | 2 +-
>>>>  appendix/appendix.tex | 6 +++++-
>>>>  3 files changed, 8 insertions(+), 4 deletions(-)
>>>>
>>>> -- 
>>>> 2.7.4
>>>>
>>>
>>>
>>
> 
> 

Re: [PATCH 0/2] Enable inlinelinks of alphapf.bst for 1c

[Paul E. McKenney]

On Thu, Dec 29, 2016 at 01:13:24PM +0900, Akira Yokosawa wrote:
> On 2016/12/28 19:56:03 -0800, Paul E. McKenney wrote:
> > On Wed, Dec 28, 2016 at 07:07:28AM +0900, Akira Yokosawa wrote:
> >> On 2016/12/27 12:53:45 -0800, Paul E. McKenney wrote:
> >>> On Wed, Dec 28, 2016 at 12:25:48AM +0900, Akira Yokosawa wrote:
> >>>> >From 3f4f73d738b77422bd074322f3ac67f644a8d580 Mon Sep 17 00:00:00 2001
> >>>> From: Akira Yokosawa <akiyks@gmail.com>
> >>>> Date: Wed, 28 Dec 2016 00:10:28 +0900
> >>>> Subject: [PATCH 0/2] Enable inlinelinks of alphapf.bst for 1c
> >>>>
> >>>> Hi Paul,
> >>>>
> >>>> On 2016/12/26 16:39:52 -0800, Paul E. McKenney wrote:
> >>>>> On Mon, Dec 26, 2016 at 11:52:40PM +0900, Akira Yokosawa wrote:
> >>>> [snip]
> >>>>>> One idea is to use alphapf.bst only for 1c with inlinelinks enabled. 
> >>>>>>
> >>>>>> Thoughts?
> >>>>>
> >>>>> I am good with enabling alphaph.bst inlinelinks only for 1c!
> >>>>
> >>>> So, this patch set does the change.
> >>>> For 2c, we reverted to the original alpha bibliography style for the
> >>>> moment.
> >>>> And I'll keep polishing the band-aid script to shorten the href-ed part
> >>>> in titles. You might want to try it for 2c when you do a release.
> >>>
> >>> Applied and pushed, thank you!
> >>>
> >>> Speaking of releases, for whatever it is worth, I expect to do one
> >>> in a few days.
> >>
> >> Every 6 month!
> >>
> >> At the current state of ongoing bibliography update, I don't think
> >> it makes much difference if you try inlinelinks for 2c.
> >> Or, will you apply the "bib-append-dio" series this time?
> >> Then it might be worthwhile. You can replace the released .pdf with
> >> inlinelinks enabled after the fact.
> >>
> >> I have readied other branches of url updates of .bib files, but I thought
> >> I should wait and send their pull request after the doi updates are applied.
> >> If you are willing to apply the other (lot of) updates for the next release,
> >> I can send the pull requests soon. But it is not urgent.
> >>
> >> By the way, I want the "courier scaled" font to be default monospace
> >> font for 2c and 1c builds. Have you tried the "mss" target lately?
> >> If you are ok with it, I'll prepare a patch to do so.
> > 
> > It does build, but what am I looking for?  Does it allow me to remove
> > the bogus "~" characters in some of the tables containing \co{}?
> 
> Well, that may be possible, but for now, I want you to see if the
> reduced height of the monospace font in the text is acceptable for you.

It looks fine to me.

> The direct effect of the change is that we can revert 2 commits
> which manually specified smaller font sizes for code sample figures.
> 
> See commits bc0fd9d40035 ("after: Tweak font size of Figure A.2") and
> c7c5e8a1829e ("formal/dyntickrcu: Adjust font size of sample code").
> 
> Undoing tweaks in Tables can be looked at once we switch the default font.

However, this sounds like something to do immediately after release in
order to give people more time to spot any problems.  Seem reasonable?

							Thanx, Paul

> >>>> --
> >>>> Akira Yokosawa (2):
> >>>>   Makefile: Fix .bbl dependency
> >>>>   Enable 'inlinelinks' option of alphapf.bst for 1c layout
> >>>>
> >>>>  Makefile              | 4 ++--
> >>>>  alphapf.bst           | 2 +-
> >>>>  appendix/appendix.tex | 6 +++++-
> >>>>  3 files changed, 8 insertions(+), 4 deletions(-)
> >>>>
> >>>> -- 
> >>>> 2.7.4
> >>>>
> >>>
> >>>
> >>
> > 
> > 
> --
> 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
> 

Re: [PATCH 0/2] Enable inlinelinks of alphapf.bst for 1c

[Akira Yokosawa]

On 2016/12/28 21:06:01 -0800, Paul E. McKenney wrote:
> On Thu, Dec 29, 2016 at 01:13:24PM +0900, Akira Yokosawa wrote:
>> On 2016/12/28 19:56:03 -0800, Paul E. McKenney wrote:
>>> On Wed, Dec 28, 2016 at 07:07:28AM +0900, Akira Yokosawa wrote:
>>>> On 2016/12/27 12:53:45 -0800, Paul E. McKenney wrote:
>>>>> On Wed, Dec 28, 2016 at 12:25:48AM +0900, Akira Yokosawa wrote:
>>>>>> >From 3f4f73d738b77422bd074322f3ac67f644a8d580 Mon Sep 17 00:00:00 2001
>>>>>> From: Akira Yokosawa <akiyks@gmail.com>
>>>>>> Date: Wed, 28 Dec 2016 00:10:28 +0900
>>>>>> Subject: [PATCH 0/2] Enable inlinelinks of alphapf.bst for 1c
>>>>>>
>>>>>> Hi Paul,
>>>>>>
>>>>>> On 2016/12/26 16:39:52 -0800, Paul E. McKenney wrote:
>>>>>>> On Mon, Dec 26, 2016 at 11:52:40PM +0900, Akira Yokosawa wrote:
>>>>>> [snip]
>>>>>>>> One idea is to use alphapf.bst only for 1c with inlinelinks enabled. 
>>>>>>>>
>>>>>>>> Thoughts?
>>>>>>>
>>>>>>> I am good with enabling alphaph.bst inlinelinks only for 1c!
>>>>>>
>>>>>> So, this patch set does the change.
>>>>>> For 2c, we reverted to the original alpha bibliography style for the
>>>>>> moment.
>>>>>> And I'll keep polishing the band-aid script to shorten the href-ed part
>>>>>> in titles. You might want to try it for 2c when you do a release.
>>>>>
>>>>> Applied and pushed, thank you!
>>>>>
>>>>> Speaking of releases, for whatever it is worth, I expect to do one
>>>>> in a few days.
>>>>
>>>> Every 6 month!
>>>>
>>>> At the current state of ongoing bibliography update, I don't think
>>>> it makes much difference if you try inlinelinks for 2c.
>>>> Or, will you apply the "bib-append-dio" series this time?
>>>> Then it might be worthwhile. You can replace the released .pdf with
>>>> inlinelinks enabled after the fact.
>>>>
>>>> I have readied other branches of url updates of .bib files, but I thought
>>>> I should wait and send their pull request after the doi updates are applied.
>>>> If you are willing to apply the other (lot of) updates for the next release,
>>>> I can send the pull requests soon. But it is not urgent.
>>>>
>>>> By the way, I want the "courier scaled" font to be default monospace
>>>> font for 2c and 1c builds. Have you tried the "mss" target lately?
>>>> If you are ok with it, I'll prepare a patch to do so.
>>>
>>> It does build, but what am I looking for?  Does it allow me to remove
>>> the bogus "~" characters in some of the tables containing \co{}?
>>
>> Well, that may be possible, but for now, I want you to see if the
>> reduced height of the monospace font in the text is acceptable for you.
> 
> It looks fine to me.
> 
>> The direct effect of the change is that we can revert 2 commits
>> which manually specified smaller font sizes for code sample figures.
>>
>> See commits bc0fd9d40035 ("after: Tweak font size of Figure A.2") and
>> c7c5e8a1829e ("formal/dyntickrcu: Adjust font size of sample code").
>>
>> Undoing tweaks in Tables can be looked at once we switch the default font.
> 
> However, this sounds like something to do immediately after release in
> order to give people more time to spot any problems.  Seem reasonable?

Yes, I agree.
Will submit a patch set after the upcoming release.

                                                   Thanks, Akira
> 
> 							Thanx, Paul
> 
>>>>>> --
>>>>>> Akira Yokosawa (2):
>>>>>>   Makefile: Fix .bbl dependency
>>>>>>   Enable 'inlinelinks' option of alphapf.bst for 1c layout
>>>>>>
>>>>>>  Makefile              | 4 ++--
>>>>>>  alphapf.bst           | 2 +-
>>>>>>  appendix/appendix.tex | 6 +++++-
>>>>>>  3 files changed, 8 insertions(+), 4 deletions(-)
>>>>>>
>>>>>> -- 
>>>>>> 2.7.4
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>> --
>> 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
>>
> 
> 

Re: [PATCH 0/2] Enable inlinelinks of alphapf.bst for 1c

[Paul E. McKenney]

On Thu, Dec 29, 2016 at 02:10:39PM +0900, Akira Yokosawa wrote:
> On 2016/12/28 21:06:01 -0800, Paul E. McKenney wrote:
> > On Thu, Dec 29, 2016 at 01:13:24PM +0900, Akira Yokosawa wrote:
> >> On 2016/12/28 19:56:03 -0800, Paul E. McKenney wrote:
> >>> On Wed, Dec 28, 2016 at 07:07:28AM +0900, Akira Yokosawa wrote:
> >>>> On 2016/12/27 12:53:45 -0800, Paul E. McKenney wrote:
> >>>>> On Wed, Dec 28, 2016 at 12:25:48AM +0900, Akira Yokosawa wrote:
> >>>>>> >From 3f4f73d738b77422bd074322f3ac67f644a8d580 Mon Sep 17 00:00:00 2001
> >>>>>> From: Akira Yokosawa <akiyks@gmail.com>
> >>>>>> Date: Wed, 28 Dec 2016 00:10:28 +0900
> >>>>>> Subject: [PATCH 0/2] Enable inlinelinks of alphapf.bst for 1c
> >>>>>>
> >>>>>> Hi Paul,
> >>>>>>
> >>>>>> On 2016/12/26 16:39:52 -0800, Paul E. McKenney wrote:
> >>>>>>> On Mon, Dec 26, 2016 at 11:52:40PM +0900, Akira Yokosawa wrote:
> >>>>>> [snip]
> >>>>>>>> One idea is to use alphapf.bst only for 1c with inlinelinks enabled. 
> >>>>>>>>
> >>>>>>>> Thoughts?
> >>>>>>>
> >>>>>>> I am good with enabling alphaph.bst inlinelinks only for 1c!
> >>>>>>
> >>>>>> So, this patch set does the change.
> >>>>>> For 2c, we reverted to the original alpha bibliography style for the
> >>>>>> moment.
> >>>>>> And I'll keep polishing the band-aid script to shorten the href-ed part
> >>>>>> in titles. You might want to try it for 2c when you do a release.
> >>>>>
> >>>>> Applied and pushed, thank you!
> >>>>>
> >>>>> Speaking of releases, for whatever it is worth, I expect to do one
> >>>>> in a few days.
> >>>>
> >>>> Every 6 month!
> >>>>
> >>>> At the current state of ongoing bibliography update, I don't think
> >>>> it makes much difference if you try inlinelinks for 2c.
> >>>> Or, will you apply the "bib-append-dio" series this time?
> >>>> Then it might be worthwhile. You can replace the released .pdf with
> >>>> inlinelinks enabled after the fact.
> >>>>
> >>>> I have readied other branches of url updates of .bib files, but I thought
> >>>> I should wait and send their pull request after the doi updates are applied.
> >>>> If you are willing to apply the other (lot of) updates for the next release,
> >>>> I can send the pull requests soon. But it is not urgent.
> >>>>
> >>>> By the way, I want the "courier scaled" font to be default monospace
> >>>> font for 2c and 1c builds. Have you tried the "mss" target lately?
> >>>> If you are ok with it, I'll prepare a patch to do so.
> >>>
> >>> It does build, but what am I looking for?  Does it allow me to remove
> >>> the bogus "~" characters in some of the tables containing \co{}?
> >>
> >> Well, that may be possible, but for now, I want you to see if the
> >> reduced height of the monospace font in the text is acceptable for you.
> > 
> > It looks fine to me.
> > 
> >> The direct effect of the change is that we can revert 2 commits
> >> which manually specified smaller font sizes for code sample figures.
> >>
> >> See commits bc0fd9d40035 ("after: Tweak font size of Figure A.2") and
> >> c7c5e8a1829e ("formal/dyntickrcu: Adjust font size of sample code").
> >>
> >> Undoing tweaks in Tables can be looked at once we switch the default font.
> > 
> > However, this sounds like something to do immediately after release in
> > order to give people more time to spot any problems.  Seem reasonable?
> 
> Yes, I agree.
> Will submit a patch set after the upcoming release.

Very good!

							Thanx, Paul

> >>>>>> --
> >>>>>> Akira Yokosawa (2):
> >>>>>>   Makefile: Fix .bbl dependency
> >>>>>>   Enable 'inlinelinks' option of alphapf.bst for 1c layout
> >>>>>>
> >>>>>>  Makefile              | 4 ++--
> >>>>>>  alphapf.bst           | 2 +-
> >>>>>>  appendix/appendix.tex | 6 +++++-
> >>>>>>  3 files changed, 8 insertions(+), 4 deletions(-)
> >>>>>>
> >>>>>> -- 
> >>>>>> 2.7.4
> >>>>>>
> >>>>>
> >>>>>
> >>>>
> >>>
> >>>
> >> --
> >> 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
> >>
> > 
> > 
> 

Re: [PATCH 0/2] Enable inlinelinks of alphapf.bst for 1c

[Akira Yokosawa]

On 2016/12/28 19:56:03 -0800, Paul E. McKenney wrote:
> On Wed, Dec 28, 2016 at 07:07:28AM +0900, Akira Yokosawa wrote:
>> On 2016/12/27 12:53:45 -0800, Paul E. McKenney wrote:
>>> On Wed, Dec 28, 2016 at 12:25:48AM +0900, Akira Yokosawa wrote:
>>>> >From 3f4f73d738b77422bd074322f3ac67f644a8d580 Mon Sep 17 00:00:00 2001
>>>> From: Akira Yokosawa <akiyks@gmail.com>
>>>> Date: Wed, 28 Dec 2016 00:10:28 +0900
>>>> Subject: [PATCH 0/2] Enable inlinelinks of alphapf.bst for 1c
>>>>
>>>> Hi Paul,
>>>>
>>>> On 2016/12/26 16:39:52 -0800, Paul E. McKenney wrote:
>>>>> On Mon, Dec 26, 2016 at 11:52:40PM +0900, Akira Yokosawa wrote:
>>>> [snip]
>>>>>> One idea is to use alphapf.bst only for 1c with inlinelinks enabled. 
>>>>>>
>>>>>> Thoughts?
>>>>>
>>>>> I am good with enabling alphaph.bst inlinelinks only for 1c!
>>>>
>>>> So, this patch set does the change.
>>>> For 2c, we reverted to the original alpha bibliography style for the
>>>> moment.
>>>> And I'll keep polishing the band-aid script to shorten the href-ed part
>>>> in titles. You might want to try it for 2c when you do a release.
>>>
>>> Applied and pushed, thank you!
>>>
>>> Speaking of releases, for whatever it is worth, I expect to do one
>>> in a few days.
>>
>> Every 6 month!
>>
>> At the current state of ongoing bibliography update, I don't think
>> it makes much difference if you try inlinelinks for 2c.
>> Or, will you apply the "bib-append-dio" series this time?
>> Then it might be worthwhile. You can replace the released .pdf with
>> inlinelinks enabled after the fact.
>>
>> I have readied other branches of url updates of .bib files, but I thought
>> I should wait and send their pull request after the doi updates are applied.
>> If you are willing to apply the other (lot of) updates for the next release,
>> I can send the pull requests soon. But it is not urgent.
>>
>> By the way, I want the "courier scaled" font to be default monospace
>> font for 2c and 1c builds. Have you tried the "mss" target lately?
>> If you are ok with it, I'll prepare a patch to do so.
> 
> It does build, but what am I looking for?  Does it allow me to remove
> the bogus "~" characters in some of the tables containing \co{}?

JFYI, those bogus "~" characters have nothing to do with the choice of
monospace font.
It is the \co{} command (or the \lstinline command it uses) that confuses
tabular environment's column width estimation. When a \co{} contains "_"
characters, it seems that the tabular environment sometimes treats them
as if they prefixed subscripts and estimates the width shorter than the
string to be actuary typeset.

I did some search, but could not find anyone else reporting the issue...

Most of \co{}s within tables are used because they don't require escaping of
LaTeX delimiters such as "_". For this purpose, the \co{} command is
overkill. I'll define another command to be used inside tables.

A few of them are used for automatic line breaks provided by lstinline.
They seem to need protection of parbox or minipage around them on case by
case bases.

I'll see proper ways to present those tables. But some of them may take
a while.

                                                 Thanks, Akira
> 
> 							Thanx, Paul
> 
>>                                                  Thanks, Akira
>>
>>>
>>> 							Thanx, Paul
>>>
>>>>                                                   Thanks, Akira
>>>> --
>>>> Akira Yokosawa (2):
>>>>   Makefile: Fix .bbl dependency
>>>>   Enable 'inlinelinks' option of alphapf.bst for 1c layout
>>>>
>>>>  Makefile              | 4 ++--
>>>>  alphapf.bst           | 2 +-
>>>>  appendix/appendix.tex | 6 +++++-
>>>>  3 files changed, 8 insertions(+), 4 deletions(-)
>>>>
>>>> -- 
>>>> 2.7.4
>>>>
>>>
>>>
>>
> 
> 

Re: [PATCH 0/2] Enable inlinelinks of alphapf.bst for 1c

[Paul E. McKenney]

On Sat, Dec 31, 2016 at 12:33:13AM +0900, Akira Yokosawa wrote:
> On 2016/12/28 19:56:03 -0800, Paul E. McKenney wrote:
> > On Wed, Dec 28, 2016 at 07:07:28AM +0900, Akira Yokosawa wrote:
> >> On 2016/12/27 12:53:45 -0800, Paul E. McKenney wrote:
> >>> On Wed, Dec 28, 2016 at 12:25:48AM +0900, Akira Yokosawa wrote:
> >>>> >From 3f4f73d738b77422bd074322f3ac67f644a8d580 Mon Sep 17 00:00:00 2001
> >>>> From: Akira Yokosawa <akiyks@gmail.com>
> >>>> Date: Wed, 28 Dec 2016 00:10:28 +0900
> >>>> Subject: [PATCH 0/2] Enable inlinelinks of alphapf.bst for 1c
> >>>>
> >>>> Hi Paul,
> >>>>
> >>>> On 2016/12/26 16:39:52 -0800, Paul E. McKenney wrote:
> >>>>> On Mon, Dec 26, 2016 at 11:52:40PM +0900, Akira Yokosawa wrote:
> >>>> [snip]
> >>>>>> One idea is to use alphapf.bst only for 1c with inlinelinks enabled. 
> >>>>>>
> >>>>>> Thoughts?
> >>>>>
> >>>>> I am good with enabling alphaph.bst inlinelinks only for 1c!
> >>>>
> >>>> So, this patch set does the change.
> >>>> For 2c, we reverted to the original alpha bibliography style for the
> >>>> moment.
> >>>> And I'll keep polishing the band-aid script to shorten the href-ed part
> >>>> in titles. You might want to try it for 2c when you do a release.
> >>>
> >>> Applied and pushed, thank you!
> >>>
> >>> Speaking of releases, for whatever it is worth, I expect to do one
> >>> in a few days.
> >>
> >> Every 6 month!
> >>
> >> At the current state of ongoing bibliography update, I don't think
> >> it makes much difference if you try inlinelinks for 2c.
> >> Or, will you apply the "bib-append-dio" series this time?
> >> Then it might be worthwhile. You can replace the released .pdf with
> >> inlinelinks enabled after the fact.
> >>
> >> I have readied other branches of url updates of .bib files, but I thought
> >> I should wait and send their pull request after the doi updates are applied.
> >> If you are willing to apply the other (lot of) updates for the next release,
> >> I can send the pull requests soon. But it is not urgent.
> >>
> >> By the way, I want the "courier scaled" font to be default monospace
> >> font for 2c and 1c builds. Have you tried the "mss" target lately?
> >> If you are ok with it, I'll prepare a patch to do so.
> > 
> > It does build, but what am I looking for?  Does it allow me to remove
> > the bogus "~" characters in some of the tables containing \co{}?
> 
> JFYI, those bogus "~" characters have nothing to do with the choice of
> monospace font.
> It is the \co{} command (or the \lstinline command it uses) that confuses
> tabular environment's column width estimation. When a \co{} contains "_"
> characters, it seems that the tabular environment sometimes treats them
> as if they prefixed subscripts and estimates the width shorter than the
> string to be actuary typeset.
> 
> I did some search, but could not find anyone else reporting the issue...
> 
> Most of \co{}s within tables are used because they don't require escaping of
> LaTeX delimiters such as "_". For this purpose, the \co{} command is
> overkill. I'll define another command to be used inside tables.
> 
> A few of them are used for automatic line breaks provided by lstinline.
> They seem to need protection of parbox or minipage around them on case by
> case bases.
> 
> I'll see proper ways to present those tables. But some of them may take
> a while.

Thank you for the explanation!  And the "~" characters have been there
for some time, so no overwhelming urgency.

But at least I now know that the number of "~" characters needed is
a function of the number of "_" characters, so less experimentation
required.  ;-)

							Thanx, Paul