mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Mohr <andi@lisas.de>
To: clemens@ladisch.de, hpa@zytor.com, linux-kernel@vger.kernel.org,
	tglx@linutronix.de, corbet@lwn.net, arnd@arndb.de,
	peterz@infradead.org, mingo@kernel.org,
	gregkh@linuxfoundation.org, torvalds@linux-foundation.org,
	mst@redhat.com
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/urgent] hpet: Drop stale URLs
Date: Thu, 18 Feb 2016 07:40:24 +0100	[thread overview]
Message-ID: <20160218064024.GA13272@rhlx01.hs-esslingen.de> (raw)
In-Reply-To: <tip-4e7f9df25874cedbbc604a5c5c2e7a6efe662387@git.kernel.org>

Hi,

On Wed, Feb 17, 2016 at 04:14:54AM -0800, tip-bot for Michael S. Tsirkin wrote:
> Commit-ID:  4e7f9df25874cedbbc604a5c5c2e7a6efe662387
> Gitweb:     http://git.kernel.org/tip/4e7f9df25874cedbbc604a5c5c2e7a6efe662387
> Author:     Michael S. Tsirkin <mst@redhat.com>
> AuthorDate: Thu, 11 Feb 2016 01:05:01 +0200
> Committer:  Ingo Molnar <mingo@kernel.org>
> CommitDate: Wed, 17 Feb 2016 09:39:56 +0100
> 
> hpet: Drop stale URLs
> 
> Looks like the HPET spec at intel.com got moved.
> It isn't hard to find so drop the link, just mention
> the revision assumed.

While URLs unfortunately often are less permanent than possibly intended
(details see useful entire sub content of
"Aw: Re: Checkout hangs on invalid external URL"
  http://svn.haxx.se/users/archive-2015-11/0027.shtml)
and thus too often need to be updated or even removed as a consequence,
I feel that once an URL as a very reliable reference has been lost,
naming of a file likely is the next most reliable fallback reference
(to at least have feeding into an Internet search engine
as the next fallback step).
An alternative/second reference
would have been listing the full title of this existing document, too.

Thus I'm questioning whether the exact file name
should in fact be removed here (at 3 locations even) by this commit,
while at least usefully adding
a (albeit somewhat weak) reference of "revision 1".

>  The High Precision Event Timer (HPET) hardware follows a specification
> -by Intel and Microsoft which can be found at
> -
> -	http://www.intel.com/hardwaredesign/hpetspec_1.pdf
> +by Intel and Microsoft, revision 1.


Oh, and I noticed as a curiosity (or so I thought)
that this cleanup-style work is (to be made?) part of "x86/urgent",
which I didn't expect to be defined as topically related.

Thanks,

Andreas Mohr

      reply	other threads:[~2016-02-18  6:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10 23:05 [PATCH v2] hpet: drop stale link Michael S. Tsirkin
2016-02-12  3:22 ` Greg Kroah-Hartman
2016-02-17 12:14 ` [tip:x86/urgent] hpet: Drop stale URLs tip-bot for Michael S. Tsirkin
2016-02-18  6:40   ` Andreas Mohr [this message]

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=20160218064024.GA13272@rhlx01.hs-esslingen.de \
    --to=andi@lisas.de \
    --cc=arnd@arndb.de \
    --cc=clemens@ladisch.de \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mst@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®