From: "Nirbheek Chauhan" <nirbheek@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gnome:master commit in: scripts/
Date: Fri, 18 Feb 2011 04:40:42 +0000 (UTC) [thread overview]
Message-ID: <e8f8248dc43016a4ba518ad8bca716861f822065.nirbheek@gentoo> (raw)
commit: e8f8248dc43016a4ba518ad8bca716861f822065
Author: Nirbheek Chauhan <nirbheek <AT> gentoo <DOT> org>
AuthorDate: Fri Feb 18 03:48:04 2011 +0000
Commit: Nirbheek Chauhan <nirbheek <AT> gentoo <DOT> org>
CommitDate: Fri Feb 18 03:48:28 2011 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/gnome.git;a=commit;h=e8f8248d
scripts: fix shebang to use python2
---
scripts/bump-to-latest.py | 2 +-
scripts/find-keywordreq.py | 2 +-
scripts/gen_archlist.py | 2 +-
scripts/gir-rebuilder.py | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/scripts/bump-to-latest.py b/scripts/bump-to-latest.py
index 4eab4fd..acd4587 100755
--- a/scripts/bump-to-latest.py
+++ b/scripts/bump-to-latest.py
@@ -1,4 +1,4 @@
-#!/usr/bin/env python
+#!/usr/bin/env python2
# vim: set sw=4 sts=4 et :
# Author(s): Nirbheek Chauhan <nirbheek@gentoo.org>
#
diff --git a/scripts/find-keywordreq.py b/scripts/find-keywordreq.py
index 7f319f6..6b991a4 100644
--- a/scripts/find-keywordreq.py
+++ b/scripts/find-keywordreq.py
@@ -1,4 +1,4 @@
-#!/usr/bin/python
+#!/usr/bin/env python2
""" Helper module to print a list of needed keywords provided a list of cpv.
diff --git a/scripts/gen_archlist.py b/scripts/gen_archlist.py
index 2b68785..5d9dee5 100755
--- a/scripts/gen_archlist.py
+++ b/scripts/gen_archlist.py
@@ -1,4 +1,4 @@
-#!/usr/bin/env python
+#!/usr/bin/env python2
# vim: set sw=4 sts=4 et :
# Author(s): Nirbheek Chauhan <nirbheek@gentoo.org>
#
diff --git a/scripts/gir-rebuilder.py b/scripts/gir-rebuilder.py
index 7d4efd5..6cecd59 100755
--- a/scripts/gir-rebuilder.py
+++ b/scripts/gir-rebuilder.py
@@ -1,4 +1,4 @@
-#!/usr/bin/env python
+#!/usr/bin/env python2
# vim: set sts=4 sw=4 et tw=90 :
#
# Author(s): Nirbheek Chauhan <nirbheek@gentoo.org>
next reply other threads:[~2011-02-18 4:40 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 4:40 Nirbheek Chauhan [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-04 15:40 [gentoo-commits] proj/gnome:master commit in: scripts/ Nirbheek Chauhan
2011-03-12 20:10 Nirbheek Chauhan
2011-03-14 18:41 Nirbheek Chauhan
2011-03-15 13:08 Nirbheek Chauhan
2011-03-17 17:12 Nirbheek Chauhan
2011-03-18 8:23 Nirbheek Chauhan
2011-03-18 9:59 Nirbheek Chauhan
2011-03-20 8:11 Nirbheek Chauhan
2011-03-23 10:39 Gilles Dartiguelongue
2011-03-23 19:21 Gilles Dartiguelongue
2011-03-23 21:59 Nirbheek Chauhan
2011-03-23 21:59 Nirbheek Chauhan
2011-03-23 21:59 Nirbheek Chauhan
2011-03-26 1:58 Nirbheek Chauhan
2011-03-28 15:04 Nirbheek Chauhan
2011-03-28 16:15 Nirbheek Chauhan
2011-04-09 6:29 Nirbheek Chauhan
2011-04-13 9:57 Nirbheek Chauhan
2011-05-19 12:35 Gilles Dartiguelongue
2011-05-21 18:38 Nirbheek Chauhan
2011-07-12 21:15 Nirbheek Chauhan
2011-08-18 6:23 Nirbheek Chauhan
2012-04-01 19:12 Nirbheek Chauhan
2012-04-01 21:14 Nirbheek Chauhan
2018-01-10 3:25 Mart Raudsepp
2018-04-25 10:32 Mart Raudsepp
2019-02-07 11:58 Mart Raudsepp
2020-03-10 22:05 Matt Turner
2020-03-28 8:31 Mart Raudsepp
2020-04-03 19:42 Matt Turner
2020-04-03 19:42 Matt Turner
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=e8f8248dc43016a4ba518ad8bca716861f822065.nirbheek@gentoo \
--to=nirbheek@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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