> On Feb 9, 2017, at 1:37, Paul E. McKenney <paulmck@xxxxxxxxxxxxxxxxxx> 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@xxxxxxxxx> >> 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? Thanks, Akira (from mobile, might be QP encoded) > That might be the > best approach longer term. Depending of course on how difficult it > is to locate them all... > > Thanx, Paul > >> Thanks, Akira >> -- >> Akira Yokosawa (5): >> bib/maze: Mark url of ETHZurich:FS2011maze as broken link >> bib/syncrefs: Mark url of DougLocke2002a as broken >> bib/syncrefs: Mark url of Victor2002a as broken >> bib/parallelsys: Properly format UCB in author field >> alphapf.bst: Make use of 'location' field in 'inproceedings' entry >> >> alphapf.bst | 47 +++++++++++++++++++++++++++++++++-------------- >> bib/maze.bib | 4 +++- >> bib/parallelsys.bib | 4 ++-- >> bib/syncrefs.bib | 14 ++++++++------ >> 4 files changed, 46 insertions(+), 23 deletions(-) >> >> -- >> 2.7.4 >> > -- To unsubscribe from this list: send the line "unsubscribe perfbook" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
