Attachment 25184 Details for Bug 20936 – Additional patch to finish the process

[patch] Additional patch to finish the process

0002-fd.o-20936-Fix-another-couple-of-instances-of-the.patch (text/plain), 1.42 KB, created by Simon McVittie on 2009-04-27 02:45:27 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Simon McVittie

Created: 2009-04-27 02:45:27 UTC

Size: 1.42 KB

patch

obsolete

>From 3187677ab25a6522c6e2e437fae8d19ffc0a135f Mon Sep 17 00:00:00 2001
>From: Simon McVittie <simon.mcvittie@collabora.co.uk>
>Date: Wed, 15 Apr 2009 21:39:44 +0100
>Subject: [PATCH 2/2] fd.o #20936: Fix another couple of instances of the old FSF address
>
>`git grep 'Temple Place'` now returns nothing.
>---
> dbus/dbus-bash-completion-helper.c |    2 +-
> dbus/dbus-gtool-test.h             |    2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
>diff --git a/dbus/dbus-bash-completion-helper.c b/dbus/dbus-bash-completion-helper.c
>index 022c722..50ca47a 100644
>--- a/dbus/dbus-bash-completion-helper.c
>+++ b/dbus/dbus-bash-completion-helper.c
>@@ -15,7 +15,7 @@
>  *
>  * 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
>+ * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
>  *
>  */
> 
>diff --git a/dbus/dbus-gtool-test.h b/dbus/dbus-gtool-test.h
>index 971264e..b8dbf31 100644
>--- a/dbus/dbus-gtool-test.h
>+++ b/dbus/dbus-gtool-test.h
>@@ -17,7 +17,7 @@
>  * 
>  * 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
>+ * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
>  *
>  */
> 
>-- 
>1.6.2.4
>

Actions: View | Splinter Review

Attachments on bug 20936: 24356 | 25183 | 25184 | 26588

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.