bashburn-info Mailing List for BashBurn (Page 10)
Brought to you by:
bashburn
Menu
▾
▴
bashburn-info — BashBurn mailing list
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
(3) |
Mar
|
Apr
(31) |
May
(5) |
Jun
(10) |
Jul
(21) |
Aug
(9) |
Sep
(9) |
Oct
(5) |
Nov
|
Dec
(17) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
(4) |
Feb
(7) |
Mar
|
Apr
(6) |
May
(1) |
Jun
|
Jul
|
Aug
(5) |
Sep
|
Oct
(7) |
Nov
(3) |
Dec
(17) |
| 2007 |
Jan
(2) |
Feb
|
Mar
(2) |
Apr
|
May
(1) |
Jun
(1) |
Jul
(7) |
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
| 2008 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
(1) |
Jun
|
Jul
(8) |
Aug
(114) |
Sep
(283) |
Oct
(128) |
Nov
|
Dec
(1) |
|
From: Nick W. <ni...@li...> - 2008-09-23 13:34:48
|
On Tue, 23 Sep 2008 09:27:05 -0400 (EDT) "Steven W. Orr" <st...@sy...> wrote: > On Tuesday, Sep 23rd 2008 at 05:38 -0000, quoth Nick Warne: > > =>Latest TRUNK > => > =>The grep function that pulls in the (regex'ed) fstab entries > doesn't =>work when you go to configure devices - I don't know why. > => > =>I have no advanced menu at all. > => > =>Nick > > Fixed. Something fgot dropped in the merge. Sorry. > OK, good stuff, but issue #1 still fails: --> The grep function that pulls in the (regex'ed) fstab entries --> doesn't work when you go to configure devices - I don't know why. There should be a list like /dev/cdrom /mnt/cdrom etc. appear at the bottom when entering configuration options 0) 1) and 2) Nick -- Free Software Foundation Associate Member 5508 |
|
From: Steven W. O. <st...@sy...> - 2008-09-23 13:30:18
|
On Tuesday, Sep 23rd 2008 at 05:42 -0000, quoth Nick Warne: =>On Tue, 23 Sep 2008 10:38:37 +0100 =>Nick Warne <ni...@li...> wrote: => =>> Latest TRUNK =>> =>> The grep function that pulls in the (regex'ed) fstab entries doesn't =>> work when you go to configure devices - I don't know why. =>> =>> I have no advanced menu at all. =>> => =>I also noticed in func/configfunc.sh (line 57) two: => => typeset -r old_IFS="$IFS" => typeset old_IFS="$IFS" => => =>I don't know which one is correct, but debugging the script output =>shouts about old_IFS being readonly. => =>Nick Also fixed. Thanks. -- steveo at syslang dot net TMMP1 http://frambors.syslang.net/ Do you have neighbors who are not frambors? Steve Orr Who should we vote for? http://steveo.syslang.net/electionrec-2008/ |
|
From: Steven W. O. <st...@sy...> - 2008-09-23 13:27:15
|
On Tuesday, Sep 23rd 2008 at 05:38 -0000, quoth Nick Warne: =>Latest TRUNK => =>The grep function that pulls in the (regex'ed) fstab entries doesn't =>work when you go to configure devices - I don't know why. => =>I have no advanced menu at all. => =>Nick Fixed. Something fgot dropped in the merge. Sorry. -- steveo at syslang dot net TMMP1 http://frambors.syslang.net/ Do you have neighbors who are not frambors? Steve Orr Who should we vote for? http://steveo.syslang.net/electionrec-2008/ |
|
From: A. L. <and...@gm...> - 2008-09-23 12:56:38
|
>> Well, a very simple way to get around that would be to ls -1 lang | >> grep -v TRANSLATION_RULE. >> Quick and dirty but it works. I'm not against creating a doc directory >> though if you like that solution better. > > OK, then why not add the TRANSLATION_RULE file to top level? Does it > need to be hidden away in lang/ directory? > > Nick > -- > Free Software Foundation Associate Member 5508 > No I see no reason why we can't add a doc directory at top level and add TRANSLATION_RULE (And other files like README, INSTALL etc.) to that. -- Anders Lindén http://bashburn.sf.net |
|
From: Nick W. <ni...@li...> - 2008-09-23 12:53:32
|
On Tue, 23 Sep 2008 14:31:59 +0200 "Anders Lindén" <and...@gm...> wrote: > > Good idea, but we need to do something here. > > > > As the file will need to be added to the install script, this then > > introduces an additional problem, as the way BB selects lang list in > > the configuration is to actually 'ls -1' the lang/ directory - this > > means TRANSLATION_RULE will show up as a language! > > > > So, either change the way the lang/directories are shown (somehow > > only list directories), OR, which I prefer, is to create a doc/ > > directory whereby all the related information files can live. > > > > Nick > > Well, a very simple way to get around that would be to ls -1 lang | > grep -v TRANSLATION_RULE. > Quick and dirty but it works. I'm not against creating a doc directory > though if you like that solution better. OK, then why not add the TRANSLATION_RULE file to top level? Does it need to be hidden away in lang/ directory? Nick -- Free Software Foundation Associate Member 5508 |
|
From: A. L. <and...@gm...> - 2008-09-23 12:33:29
|
Bah! Sent the reply to nick and not to the list. I suck. On Tue, Sep 23, 2008 at 2:05 PM, Nick Warne <ni...@li...> wrote: > On Tue, 23 Sep 2008 13:46:05 +0200 > Markus Kollmar <mar...@on...> wrote: > >> I have added a new file "TRANSLATION_RULE" in the base language >> directory of trunk. >> >> It should describe the process of translation. So we can work >> upon/with this "specification". >> But until now it is more a discussion-point - if someone has >> improvements or additional ideas, it's welcome. >> >> (Note, that I am not online until friday or saturday. So I can't >> response in this time, but when I am back I do so.) > > Good idea, but we need to do something here. > > As the file will need to be added to the install script, this then > introduces an additional problem, as the way BB selects lang list in > the configuration is to actually 'ls -1' the lang/ directory - this > means TRANSLATION_RULE will show up as a language! > > So, either change the way the lang/directories are shown (somehow only > list directories), OR, which I prefer, is to create a doc/ directory > whereby all the related information files can live. > Well, a very simple way to get around that would be to ls -1 lang | grep -v TRANSLATION_RULE. Quick and dirty but it works. I'm not against creating a doc directory though if you like that solution better. -- Anders Lindén http://bashburn.sf.net |
|
From: Nick W. <ni...@li...> - 2008-09-23 12:06:10
|
On Tue, 23 Sep 2008 13:46:05 +0200 Markus Kollmar <mar...@on...> wrote: > I have added a new file "TRANSLATION_RULE" in the base language > directory of trunk. > > It should describe the process of translation. So we can work > upon/with this "specification". > But until now it is more a discussion-point - if someone has > improvements or additional ideas, it's welcome. > > (Note, that I am not online until friday or saturday. So I can't > response in this time, but when I am back I do so.) Good idea, but we need to do something here. As the file will need to be added to the install script, this then introduces an additional problem, as the way BB selects lang list in the configuration is to actually 'ls -1' the lang/ directory - this means TRANSLATION_RULE will show up as a language! So, either change the way the lang/directories are shown (somehow only list directories), OR, which I prefer, is to create a doc/ directory whereby all the related information files can live. Nick -- Free Software Foundation Associate Member 5508 |
|
From: Markus K. <mar...@on...> - 2008-09-23 11:40:45
|
I have added a new file "TRANSLATION_RULE" in the base language directory of trunk. It should describe the process of translation. So we can work upon/with this "specification". But until now it is more a discussion-point - if someone has improvements or additional ideas, it's welcome. (Note, that I am not online until friday or saturday. So I can't response in this time, but when I am back I do so.) Markus Kollmar |
|
From: Nick W. <ni...@li...> - 2008-09-23 09:42:49
|
On Tue, 23 Sep 2008 10:38:37 +0100
Nick Warne <ni...@li...> wrote:
> Latest TRUNK
>
> The grep function that pulls in the (regex'ed) fstab entries doesn't
> work when you go to configure devices - I don't know why.
>
> I have no advanced menu at all.
>
I also noticed in func/configfunc.sh (line 57) two:
typeset -r old_IFS="$IFS"
typeset old_IFS="$IFS"
I don't know which one is correct, but debugging the script output
shouts about old_IFS being readonly.
Nick
--
Free Software Foundation Associate Member 5508
|
|
From: Nick W. <ni...@li...> - 2008-09-23 09:38:45
|
Latest TRUNK The grep function that pulls in the (regex'ed) fstab entries doesn't work when you go to configure devices - I don't know why. I have no advanced menu at all. Nick -- Free Software Foundation Associate Member 5508 |
|
From: Nick W. <ni...@li...> - 2008-09-23 06:34:39
|
On Mon, 22 Sep 2008 22:28:19 -0400 (EDT) "Steven W. Orr" <st...@sy...> wrote: > I just merged from release/3.0@533 to trunk. > > New rev is 561. I relaly hope I didn't screw anything up. > Seems OK. Right, what needs to happen is if any issues are found in RELEASE, then we fix it in TRUNK. When it is deemed fixed, then it gets moved to RELEASE branch to fix that issue. That way, the two trees are relatively related. As an aside, things in TRUNK may break certain things that fix the RELEASE tree, so we can't do anything until they are all fixed. The idea here is that soon RELEASE will be stable enough to use without errors. What was happening though, was RELEASE had fixes that TRUNK never had, so the development branch TRUNK was worse than/behind the RELEASE tree. Nick -- Free Software Foundation Associate Member 5508 |
|
From: Steven W. O. <st...@sy...> - 2008-09-23 02:28:38
|
I just merged from release/3.0@533 to trunk. New rev is 561. I relaly hope I didn't screw anything up. -- Time flies like the wind. Fruit flies like a banana. Stranger things have .0. happened but none stranger than this. Does your driver's license say Organ ..0 Donor?Black holes are where God divided by zero. Listen to me! We are all- 000 individuals! What if this weren't a hypothetical question? steveo at syslang.net |
|
From: Steven W. O. <st...@sy...> - 2008-09-22 19:21:55
|
On Monday, Sep 22nd 2008 at 14:40 -0000, quoth Nick Warne: =>On Mon, 22 Sep 2008 09:30:54 -0400 (EDT) =>"Steven W. Orr" <st...@sy...> wrote: => =>> On Monday, Sep 22nd 2008 at 04:49 -0000, quoth Nick Warne: =>> =>> =>BTW, forgot. I have been working and committing to TRUNK branch =>> only. => =>> =>Nick =>> =>> Right. And I've been adding to trunk for new functionality but if =>> it's a bug that needs to be fixed, I've been doing it in release/3.0 => =>Steve, => =>Leave RELEASE alone. Only update TRUNK. Once certain things are =>confirmed OK in TRUNK, then it can be moved to RELEASE. => =>I am using/working on TRUNK, and, of course, the changes you done to =>the RELEASE branch wasn't there. => =>Release shouldn't be touched at all until we can prove all works and =>then it gets moved. It's a deal. And later tonight, I'll merge the stuff I did in 3.0 over to trunk. Sorry for the confusion. -- steveo at syslang dot net TMMP1 http://frambors.syslang.net/ Do you have neighbors who are not frambors? Steve Orr Who should we vote for? http://steveo.syslang.net/electionrec-2008/ |
|
From: Nick W. <ni...@li...> - 2008-09-22 18:40:50
|
On Mon, 22 Sep 2008 09:30:54 -0400 (EDT) "Steven W. Orr" <st...@sy...> wrote: > On Monday, Sep 22nd 2008 at 04:49 -0000, quoth Nick Warne: > > =>BTW, forgot. I have been working and committing to TRUNK branch > only. => > =>Nick > > Right. And I've been adding to trunk for new functionality but if > it's a bug that needs to be fixed, I've been doing it in release/3.0 Steve, Leave RELEASE alone. Only update TRUNK. Once certain things are confirmed OK in TRUNK, then it can be moved to RELEASE. I am using/working on TRUNK, and, of course, the changes you done to the RELEASE branch wasn't there. Release shouldn't be touched at all until we can prove all works and then it gets moved. Nick -- Free Software Foundation Associate Member 5508 |
|
From: Steven W. O. <st...@sy...> - 2008-09-22 13:31:19
|
On Monday, Sep 22nd 2008 at 04:49 -0000, quoth Nick Warne: =>BTW, forgot. I have been working and committing to TRUNK branch only. => =>Nick Right. And I've been adding to trunk for new functionality but if it's a bug that needs to be fixed, I've been doing it in release/3.0 -- steveo at syslang dot net TMMP1 http://frambors.syslang.net/ Do you have neighbors who are not frambors? Steve Orr Who should we vote for? http://steveo.syslang.net/electionrec-2008/ |
|
From: Steven W. O. <st...@sy...> - 2008-09-22 13:29:50
|
On Monday, Sep 22nd 2008 at 03:58 -0000, quoth Nick Warne:
=>On Mon, 22 Sep 2008 08:42:24 +0100
=>Nick Warne <ni...@li...> wrote:
=>
=>> One thing at a time. I found that the author field still doesn't work
=>> right, but before we fix that...
=>>
=>> I removed my .bashburnrc file to see it a fresh install fixed it up
=>> (i.e. remove stale entries), and now I get this at init:
=>>
=>> There is no '/home/nick/.bashburnrc'.
=>> This is the file where BashBurn stores and reads its configuration.
=>> I will now attempt to create one.
=>> BBROOTDIR still has not been set.
=>>
=>> Reading the code I see there is a test on the file, and then BBROOTDIR
=>> gets fetched - but this has been removed, and I can't see where this
=>> value gets set now?
=>
=>OK, I fixed this up and checked in. I think it's right now.
=>
=>Nick
I'm confused. What I see is this:
524 > svn diff -r PREV BashBurn.sh
Index: BashBurn.sh
===================================================================
--- BashBurn.sh (revision 559)
+++ BashBurn.sh (working copy)
@@ -293,7 +293,7 @@
typeset BBROOTDIR='@@BBROOTDIR@@'
typeset TERMINAL_CHARACTERISTICS
-typeset HISTFILE=~/.bashburn_history
+typeset HISTFILE=$HOMEDIR/.bashburn_history
getconfigparam()
{
@@ -321,7 +321,7 @@
echo -e "$(date)\n" >> $bberrorlog
-# Create ~/.bashburnrc if it is not available
+# Create $HOMEDIR/.bashburnrc if it is not available
if [[ ! -r $BBCONFFILE ]]
then
cat <<EOF 1>&2
Is your ~ different from $HOME different from $HOMEDIR?
What you did should have no impact on the problem that you're describing.
Also, we *really* have to say what branch we're talking about. I found the
problem is trunk.
--
steveo at syslang dot net TMMP1 http://frambors.syslang.net/
Do you have neighbors who are not frambors? Steve Orr
Who should we vote for? http://steveo.syslang.net/electionrec-2008/
|
|
From: Nick W. <ni...@li...> - 2008-09-22 09:01:48
|
On Mon, 22 Sep 2008 08:58:12 +0100 Nick Warne <ni...@li...> wrote: > On Mon, 22 Sep 2008 08:42:24 +0100 > Nick Warne <ni...@li...> wrote: > > > One thing at a time. I found that the author field still doesn't > > work right, but before we fix that... > > > > I removed my .bashburnrc file to see it a fresh install fixed it up > > (i.e. remove stale entries), and now I get this at init: > > > > There is no '/home/nick/.bashburnrc'. > > This is the file where BashBurn stores and reads its configuration. > > I will now attempt to create one. > > BBROOTDIR still has not been set. > > > > Reading the code I see there is a test on the file, and then > > BBROOTDIR gets fetched - but this has been removed, and I can't see > > where this value gets set now? > > OK, I fixed this up and checked in. I think it's right now. Oh. I see Steve has done similar in the RELEASES branch... I didn't think of looking there first. We are starting to stomp on each other here. Nick -- Free Software Foundation Associate Member 5508 |
|
From: Nick W. <ni...@li...> - 2008-09-22 08:50:04
|
BTW, forgot. I have been working and committing to TRUNK branch only. Nick -- Free Software Foundation Associate Member 5508 |
|
From: Nick W. <ni...@li...> - 2008-09-22 08:08:29
|
On Sun, 21 Sep 2008 16:17:04 -0400 (EDT) "Steven W. Orr" <st...@sy...> wrote: > It looks like we have three different values that are being used for > IFS. There's the IFS=: which is needed to read a bbrc file. There's > IFS=@ used to pass uneval'd data to bbconfmenu. And now there's > IFS='|' which is needed to store configure_changes. (BTW, the > implication is that a config val may no longer contain an embedded > pipe char.) > > Nick, I hope this works. There's always one guy who screws up and > makes people aware that he's good at testing. I consider it a > blessing. ;-) The good news is that if you find anything wrong with > it, it should be easy to fix. (I try to never let people know that I > know how to get the printer working. ;-) > > On a related topic, I was just curious. Do people understand what IFS > is and what I'm doing with it? How it gets restored? etc...? > OK, still not right. Remove bashburnrc file, and first setting: Your Choice? |> Nick Warne /usr/lib/Bashburn/lib/func/configfunc.sh: line 131: Warne: command not found Second attempt immediately after: Your Choice? |> Nick Warne 8) Author (Nick)* Third attempt immediately after: Your Choice? |> Nick Warne 8) Author (Nick Warne)* Now try mail address: Your Choice? |> Nick Warne ni...@uk... 8) Author (Nick Warne nick)* Nick -- Free Software Foundation Associate Member 5508 |
|
From: Nick W. <ni...@li...> - 2008-09-22 07:58:33
|
On Mon, 22 Sep 2008 08:42:24 +0100 Nick Warne <ni...@li...> wrote: > One thing at a time. I found that the author field still doesn't work > right, but before we fix that... > > I removed my .bashburnrc file to see it a fresh install fixed it up > (i.e. remove stale entries), and now I get this at init: > > There is no '/home/nick/.bashburnrc'. > This is the file where BashBurn stores and reads its configuration. > I will now attempt to create one. > BBROOTDIR still has not been set. > > Reading the code I see there is a test on the file, and then BBROOTDIR > gets fetched - but this has been removed, and I can't see where this > value gets set now? OK, I fixed this up and checked in. I think it's right now. Nick -- Free Software Foundation Associate Member 5508 |
|
From: Nick W. <ni...@li...> - 2008-09-22 07:42:41
|
One thing at a time. I found that the author field still doesn't work right, but before we fix that... I removed my .bashburnrc file to see it a fresh install fixed it up (i.e. remove stale entries), and now I get this at init: There is no '/home/nick/.bashburnrc'. This is the file where BashBurn stores and reads its configuration. I will now attempt to create one. BBROOTDIR still has not been set. Reading the code I see there is a test on the file, and then BBROOTDIR gets fetched - but this has been removed, and I can't see where this value gets set now? Nick -- Free Software Foundation Associate Member 5508 |
|
From: Steven W. O. <st...@sy...> - 2008-09-22 04:09:06
|
On Sunday, Sep 21st 2008 at 20:12 -0000, quoth Anders Lind?n: =>Lots of error reports tonight :) => =>When I reset the options in the regular configure menu and then exit BB, =>the next time I enter the advanced config, all options are zeroed out. A =>reset in config should not affect the advanced options at all. I knew about this but I thought I'd save it for later. No such luck. It should be fixed in 3.0 rev 556. Now a reset of config params will not reset adv config params, and vice versa. TBD: I need to restore the comments in the bashburnrc file that used to be there. :-( -- steveo at syslang dot net TMMP1 http://frambors.syslang.net/ Do you have neighbors who are not frambors? Steve Orr Who should we vote for? http://steveo.syslang.net/electionrec-2008/ |
|
From: Steven W. O. <st...@sy...> - 2008-09-22 02:48:23
|
On Sunday, Sep 21st 2008 at 20:08 -0000, quoth Anders Lind?n: =>It also seems that in the regular configure menu, help text is only =>displayed in English, not the selected language. The menu itself is =>translated correctly though. => =>On Mon, 2008-09-22 at 01:14 +0200, Anders Lind?n wrote: =>> The advanced menu does not display any information anymore when =>> selecting an option. Did I break something or did you Steven? =>> This might fix the problem. I indirected once too many times in 3.0. -- steveo at syslang dot net TMMP1 http://frambors.syslang.net/ Do you have neighbors who are not frambors? Steve Orr Who should we vote for? http://steveo.syslang.net/electionrec-2008/ |
|
From: Steven W. O. <st...@sy...> - 2008-09-22 02:30:35
|
On Sunday, Sep 21st 2008 at 19:14 -0000, quoth Anders Lind?n: =>The advanced menu does not display any information anymore when =>selecting an option. Did I break something or did you Steven? If I select Advanced Options, none of the options in advanced have any information to display. Is there a point where they did? I looked as far back as Aug 31. I don't see any info text. BTW, all of the text in the advanced menu is literal, i.e., it's not ref'd symbolically and so will not be translated if BBLANG is not English. One more thing: If you find problems, please make sure to reference what branch you see the problem in. Thanks. -- steveo at syslang dot net TMMP1 http://frambors.syslang.net/ Do you have neighbors who are not frambors? Steve Orr Who should we vote for? http://steveo.syslang.net/electionrec-2008/ |
|
From: Steven W. O. <st...@sy...> - 2008-09-22 02:15:01
|
On Sunday, Sep 21st 2008 at 18:35 -0000, quoth Anders Lind?n:
=>Yeah thats pretty much what I meant. Telling the shell which characters
=>are to be used to separate fields.
=>
=>Question, why are you setting a new IFS and shortly after set it back to
=>the old IFS in loops?
=>Is it because programs used in the loop needs the original IFS to work
=>properly?
Correct. In some cases, it's actually *not* used, but it's good practice
to restore IFS right after you're done with it. Sometimes you end up using
it and you're not aware of it. I usually lose a few minutes chasing
problems when that happens. :-(
=>On another note, I noticed when starting the latest svn snapshot of BB,
=>it spits out an error message
=>that the command die does not exist. I'm guessing because you have not
=>sourced the needed file yet at that point.
Good catch. Fixed.
=>
=>
=>On Sun, 2008-09-21 at 18:20 -0400, Steven W. Orr wrote:
=>> On Sunday, Sep 21st 2008 at 16:34 -0000, quoth Anders Lind?n:
=>>
=>> =>Meh, I sent my reply to Steven and not the list. Reposting it here.
=>> =>
=>> =>If I'm not mistaken, IFS is something that is treated as a space or
=>> =>newline character no? You can set a character like @, : or | in our case
=>> =>to be treated as a whitespace to separate text fields?
=>> =>
=>> =>On Sun, 2008-09-21 at 16:17 -0400, Steven W. Orr wrote:
=>> =>> It looks like we have three different values that are being used for IFS.
=>> =>> There's the IFS=: which is needed to read a bbrc file. There's IFS=@ used
=>> =>> to pass uneval'd data to bbconfmenu. And now there's IFS='|' which is
=>> =>> needed to store configure_changes. (BTW, the implication is that a config
=>> =>> val may no longer contain an embedded pipe char.)
=>> =>>
=>> =>> Nick, I hope this works. There's always one guy who screws up and makes
=>> =>> people aware that he's good at testing. I consider it a blessing. ;-) The
=>> =>> good news is that if you find anything wrong with it, it should be easy to
=>> =>> fix. (I try to never let people know that I know how to get the printer
=>> =>> working. ;-)
=>> =>>
=>> =>> On a related topic, I was just curious. Do people understand what IFS is
=>> =>> and what I'm doing with it? How it gets restored? etc...?
=>>
=>> Close. IFS is used as the mechanism to tell bash how to parse text. For
=>> example, if I have
=>>
=>> foo='This is a string: It has some stuff in it. And it's 2:00PM.'
=>> then I can say
=>> set -- $foo
=>> After the set command,
=>> $1 will be 'This'
=>> $2 will be 'is'
=>> $3 will be 'a'
=>> and $4 will be 'string:'
=>>
=>> But if I was to say
=>> IFS=:
=>> set -- $foo
=>> then $1 will be 'This is a string'
=>> $2 will be ' It has some stuff in it. And it's 2'
=>> and $3 will be '00PM.'
=>>
=>> In addition, lists will be taken apart differently (for example is for
=>> loops, depending on IFS. All the values of IFS that I work with are local
=>> copies in subroutines. e.g.,
=>>
=>> subX()
=>> {
=>> typeset old_IFS="$IFS"
=>> typeset IFS="$old_IFS"
=>>
=>> The default value for IFS is whitespace
=>>
=>> 533 > echo "$IFS" | od -bc
=>> 0000000 040 011 012 012
=>> \t \n \n
=>> 0000004
=>>
=>>
=>--
=>Anders Lind?n
=>http://bashburn.sf.net
=>
=>
=>-------------------------------------------------------------------------
=>This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
=>Build the coolest Linux based applications with Moblin SDK & win great prizes
=>Grand prize is a trip for two to an Open Source event anywhere in the world
=>http://moblin-contest.org/redirect.php?banner_id=100&url=/
=>_______________________________________________
=>Bashburn-info mailing list
=>Bas...@li...
=>https://lists.sourceforge.net/lists/listinfo/bashburn-info
=>
--
steveo at syslang dot net TMMP1 http://frambors.syslang.net/
Do you have neighbors who are not frambors? Steve Orr
Who should we vote for? http://steveo.syslang.net/electionrec-2008/
|
8 messages has been excluded from this view by a project administrator.
