From: Serge L. <ser...@gm...> - 2011-07-06 04:20:51
|
Hi, It looks like I missed instruction/howto for DL git repo. I don't post the changes very often of course, but anyway - I wouldn’t like to bother Heiko with tracking and resubmitting those changes. If you know where I can find the manual, please let me know. Thanks, Serge |
From: Heiko Z. <he...@zu...> - 2011-07-06 12:18:09
|
Hey, Below are some commands from the buildroot mailinglist, which I used initially to figure out how this git thing works. If you didn't use git before then I'm sure there will be questions, so feel free to ask. This is the URL you'll need to use: ssh://use...@de.../gitroot/devil-linux/devil-linux of course replace username with your SF username. Here's some additional documentation: http://sourceforge.net/scm/?type=git&group_id=34096 You find the DL specific stuff under target/devil-linux. There's also a default DL config under config/ which will compile a working x86_64 version. There are quite a few buildroot specific things if you want to add new scripts. A lot of information can be found here: http://buildroot.uclibc.org/ I usually send any non-DL specific changes to buildroot, so they can incorporate it. They're quite picky about what goes in and the quality of the script (the 2nd one being a good thing). Heiko ----- Forwarded message from Thomas Petazzoni <tho...@fr...> ----- Date: Sun, 5 Dec 2010 09:17:24 +0100 From: Thomas Petazzoni <tho...@fr...> Subject: [Buildroot] How to contribute to Buildroot with Git To: bui...@bu... On Sat, 4 Dec 2010 16:09:00 -0800 (PST) Justin Mark <oi...@ya...> wrote: > I can build libgee with buildroot in my workspace, how should I > submit the patch for review? post the patch here or directly do it > from git? Can someone give me some details since I don't know much > about git? The best is to use Git. Here is a simplified version of the Git workflow that I use to work with Buildroot: 1) Clone (to be done only once) git clone git://git.busybox.net/buildroot 2) Configure Git (to be done only once) Then tell git who you are : git config --global user.name "Firstname Lastname" git config --global user.email fir...@so... And tell git how to send emails : git config --global sendemail.smtpserver mysmtpserver And to avoid chained reply : git config --global sendemail.chainreplyto false 3) Create a branch to work on your topic (to be done for every separate topic you'd like to work with) git checkout -b mytopic Note that this also switches immediatly to the new 'mytopic' branch. You can run 'git branch' at any time to know on which branch you are. 4) Make some modifications, for one particuler subtopic (like adding the vala compiler) 5) Commit those modifications git commit -s -a And enter an appropriate commit log. If you created new files, add them with "git add". Then go back to step 4 for the other changes you want to do, or proceed to step 6 if you're done with your changes. 6) Review your changes git log -p master.. 7) Prepare patches for your changes git format-patch HEAD This will generate a set of 000X-*.patch files in the Buildroot directory 8) Send your patches to the list git send-email --to bui...@uc... --compose *.patch And you're done. If while reviewing your commits you find that you need to merge some of them (because you did some mistakes that you fixed later and you don't want the world to know about your mistakes), then you have to use the rebasing feature of git: git rebase -i master Git will open up a text editor with the list of your commits. You can edit this file to change the order of the commits, or to change the action taken on a particular commit (see the file itself for documentation on those actions). A typical thing is : pick SOMEGITHASH package: add foobar pick SOMEGITHASH package: add barfoo pick SOMEGITHASH I did something wrong in add foobar, merge me So obviously you want the last commit to be merged into the first one, so that nobody knows you did some mistakes during your development. So, turn those three lines into the following ones: pick SOMEGITHASH package: add foobar fixup SOMEGITHASH I did something wrong in add foobar, merge me pick SOMEGITHASH package: add barfoo And exit the text editor. Git will reorganize your commits, and you'll end up with just two commits. Don't hesitate to ask questions if you have issues, Thomas -- Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com _______________________________________________ buildroot mailing list bui...@bu... http://lists.busybox.net/mailman/listinfo/buildroot ----- End forwarded message ----- -- Regards Heiko Zuerker http://www.devil-linux.org Quoting Serge Leschinsky <ser...@gm...>: > Hi, > > It looks like I missed instruction/howto for DL git repo. I don't post the > changes very often of course, but anyway - I wouldn?t like to > bother Heiko with > tracking and resubmitting those changes. If you know where I can find the > manual, please let me know. > > > Thanks, > Serge > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > Devil-linux-develop mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-develop -- Regards Heiko Zuerker http://www.devil-linux.org |
From: Heiko Z. <he...@zu...> - 2011-07-06 13:29:54
|
Completely forgot, there's a new lfssystem for DL 1.5. I'll upload it to the FTP server. Heiko Quoting Heiko Zuerker <he...@zu...>: > Hey, > > Below are some commands from the buildroot mailinglist, which I used > initially to figure out how this git thing works. > If you didn't use git before then I'm sure there will be questions, so > feel free to ask. > > This is the URL you'll need to use: > ssh://use...@de.../gitroot/devil-linux/devil-linux > of course replace username with your SF username. > > Here's some additional documentation: > http://sourceforge.net/scm/?type=git&group_id=34096 > > You find the DL specific stuff under target/devil-linux. > There's also a default DL config under config/ which will compile a > working x86_64 version. > > There are quite a few buildroot specific things if you want to add new > scripts. A lot of information can be found here: > http://buildroot.uclibc.org/ > I usually send any non-DL specific changes to buildroot, so they can > incorporate it. They're quite picky about what goes in and the quality > of the script (the 2nd one being a good thing). > > Heiko > > ----- Forwarded message from Thomas Petazzoni > <tho...@fr...> ----- > Date: Sun, 5 Dec 2010 09:17:24 +0100 > From: Thomas Petazzoni <tho...@fr...> > Subject: [Buildroot] How to contribute to Buildroot with Git > To: bui...@bu... > > On Sat, 4 Dec 2010 16:09:00 -0800 (PST) > Justin Mark <oi...@ya...> wrote: > >> I can build libgee with buildroot in my workspace, how should I >> submit the patch for review? post the patch here or directly do it >> from git? Can someone give me some details since I don't know much >> about git? > > The best is to use Git. Here is a simplified version of the Git workflow > that I use to work with Buildroot: > > 1) Clone (to be done only once) > > git clone git://git.busybox.net/buildroot > > 2) Configure Git (to be done only once) > > Then tell git who you are : > > git config --global user.name "Firstname Lastname" > git config --global user.email fir...@so... > > And tell git how to send emails : > > git config --global sendemail.smtpserver mysmtpserver > > And to avoid chained reply : > > git config --global sendemail.chainreplyto false > > 3) Create a branch to work on your topic (to be done for every > separate topic you'd like to work with) > > git checkout -b mytopic > > Note that this also switches immediatly to the new 'mytopic' > branch. You can run 'git branch' at any time to know on which > branch you are. > > 4) Make some modifications, for one particuler subtopic (like adding > the vala compiler) > > 5) Commit those modifications > > git commit -s -a > > And enter an appropriate commit log. > > If you created new files, add them with "git add". > > Then go back to step 4 for the other changes you want to do, or > proceed to step 6 if you're done with your changes. > > 6) Review your changes > > git log -p master.. > > 7) Prepare patches for your changes > > git format-patch HEAD > > This will generate a set of 000X-*.patch files in the Buildroot > directory > > 8) Send your patches to the list > > git send-email --to bui...@uc... --compose *.patch > > And you're done. > > If while reviewing your commits you find that you need to merge some of > them (because you did some mistakes that you fixed later and you don't > want the world to know about your mistakes), then you have to use the > rebasing feature of git: > > git rebase -i master > > Git will open up a text editor with the list of your commits. You can > edit this file to change the order of the commits, or to change the > action taken on a particular commit (see the file itself for > documentation on those actions). A typical thing is : > > pick SOMEGITHASH package: add foobar > pick SOMEGITHASH package: add barfoo > pick SOMEGITHASH I did something wrong in add foobar, merge me > > So obviously you want the last commit to be merged into the first one, > so that nobody knows you did some mistakes during your development. So, > turn those three lines into the following ones: > > pick SOMEGITHASH package: add foobar > fixup SOMEGITHASH I did something wrong in add foobar, merge me > pick SOMEGITHASH package: add barfoo > > And exit the text editor. Git will reorganize your commits, and you'll > end up with just two commits. > > Don't hesitate to ask questions if you have issues, > > Thomas > -- > Thomas Petazzoni, Free Electrons > Kernel, drivers, real-time and embedded Linux > development, consulting, training and support. > http://free-electrons.com > _______________________________________________ > buildroot mailing list > bui...@bu... > http://lists.busybox.net/mailman/listinfo/buildroot > > ----- End forwarded message ----- > > -- > > Regards > Heiko Zuerker > http://www.devil-linux.org > > Quoting Serge Leschinsky <ser...@gm...>: > >> Hi, >> >> It looks like I missed instruction/howto for DL git repo. I don't post the >> changes very often of course, but anyway - I wouldn?t like to >> bother Heiko with >> tracking and resubmitting those changes. If you know where I can find the >> manual, please let me know. >> >> >> Thanks, >> Serge >> >> ------------------------------------------------------------------------------ >> All of the data generated in your IT infrastructure is seriously valuable. >> Why? It contains a definitive record of application performance, security >> threats, fraudulent activity, and more. Splunk takes this data and makes >> sense of it. IT sense. And common sense. >> http://p.sf.net/sfu/splunk-d2d-c2 >> _______________________________________________ >> Devil-linux-develop mailing list >> Dev...@li... >> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop > > > -- > > Regards > Heiko Zuerker > http://www.devil-linux.org > > > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > Devil-linux-develop mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-develop -- Regards Heiko Zuerker http://www.devil-linux.org |
From: Heiko Z. <he...@zu...> - 2011-07-06 16:16:18
|
The file is uploading and will be available 30 minutes after I sent this email. ftp://ftp.devil-linux.org/pub/devel/sources/lfssystem-for-DL-1.5/ Heiko Quoting Heiko Zuerker <he...@zu...>: > Completely forgot, there's a new lfssystem for DL 1.5. > I'll upload it to the FTP server. > > Heiko > > Quoting Heiko Zuerker <he...@zu...>: > >> Hey, >> >> Below are some commands from the buildroot mailinglist, which I used >> initially to figure out how this git thing works. >> If you didn't use git before then I'm sure there will be questions, so >> feel free to ask. >> >> This is the URL you'll need to use: >> ssh://use...@de.../gitroot/devil-linux/devil-linux >> of course replace username with your SF username. >> >> Here's some additional documentation: >> http://sourceforge.net/scm/?type=git&group_id=34096 >> >> You find the DL specific stuff under target/devil-linux. >> There's also a default DL config under config/ which will compile a >> working x86_64 version. >> >> There are quite a few buildroot specific things if you want to add new >> scripts. A lot of information can be found here: >> http://buildroot.uclibc.org/ >> I usually send any non-DL specific changes to buildroot, so they can >> incorporate it. They're quite picky about what goes in and the quality >> of the script (the 2nd one being a good thing). >> >> Heiko >> >> ----- Forwarded message from Thomas Petazzoni >> <tho...@fr...> ----- >> Date: Sun, 5 Dec 2010 09:17:24 +0100 >> From: Thomas Petazzoni <tho...@fr...> >> Subject: [Buildroot] How to contribute to Buildroot with Git >> To: bui...@bu... >> >> On Sat, 4 Dec 2010 16:09:00 -0800 (PST) >> Justin Mark <oi...@ya...> wrote: >> >>> I can build libgee with buildroot in my workspace, how should I >>> submit the patch for review? post the patch here or directly do it >>> from git? Can someone give me some details since I don't know much >>> about git? >> >> The best is to use Git. Here is a simplified version of the Git workflow >> that I use to work with Buildroot: >> >> 1) Clone (to be done only once) >> >> git clone git://git.busybox.net/buildroot >> >> 2) Configure Git (to be done only once) >> >> Then tell git who you are : >> >> git config --global user.name "Firstname Lastname" >> git config --global user.email fir...@so... >> >> And tell git how to send emails : >> >> git config --global sendemail.smtpserver mysmtpserver >> >> And to avoid chained reply : >> >> git config --global sendemail.chainreplyto false >> >> 3) Create a branch to work on your topic (to be done for every >> separate topic you'd like to work with) >> >> git checkout -b mytopic >> >> Note that this also switches immediatly to the new 'mytopic' >> branch. You can run 'git branch' at any time to know on which >> branch you are. >> >> 4) Make some modifications, for one particuler subtopic (like adding >> the vala compiler) >> >> 5) Commit those modifications >> >> git commit -s -a >> >> And enter an appropriate commit log. >> >> If you created new files, add them with "git add". >> >> Then go back to step 4 for the other changes you want to do, or >> proceed to step 6 if you're done with your changes. >> >> 6) Review your changes >> >> git log -p master.. >> >> 7) Prepare patches for your changes >> >> git format-patch HEAD >> >> This will generate a set of 000X-*.patch files in the Buildroot >> directory >> >> 8) Send your patches to the list >> >> git send-email --to bui...@uc... --compose *.patch >> >> And you're done. >> >> If while reviewing your commits you find that you need to merge some of >> them (because you did some mistakes that you fixed later and you don't >> want the world to know about your mistakes), then you have to use the >> rebasing feature of git: >> >> git rebase -i master >> >> Git will open up a text editor with the list of your commits. You can >> edit this file to change the order of the commits, or to change the >> action taken on a particular commit (see the file itself for >> documentation on those actions). A typical thing is : >> >> pick SOMEGITHASH package: add foobar >> pick SOMEGITHASH package: add barfoo >> pick SOMEGITHASH I did something wrong in add foobar, merge me >> >> So obviously you want the last commit to be merged into the first one, >> so that nobody knows you did some mistakes during your development. So, >> turn those three lines into the following ones: >> >> pick SOMEGITHASH package: add foobar >> fixup SOMEGITHASH I did something wrong in add foobar, merge me >> pick SOMEGITHASH package: add barfoo >> >> And exit the text editor. Git will reorganize your commits, and you'll >> end up with just two commits. >> >> Don't hesitate to ask questions if you have issues, >> >> Thomas >> -- >> Thomas Petazzoni, Free Electrons >> Kernel, drivers, real-time and embedded Linux >> development, consulting, training and support. >> http://free-electrons.com >> _______________________________________________ >> buildroot mailing list >> bui...@bu... >> http://lists.busybox.net/mailman/listinfo/buildroot >> >> ----- End forwarded message ----- >> >> -- >> >> Regards >> Heiko Zuerker >> http://www.devil-linux.org >> >> Quoting Serge Leschinsky <ser...@gm...>: >> >>> Hi, >>> >>> It looks like I missed instruction/howto for DL git repo. I don't post the >>> changes very often of course, but anyway - I wouldn?t like to >>> bother Heiko with >>> tracking and resubmitting those changes. If you know where I can find the >>> manual, please let me know. >>> >>> >>> Thanks, >>> Serge >>> >>> ------------------------------------------------------------------------------ >>> All of the data generated in your IT infrastructure is seriously valuable. >>> Why? It contains a definitive record of application performance, security >>> threats, fraudulent activity, and more. Splunk takes this data and makes >>> sense of it. IT sense. And common sense. >>> http://p.sf.net/sfu/splunk-d2d-c2 >>> _______________________________________________ >>> Devil-linux-develop mailing list >>> Dev...@li... >>> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop >> >> >> -- >> >> Regards >> Heiko Zuerker >> http://www.devil-linux.org >> >> >> >> ------------------------------------------------------------------------------ >> All of the data generated in your IT infrastructure is seriously valuable. >> Why? It contains a definitive record of application performance, security >> threats, fraudulent activity, and more. Splunk takes this data and makes >> sense of it. IT sense. And common sense. >> http://p.sf.net/sfu/splunk-d2d-c2 >> _______________________________________________ >> Devil-linux-develop mailing list >> Dev...@li... >> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop > > > -- > > Regards > Heiko Zuerker > http://www.devil-linux.org > > > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > Devil-linux-develop mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-develop -- Regards Heiko Zuerker http://www.devil-linux.org |
From: Serge L. <ser...@gm...> - 2011-07-07 03:47:08
|
Heiko, Thank you! Serge On 07/06/2011 08:16 AM, Heiko Zuerker wrote: > The file is uploading and will be available 30 minutes after I sent > this email. > > ftp://ftp.devil-linux.org/pub/devel/sources/lfssystem-for-DL-1.5/ > > Heiko > > Quoting Heiko Zuerker<he...@zu...>: > >> Completely forgot, there's a new lfssystem for DL 1.5. >> I'll upload it to the FTP server. >> >> Heiko >> >> Quoting Heiko Zuerker<he...@zu...>: >> >>> Hey, >>> >>> Below are some commands from the buildroot mailinglist, which I used >>> initially to figure out how this git thing works. >>> If you didn't use git before then I'm sure there will be questions, so >>> feel free to ask. >>> >>> This is the URL you'll need to use: >>> ssh://use...@de.../gitroot/devil-linux/devil-linux >>> of course replace username with your SF username. >>> >>> Here's some additional documentation: >>> http://sourceforge.net/scm/?type=git&group_id=34096 >>> >>> You find the DL specific stuff under target/devil-linux. >>> There's also a default DL config under config/ which will compile a >>> working x86_64 version. >>> >>> There are quite a few buildroot specific things if you want to add new >>> scripts. A lot of information can be found here: >>> http://buildroot.uclibc.org/ >>> I usually send any non-DL specific changes to buildroot, so they can >>> incorporate it. They're quite picky about what goes in and the quality >>> of the script (the 2nd one being a good thing). >>> >>> Heiko >>> >>> ----- Forwarded message from Thomas Petazzoni >>> <tho...@fr...> ----- >>> Date: Sun, 5 Dec 2010 09:17:24 +0100 >>> From: Thomas Petazzoni<tho...@fr...> >>> Subject: [Buildroot] How to contribute to Buildroot with Git >>> To: bui...@bu... >>> >>> On Sat, 4 Dec 2010 16:09:00 -0800 (PST) >>> Justin Mark<oi...@ya...> wrote: >>> >>>> I can build libgee with buildroot in my workspace, how should I >>>> submit the patch for review? post the patch here or directly do it >>>> from git? Can someone give me some details since I don't know much >>>> about git? >>> >>> The best is to use Git. Here is a simplified version of the Git workflow >>> that I use to work with Buildroot: >>> >>> 1) Clone (to be done only once) >>> >>> git clone git://git.busybox.net/buildroot >>> >>> 2) Configure Git (to be done only once) >>> >>> Then tell git who you are : >>> >>> git config --global user.name "Firstname Lastname" >>> git config --global user.email fir...@so... >>> >>> And tell git how to send emails : >>> >>> git config --global sendemail.smtpserver mysmtpserver >>> >>> And to avoid chained reply : >>> >>> git config --global sendemail.chainreplyto false >>> >>> 3) Create a branch to work on your topic (to be done for every >>> separate topic you'd like to work with) >>> >>> git checkout -b mytopic >>> >>> Note that this also switches immediatly to the new 'mytopic' >>> branch. You can run 'git branch' at any time to know on which >>> branch you are. >>> >>> 4) Make some modifications, for one particuler subtopic (like adding >>> the vala compiler) >>> >>> 5) Commit those modifications >>> >>> git commit -s -a >>> >>> And enter an appropriate commit log. >>> >>> If you created new files, add them with "git add". >>> >>> Then go back to step 4 for the other changes you want to do, or >>> proceed to step 6 if you're done with your changes. >>> >>> 6) Review your changes >>> >>> git log -p master.. >>> >>> 7) Prepare patches for your changes >>> >>> git format-patch HEAD >>> >>> This will generate a set of 000X-*.patch files in the Buildroot >>> directory >>> >>> 8) Send your patches to the list >>> >>> git send-email --to bui...@uc... --compose *.patch >>> >>> And you're done. >>> >>> If while reviewing your commits you find that you need to merge some of >>> them (because you did some mistakes that you fixed later and you don't >>> want the world to know about your mistakes), then you have to use the >>> rebasing feature of git: >>> >>> git rebase -i master >>> >>> Git will open up a text editor with the list of your commits. You can >>> edit this file to change the order of the commits, or to change the >>> action taken on a particular commit (see the file itself for >>> documentation on those actions). A typical thing is : >>> >>> pick SOMEGITHASH package: add foobar >>> pick SOMEGITHASH package: add barfoo >>> pick SOMEGITHASH I did something wrong in add foobar, merge me >>> >>> So obviously you want the last commit to be merged into the first one, >>> so that nobody knows you did some mistakes during your development. So, >>> turn those three lines into the following ones: >>> >>> pick SOMEGITHASH package: add foobar >>> fixup SOMEGITHASH I did something wrong in add foobar, merge me >>> pick SOMEGITHASH package: add barfoo >>> >>> And exit the text editor. Git will reorganize your commits, and you'll >>> end up with just two commits. >>> >>> Don't hesitate to ask questions if you have issues, >>> >>> Thomas >>> -- >>> Thomas Petazzoni, Free Electrons >>> Kernel, drivers, real-time and embedded Linux >>> development, consulting, training and support. >>> http://free-electrons.com >>> _______________________________________________ >>> buildroot mailing list >>> bui...@bu... >>> http://lists.busybox.net/mailman/listinfo/buildroot >>> >>> ----- End forwarded message ----- >>> >>> -- >>> >>> Regards >>> Heiko Zuerker >>> http://www.devil-linux.org >>> >>> Quoting Serge Leschinsky<ser...@gm...>: >>> >>>> Hi, >>>> >>>> It looks like I missed instruction/howto for DL git repo. I don't post the >>>> changes very often of course, but anyway - I wouldn?t like to >>>> bother Heiko with >>>> tracking and resubmitting those changes. If you know where I can find the >>>> manual, please let me know. >>>> >>>> >>>> Thanks, >>>> Serge >>>> >>>> ------------------------------------------------------------------------------ >>>> All of the data generated in your IT infrastructure is seriously valuable. >>>> Why? It contains a definitive record of application performance, security >>>> threats, fraudulent activity, and more. Splunk takes this data and makes >>>> sense of it. IT sense. And common sense. >>>> http://p.sf.net/sfu/splunk-d2d-c2 >>>> _______________________________________________ >>>> Devil-linux-develop mailing list >>>> Dev...@li... >>>> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop >>> >>> >>> -- >>> >>> Regards >>> Heiko Zuerker >>> http://www.devil-linux.org >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> All of the data generated in your IT infrastructure is seriously valuable. >>> Why? It contains a definitive record of application performance, security >>> threats, fraudulent activity, and more. Splunk takes this data and makes >>> sense of it. IT sense. And common sense. >>> http://p.sf.net/sfu/splunk-d2d-c2 >>> _______________________________________________ >>> Devil-linux-develop mailing list >>> Dev...@li... >>> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop >> >> >> -- >> >> Regards >> Heiko Zuerker >> http://www.devil-linux.org >> >> >> >> ------------------------------------------------------------------------------ >> All of the data generated in your IT infrastructure is seriously valuable. >> Why? It contains a definitive record of application performance, security >> threats, fraudulent activity, and more. Splunk takes this data and makes >> sense of it. IT sense. And common sense. >> http://p.sf.net/sfu/splunk-d2d-c2 >> _______________________________________________ >> Devil-linux-develop mailing list >> Dev...@li... >> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop > > |