From: erik quanstrom <quanstro@quanstro.net>
To: ebo@sandien.com, 9fans@9fans.net
Subject: Re: [9fans] iwp9.org (Re: BibTex collections of all 4 proceedings)
Date: Tue, 4 May 2010 20:35:22 -0400 [thread overview]
Message-ID: <d0b33fc61498f18e0bb0c919be862dbd@kw.quanstro.net> (raw)
In-Reply-To: <twig.1273015610.9926@swcp.com>
> would be Quanstrom2009a.pdf Quanstrom2009b.pdf or possibly something like
> Quanstrom2009AAN.pdf Quanstrom2009SR.pdf This would help with various
> maintenance and automation tasks.
i'm not sure i understand how this would help. currently
there is a single list of paper names. for your use, these
names are random. changing to a list of authors,
years and a seperate sequence list per author sounds at best
no less complicated to me. for your use, i believe such a
list would still be random.
perhaps i should have named papers by the sha1score of
the pdf.
☺
- erik
next prev parent reply other threads:[~2010-05-05 0:35 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-04 21:00 erik quanstrom
2010-05-04 23:26 ` EBo
2010-05-05 0:35 ` erik quanstrom [this message]
2010-05-05 0:54 ` EBo
-- strict thread matches above, loose matches on Subject: below --
2010-05-04 10:58 [9fans] BibTex collections of all 4 proceedings EBo
2010-05-04 19:59 ` [9fans] iwp9.org (Re: BibTex collections of all 4 proceedings) Jonas Amoson
2010-05-06 14:55 ` erik quanstrom
2010-05-06 15:12 ` Jeff Sickel
2010-05-06 16:00 ` ron minnich
2010-05-06 16:01 ` erik quanstrom
2010-05-06 16:18 ` ron minnich
2010-05-06 17:13 ` tlaronde
2010-05-06 19:52 ` EBo
2010-05-06 17:45 ` Wes Kussmaul
2010-05-06 18:12 ` Skip Tavakkolian
2010-05-06 18:35 ` ron minnich
2010-05-06 19:46 ` Skip Tavakkolian
2010-05-06 20:36 ` ron minnich
2010-05-06 21:21 ` Skip Tavakkolian
2010-05-06 21:45 ` ron minnich
2010-05-06 21:55 ` Skip Tavakkolian
2010-05-06 23:03 ` erik quanstrom
2010-05-06 23:08 ` ron minnich
2010-05-06 23:13 ` erik quanstrom
2010-05-07 0:16 ` Christopher Nielsen
2010-05-07 0:35 ` balaji
2010-05-07 0:47 ` Skip Tavakkolian
2010-05-07 13:09 ` Eric Van Hensbergen
2010-05-07 13:59 ` Paul Lalonde
2010-05-07 14:48 ` ron minnich
2010-05-07 15:37 ` Ramon de Vera
2010-05-07 15:47 ` David Leimbach
2010-05-07 23:11 ` Mathieu Lonjaret
2010-05-08 0:04 ` ron minnich
2010-05-08 11:34 ` tlaronde
2010-05-08 16:48 ` erik quanstrom
2010-05-08 17:33 ` tlaronde
2010-05-08 17:45 ` ron minnich
2010-05-08 21:34 ` David Leimbach
2010-05-12 16:08 ` Chad Brown
2010-05-12 16:26 ` Rodolfo (kix)
2010-05-12 17:06 ` ron minnich
2010-05-13 18:16 ` EBo
2010-05-13 23:26 ` Chad Brown
2010-05-13 23:40 ` ron minnich
2010-05-14 2:45 ` EBo
2010-05-14 3:14 ` ron minnich
2010-05-14 3:18 ` EBo
2010-05-14 3:27 ` erik quanstrom
2010-05-14 3:41 ` ron minnich
2010-05-14 2:24 ` Jeff Sickel
2010-05-14 3:14 ` ron minnich
2010-05-15 1:53 ` Jeff Sickel
2010-05-15 1:59 ` ron minnich
2010-05-15 2:04 ` Jeff Sickel
2010-05-15 2:27 ` EBo
2010-05-15 3:22 ` ron minnich
2010-05-15 3:58 ` EBo
2010-05-15 15:45 ` Kim Shrier
2010-05-15 16:12 ` EBo
2010-05-15 16:31 ` Kim Shrier
2010-05-15 19:46 ` ron minnich
2010-05-15 21:52 ` EBo
2010-05-06 21:55 ` EBo
2010-05-07 3:36 ` John Floren
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=d0b33fc61498f18e0bb0c919be862dbd@kw.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=ebo@sandien.com \
/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;
as well as URLs for NNTP newsgroup(s).