On Sun, Feb 22, 2009 at 6:58 AM, Mike Frysinger wrote:
> i guess i used too many code words like "bash-4.0 is broken" and "workaround".
> i'll address this in the future by just mailing base-sys...@gentoo.org as they
> should be familiar with these insider terms.
Cool it with the war of words fol
On Saturday 21 February 2009 19:54:51 Mart Raudsepp wrote:
> On Sat, 2009-02-21 at 19:44 -0500, Mike Frysinger wrote:
> > On Saturday 21 February 2009 19:38:33 Mart Raudsepp wrote:
> > > On Sat, 2009-02-21 at 19:29 -0500, Mike Frysinger wrote:
> > > > On Saturday 21 February 2009 19:00:19 Mart Raud
On Sat, 21 Feb 2009 18:55:37 -0500
Mike Frysinger wrote:
> On Saturday 21 February 2009 18:38:55 Ryan Hill wrote:
> > On Sat, 21 Feb 2009 18:27:10 -0500 Mike Frysinger wrote:
> > > looks like bash-4.0 has broken semicolon escaping in subshells.
> > > this comes up when using find's -exec like we
On Sat, 2009-02-21 at 19:44 -0500, Mike Frysinger wrote:
> On Saturday 21 February 2009 19:38:33 Mart Raudsepp wrote:
> > On Sat, 2009-02-21 at 19:29 -0500, Mike Frysinger wrote:
> > > On Saturday 21 February 2009 19:00:19 Mart Raudsepp wrote:
> > > > On Sat, 2009-02-21 at 18:55 -0500, Mike Frysing
On Saturday 21 February 2009 19:38:33 Mart Raudsepp wrote:
> On Sat, 2009-02-21 at 19:29 -0500, Mike Frysinger wrote:
> > On Saturday 21 February 2009 19:00:19 Mart Raudsepp wrote:
> > > On Sat, 2009-02-21 at 18:55 -0500, Mike Frysinger wrote:
> > > > On Saturday 21 February 2009 18:38:55 Ryan Hill
On Sat, 2009-02-21 at 19:29 -0500, Mike Frysinger wrote:
> On Saturday 21 February 2009 19:00:19 Mart Raudsepp wrote:
> > On Sat, 2009-02-21 at 18:55 -0500, Mike Frysinger wrote:
> > > On Saturday 21 February 2009 18:38:55 Ryan Hill wrote:
> > > > On Sat, 21 Feb 2009 18:27:10 -0500 Mike Frysinger w
On Saturday 21 February 2009 19:00:19 Mart Raudsepp wrote:
> On Sat, 2009-02-21 at 18:55 -0500, Mike Frysinger wrote:
> > On Saturday 21 February 2009 18:38:55 Ryan Hill wrote:
> > > On Sat, 21 Feb 2009 18:27:10 -0500 Mike Frysinger wrote:
> > > > looks like bash-4.0 has broken semicolon escaping i
On Sat, 2009-02-21 at 18:55 -0500, Mike Frysinger wrote:
> On Saturday 21 February 2009 18:38:55 Ryan Hill wrote:
> > On Sat, 21 Feb 2009 18:27:10 -0500 Mike Frysinger wrote:
> > > looks like bash-4.0 has broken semicolon escaping in subshells. this
> > > comes up when using find's -exec like we d
On Saturday 21 February 2009 18:38:55 Ryan Hill wrote:
> On Sat, 21 Feb 2009 18:27:10 -0500 Mike Frysinger wrote:
> > looks like bash-4.0 has broken semicolon escaping in subshells. this
> > comes up when using find's -exec like we do in a few places in
> > eclasses: ls=$(find "$1" -name '*.po' -e
On Sat, 21 Feb 2009 18:27:10 -0500
Mike Frysinger wrote:
> looks like bash-4.0 has broken semicolon escaping in subshells. this
> comes up when using find's -exec like we do in a few places in
> eclasses: ls=$(find "$1" -name '*.po' -exec basename {} .po \;); shift
> you can work around the issu
looks like bash-4.0 has broken semicolon escaping in subshells. this comes up
when using find's -exec like we do in a few places in eclasses:
ls=$(find "$1" -name '*.po' -exec basename {} .po \;); shift
you can work around the issue in a couple of ways:
- quote the semicolon:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ulrich Mueller wrote:
>> On Thu, 19 Feb 2009, Brian Harring wrote:
>
>>> - "docompress" (without option or with option "-a"): add paths
>>> (directories or files) to the inclusion list
>>> - "docompress -x": add paths to the exclusion list
>
>> G
Hi,
I was writing a trivial version bump for net-voip/gnugk-2.2.8 (bug
#258518) but upstream added a file named p2pnat_license.txt (see
http://dpaste.com/123376/) This file looks to authorize gnugk project
(and users) to use p2pnat technology. gnugk is already licensed under
GPL-2 and I was wonder
13 matches
Mail list logo
