public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mike Frysinger (vapier)" <vapier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in sys-apps/less/files: lesspipe.sh
Date: Mon, 09 Feb 2009 18:58:11 +0000	[thread overview]
Message-ID: <E1LWbKd-0007Tn-1S@stork.gentoo.org> (raw)

vapier      09/02/09 18:58:11

  Modified:             lesspipe.sh
  Log:
  force tr to C locale so upper->lower always works as expected

Revision  Changes    Path
1.33                 sys-apps/less/files/lesspipe.sh

file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-apps/less/files/lesspipe.sh?rev=1.33&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-apps/less/files/lesspipe.sh?rev=1.33&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-apps/less/files/lesspipe.sh?r1=1.32&r2=1.33

Index: lesspipe.sh
===================================================================
RCS file: /var/cvsroot/gentoo-x86/sys-apps/less/files/lesspipe.sh,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- lesspipe.sh	2 Feb 2009 19:44:13 -0000	1.32
+++ lesspipe.sh	9 Feb 2009 18:58:10 -0000	1.33
@@ -217,7 +217,7 @@
 		# Maybe we didn't match due to case issues ...
 		if [[ ${recur} == 0 ]] ; then
 			recur=1
-			lesspipe "$1" "$(echo $1 | tr '[:upper:]' '[:lower:]')"
+			lesspipe "$1" "$(echo $1 | LC_ALL=C tr '[:upper:]' '[:lower:]')"
 
 		# Maybe we didn't match because the file is named weird ...
 		else
@@ -234,7 +234,7 @@
 	echo "Usage: lesspipe.sh <file>"
 elif [[ $1 == "-V" || $1 == "--version" ]] ; then
 	Id="cvsid"
-	cvsid="$Id: lesspipe.sh,v 1.32 2009/02/02 19:44:13 vapier Exp $"
+	cvsid="$Id: lesspipe.sh,v 1.33 2009/02/09 18:58:10 vapier Exp $"
 	cat <<-EOF
 		$cvsid
 		Copyright 2001-2009 Gentoo Foundation






             reply	other threads:[~2009-02-09 18:58 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-09 18:58 Mike Frysinger (vapier) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-12-31  2:25 [gentoo-commits] gentoo-x86 commit in sys-apps/less/files: lesspipe.sh Mike Frysinger (vapier)
2013-08-06 21:35 Mike Frysinger (vapier)
2013-04-29 18:37 Mike Frysinger (vapier)
2013-03-24  5:01 Mike Frysinger (vapier)
2012-11-22  4:20 Mike Frysinger (vapier)
2012-09-04 19:13 Mike Frysinger (vapier)
2011-12-07 20:29 Mike Frysinger (vapier)
2011-10-09 19:19 Mike Frysinger (vapier)
2011-01-20  3:26 Mike Frysinger (vapier)
2011-01-18 20:26 Mike Frysinger (vapier)
2010-12-31 20:52 Mike Frysinger (vapier)
2010-12-31 20:51 Mike Frysinger (vapier)
2010-08-24  1:01 Mike Frysinger (vapier)
2010-03-23 20:54 Mike Frysinger (vapier)
2010-02-14 17:11 Mike Frysinger (vapier)
2010-02-10 23:57 Mike Frysinger (vapier)
2010-02-05  6:36 Mike Frysinger (vapier)
2009-10-22  7:53 Mike Frysinger (vapier)
2009-04-11 23:20 Mike Frysinger (vapier)
2009-03-13  6:06 Mike Frysinger (vapier)
2009-02-02 19:44 Mike Frysinger (vapier)
2008-12-27  5:03 Mike Frysinger (vapier)
2008-05-30 23:54 Mike Frysinger (vapier)
2008-04-18 19:58 Mike Frysinger (vapier)
2008-04-16 17:33 Mike Frysinger (vapier)
2008-03-16 13:01 Mike Frysinger (vapier)
2007-11-06  2:19 Mike Frysinger (vapier)
2007-11-06  1:58 Mike Frysinger (vapier)

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=E1LWbKd-0007Tn-1S@stork.gentoo.org \
    --to=vapier@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