Detlev Zundel wrote on 2010-04-08 18:06:40:
>
> Hi Jocke,
Hi again :)
>
> [...]
>
> > Since an escape char appear to exist, one should be able to use it much
> > like you
> > did above so I don't think that any use case disappears. Instead the common
> > usage
> > becomes simpler and the so fa
Hi Jocke,
[...]
> Since an escape char appear to exist, one should be able to use it much like
> you
> did above so I don't think that any use case disappears. Instead the common
> usage
> becomes simpler and the so far artificial use case needs an extra escape char.
Hm. I have to admit that
Detlev Zundel wrote on 2010-04-08 12:00:05:
>
> Hi Jocke,
Hi Detlev :)
>
> >> > > To me it looks like the new code would indeed do a "greedy"
> >> > > substitution
> >> > > only stopping when no more substitutions can be done. This is very
> >> > > un-unixy and thus not something I'd like to s
Hi Jocke,
>> > > To me it looks like the new code would indeed do a "greedy" substitution
>> > > only stopping when no more substitutions can be done. This is very
>> > > un-unixy and thus not something I'd like to see as a default behaviour.
>> >
>> > Why not? What is gained by the current metho
Wolfgang Denk wrote on 2010-04-01 20:27:47:
>
> Dear Joakim Tjernlund,
>
> In message 005e9...@transmode.se> you wrote:
> >
> > > To me it looks like the new code would indeed do a "greedy" substitution
> > > only stopping when no more substitutions can be done. This is very
> > > un-unixy and t
Dear Joakim Tjernlund,
In message
you
wrote:
>
> > To me it looks like the new code would indeed do a "greedy" substitution
> > only stopping when no more substitutions can be done. This is very
> > un-unixy and thus not something I'd like to see as a default behaviour.
>
> Why not? What is g
Detlev Zundel wrote on 2010-04-01 16:56:40:
>
> Hi Jocke,
>
> >> > > Hm... will this not make escaping impossible? Assume you want to pass
> >> > >
> >> > >arg=${name}
> >> > >
> >> > > to Linux. How would you escape this so it does NOT get expanded if
> >> > > you run process_macros() arbitra
Hi Jocke,
>> > > Hm... will this not make escaping impossible? Assume you want to pass
>> > >
>> > >arg=${name}
>> > >
>> > > to Linux. How would you escape this so it does NOT get expanded if
>> > > you run process_macros() arbitrarily often?
>> >
>> > Possibly, I never needed that though.
>>
Wolfgang Denk wrote on 2010-04-01 15:05:29:
>
> Dear Joakim Tjernlund,
>
> In message 00471...@transmode.se> you wrote:
> >
> > > I don't think you ever posted this before. I cannot find any trace of
> > > such a patch - not in the public archives nor locally.
> >
> > I think I did, but this woul
Dear Joakim Tjernlund,
In message
you
wrote:
>
> > I don't think you ever posted this before. I cannot find any trace of
> > such a patch - not in the public archives nor locally.
>
> I think I did, but this would have been late 2001 or 2002 I think :)
> Not 100% sure about the date since the
Wolfgang Denk wrote on 2010-04-01 14:47:45:
>
> Dear Joakim Tjernlund,
>
> In message 0044d...@transmode.se> you wrote:
> >
> > linuxip=ip=$(ipaddr)::$(gatewayip):$(netmask):$(hostname):$(linuxif):off
> > tboot=setenv bootargs $(linuxroot) $(linuxip) $(extra);tftp 10; bootm
> > 10
> >
Dear Joakim Tjernlund,
In message
you
wrote:
>
> linuxip=ip=$(ipaddr)::$(gatewayip):$(netmask):$(hostname):$(linuxif):off
> tboot=setenv bootargs $(linuxroot) $(linuxip) $(extra);tftp 10; bootm
> 10
>
> it was fairly simple to do but I don't think WD applied it since the old
> shel
>
> Hi Nitin,
>
> > Hi!
> >
> > I am doing env settings some thing like this,
> >
> > ROOT1=/dev/mmcblk0p1
> > ROOT2=/dev/mmcblk0p2
> > ROOT=${ROOT1}
> > bootargs1=console=ttyS0,115200n8 mem=256M noinitrd rw rootdelay=1 ${ROOT}
> >
> > when I say 'setenv bootargs ${bootargs1}', ${ROOT} gets resolve
Hi Nitin,
> Hi!
>
> I am doing env settings some thing like this,
>
> ROOT1=/dev/mmcblk0p1
> ROOT2=/dev/mmcblk0p2
> ROOT=${ROOT1}
> bootargs1=console=ttyS0,115200n8 mem=256M noinitrd rw rootdelay=1 ${ROOT}
>
> when I say 'setenv bootargs ${bootargs1}', ${ROOT} gets resolved to 'ROOT1',
> it does
Hi!
I am doing env settings some thing like this,
ROOT1=/dev/mmcblk0p1
ROOT2=/dev/mmcblk0p2
ROOT=${ROOT1}
bootargs1=console=ttyS0,115200n8 mem=256M noinitrd rw rootdelay=1 ${ROOT}
when I say 'setenv bootargs ${bootargs1}', ${ROOT} gets resolved to 'ROOT1', it
does not get completely resolved to
15 matches
Mail list logo
