From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH 0/5] Bibliography update round 5
Date: Wed, 8 Feb 2017 13:41:53 -0800 [thread overview]
Message-ID: <20170208214153.GW30506@linux.vnet.ibm.com> (raw)
In-Reply-To: <52CB7A57-7BDC-42C7-9AD7-5957F5CBC973@gmail.com>
On Thu, Feb 09, 2017 at 06:36:18AM +0900, Akira Yokosawa wrote:
>
>
> Akira
> (from mobile, might be QP encoded)
>
> > On Feb 9, 2017, at 6:10, Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:
> >
> >> On Thu, Feb 09, 2017 at 05:57:23AM +0900, Akira Yokosawa wrote:
> >>
> >>
> >>> On Feb 9, 2017, at 1:37, Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:
> >>>
> >>> On Wed, Feb 08, 2017 at 11:54:41PM +0900, Akira Yokosawa wrote:
> >>>>> From 58a0655ab2b5c555bd19a6d7624a9d4413cf1360 Mon Sep 17 00:00:00 2001
> >>>> From: Akira Yokosawa <akiyks@gmail.com>
> >>>> Date: Wed, 8 Feb 2017 23:34:47 +0900
> >>>> Subject: [PATCH 0/5] Bibliography update round 5
> >>>>
> >>>> Hi Paul,
> >>>>
> >>>> Here is round 5 of bibliography updates.
> >>>> Patches 1, 2, and 3 take care of broken urls. Patch 2 contains an
> >>>> alternative link to a webpage capture.
> >>>> Patch 4 is cosmetic fix of UCB in author fields
> >>>> Patch 5 is a different type of update. It adds awareness of "location"
> >>>> field in "inproceedings" entry. Please see the commit log for details.
> >>>> I think this is a reasonable change for perfbook.
> >>>
> >>> I applied the first four, and might be convinced to apply the fifth.
> >>> But first a question -- how many changes would be required to bring
> >>> my old bib entries in line with current practice?
> >>
> >> No change is required. Because this change has effect
> >> only on entries with both "address" and "location".
> >> I thought I explained this somewhere, but missed to do so.
> >> Can this clarification convince you?
> >
> > Ah, thank you for the clarification! And on to the next question...
> >
> > Does it really make sense for me to have both "address" and "location"
> > on a given bib entry? If I am doing something strange (quite likely!),
> > it is probably better for me to fix my strange bib entries than to modify
> > the tools. Especially given the possibility that others might well
> > harvest bib entries from perfbook.
>
> Well, I don't think your usage of "address" field is strange at all.
> It would be easy to find people who do the same.
>
> The fact that genuine alpha style does not recognize "location" entry would support my observation.
Sorry to continue with the questions, but should perfbook be using
some other bibliography style? The current "alpha" was pretty much an
arbitrary choice.
Thanx, Paul
> > After all, some of my bib entries were old enough to drink almost a
> > decade ago. I guess we can only be thankful that they are unable
> > to do any driving. ;-)
> >
> > Thanx, Paul
> >
>
next prev parent reply other threads:[~2017-02-09 6:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 14:54 [PATCH 0/5] Bibliography update round 5 Akira Yokosawa
2017-02-08 14:56 ` [PATCH 1/5] bib/maze: Mark url of ETHZurich:FS2011maze as broken link Akira Yokosawa
2017-02-08 14:57 ` [PATCH 2/5] bib/syncrefs: Mark url of DougLocke2002a as broken Akira Yokosawa
2017-02-08 14:58 ` [PATCH 3/5] bib/syncrefs: Mark url of Victor2002a " Akira Yokosawa
2017-02-08 14:59 ` [PATCH 4/5] bib/parallelsys: Properly format UCB in author field Akira Yokosawa
2017-02-08 15:02 ` [PATCH 5/5] alphapf.bst: Make use of 'location' field in 'inproceedings' entry Akira Yokosawa
2017-02-08 16:37 ` [PATCH 0/5] Bibliography update round 5 Paul E. McKenney
2017-02-08 20:57 ` Akira Yokosawa
2017-02-08 21:10 ` Paul E. McKenney
2017-02-08 21:36 ` Akira Yokosawa
2017-02-08 21:40 ` Akira Yokosawa
2017-02-08 21:41 ` Paul E. McKenney [this message]
2017-02-08 22:21 ` Akira Yokosawa
2017-02-09 19:26 ` 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=20170208214153.GW30506@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 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.