From: Akira Yokosawa <akiyks@gmail.com>
To: paulmck@linux.vnet.ibm.com
Cc: perfbook@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH 0/2] Enable inlinelinks of alphapf.bst for 1c
Date: Wed, 28 Dec 2016 07:07:28 +0900 [thread overview]
Message-ID: <111de212-9aeb-95b8-4e72-9edef7cff417@gmail.com> (raw)
In-Reply-To: <20161227205345.GO3742@linux.vnet.ibm.com>
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
>>
>
>
next prev parent reply other threads:[~2016-12-27 22:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-27 15:25 [PATCH 0/2] Enable inlinelinks of alphapf.bst for 1c Akira Yokosawa
2016-12-27 15:27 ` [PATCH 1/2] Makefile: Fix .bbl dependency Akira Yokosawa
2016-12-27 15:30 ` [PATCH 2/2] Enable 'inlinelinks' option of alphapf.bst for 1c layout Akira Yokosawa
2016-12-27 20:53 ` [PATCH 0/2] Enable inlinelinks of alphapf.bst for 1c Paul E. McKenney
2016-12-27 22:07 ` Akira Yokosawa [this message]
2016-12-29 3:56 ` Paul E. McKenney
2016-12-29 4:13 ` Akira Yokosawa
2016-12-29 5:06 ` Paul E. McKenney
2016-12-29 5:10 ` Akira Yokosawa
2016-12-29 5:21 ` Paul E. McKenney
2016-12-30 15:33 ` Akira Yokosawa
2016-12-30 16:59 ` 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=111de212-9aeb-95b8-4e72-9edef7cff417@gmail.com \
--to=akiyks@gmail.com \
--cc=paulmck@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.