Bug#850967: Clarify /usr/bin/foo should not be hardcoded even in upstream parts

To: Sam Hartman <hartmans@debian.org>
Cc: Daniel Kahn Gillmor <dkg@debian.org>, 850967@bugs.debian.org
Subject: Bug#850967: Clarify /usr/bin/foo should not be hardcoded even in upstream parts
From: Ian Jackson <ijackson@chiark.greenend.org.uk>
Date: Wed, 11 Jan 2017 20:35:32 +0000
Message-id: <[🔎] 22646.38676.519080.40091@chiark.greenend.org.uk>
Reply-to: Ian Jackson <ijackson@chiark.greenend.org.uk>, 850967@bugs.debian.org
In-reply-to: <[🔎] tslk2a1v051.fsf@suchdamage.org>
References: <[🔎] 22646.26568.292077.676937@chiark.greenend.org.uk> <[🔎] 87inpltopc.fsf@alice.fifthhorseman.net> <[🔎] tslk2a1v051.fsf@suchdamage.org>

Sam Hartman writes ("Re: Bug#850967: Clarify /usr/bin/foo should not be hardcoded even in upstream parts"):
> [some stuff]

Please concentrate on the MIPS binutils bug.

Ian.

-- 
Ian Jackson <ijackson@chiark.greenend.org.uk>   These opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Reply to:

References:
- Bug#850967: Clarify /usr/bin/foo should not be hardcoded even in upstream parts
  - From: Ian Jackson <ijackson@chiark.greenend.org.uk>
- Bug#850967: Clarify /usr/bin/foo should not be hardcoded even in upstream parts
  - From: Daniel Kahn Gillmor <dkg@debian.org>
- Bug#850967: Clarify /usr/bin/foo should not be hardcoded even in upstream parts
  - From: Sam Hartman <hartmans@debian.org>

Prev by Date: Bug#850967: Clarify /usr/bin/foo should not be hardcoded even in upstream parts
Next by Date: Bug#850967: Clarify /usr/bin/foo should not be hardcoded even in upstream parts
Previous by thread: Bug#850967: Clarify /usr/bin/foo should not be hardcoded even in upstream parts
Next by thread: Bug#850967: Clarify /usr/bin/foo should not be hardcoded even in upstream parts [and 2 more messages]
Index(es):
- Date
- Thread