netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: jeffrey.t.kirsher@intel.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC] Fix Free Software Foundation address in file headers
Date: Sun, 01 Dec 2013 19:56:15 +0100	[thread overview]
Message-ID: <529B864F.3000206@gmail.com> (raw)

Jeff Kirsher wrote:

> This came up when John Fastabend got a patch to fix up the headers in
> the drivers/scsi/ directory and so I did a quick search of the network
> drivers and found several instances in the file headers where an old FSF
> address remains.  The old address is:
> 
> 59 Temple Place - Suite 330
> Boston, MA 02111-1307
> 
> The current address is:
> 
> 51 Franklin Street - Fifth Floor
> Boston, MA 02110-1301
> 
> I am wondering whether it may be best to just put a link to the Free
> Software Foundation web page instead of having to update the address any
> time a change is made.
> 
> Either way, I feel the address either needs to get corrected or changed
> to the URL, even though I am not a fan of huge patch series to make
> trivial changes like this.
> 
> Thoughts?

Something like that should be enough:

     [...]
     You should have received a copy of the GNU General Public License along
-    with this program; if not, write to the Free Software Foundation, Inc.,
-    59 Temple Place - Suite 330, Boston, MA  02111-1307, USA.
+    with this program.  If not, see <http://www.gnu.org/licenses/>.
     [...]

This was changed in that form in gpl3.


There are about 3684 references with, at least, 140 variations. Infinite Patience(TM).

             reply	other threads:[~2013-12-01 18:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-01 18:56 Xose Vazquez Perez [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-12-01  0:42 [RFC] Fix Free Software Foundation address in file headers Jeff Kirsher

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=529B864F.3000206@gmail.com \
    --to=xose.vazquez@gmail.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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 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).