Re: [Geeqie-devel] Geeqie repositories
Klaus Ethgen-5 wrote: - - Then I have different remotes with all the branches they have: github git://github.com/zas/geeqie_zas.git (fetch) github g...@github.com:zas/geeqie_zas.git (push) gitorious g...@gitorious.org:geeqie/geeqie.git (fetch) gitorious g...@gitorious.org:geeqie/geeqie.git (push) origin ssh://tschil.ethgen.ch/~/git/geeqie.git (fetch) origin ssh://tschil.ethgen.ch/~/git/geeqie.git (push) sf git://geeqie.git.sourceforge.net/gitroot/geeqie/geeqie (fetch) sf m...@geeqie.git.sourceforge.net/gitroot/geeqie/geeqie (push) As you can see, origin points on my own server where I have a similar layout and a hook that pushes all my work to all (at the moment github and gitorious) upstream repositories. Would it be possible for the master on gitorious to be automatically pushed onto SourceForge? Geeqie on SourceForge looks to be a somewhat dead project, as the files have not been updated for months. People who are looking for software will not find geeqie on gitorious because they will look no further than SourceForge. For example this link..: http://www.tuxarena.com/2011/02/top-5-image-viewers-for-ubuntukubuntu/ .. about half-way down the page shows that some people look only as far as SourceForge (and have not yet made the connection between GQView and geeqie). Wherever, however, the developers want to update geeqie, I think that to keep the general public up to date it is important that SourceForge also has the latest source tars (and packages if possible). -- View this message in context: http://old.nabble.com/Geeqie-repositories-tp30914628p32124744.html Sent from the Geeqie mailing list archive at Nabble.com. -- Magic Quadrant for Content-Aware Data Loss Prevention Research study explores the data loss prevention market. Includes in-depth analysis on the changes within the DLP market, and the criteria used to evaluate the strengths and weaknesses of these DLP solutions. http://www.accelacomm.com/jaw/sfnl/114/51385063/ ___ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel
Re: [Geeqie-devel] Geeqie repositories
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Omari, Am Mo den 25. Apr 2011 um 18:13 schrieb Omari Stephens: I just created an account on gitorious (xsdg as might be expected). Could you add me to geeqie-developers? Did so. Am Mo den 25. Apr 2011 um 18:16 schrieb Omari Stephens: Reply-to considered harmful 8) ? I cannot follow. Gruß Klaus - -- Klaus Ethgenhttp://www.ethgen.ch/ pub 2048R/D1A4EDE5 2000-02-26 Klaus Ethgen kl...@ethgen.de Fingerprint: D7 67 71 C4 99 A6 D4 FE EA 40 30 57 3C 88 26 2B -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBTbZ5FJ+OKpjRpO3lAQo/HAf/TQAw1EVfOw2A0vA4BSHN8CNcGIKjvz8J 6fkOOOYHlgTa6+blpKxXc5kA8yCwgJ1D3AFRzceD3hg3vaAqD2+bLbn63YtROHkf fHmJR/Lz6ogtypSB6Vh+H6xsWwDZyybsuIc9IoPQaaMbWIHZxcS+0pH/ESSFIy1i KwReNci2XonNvBjJdnRlB/ZbA3EGwTC7SOzE0aOkK7ZXXRMPjEb3xM4DXrwc7mUg gkK4VKWy91Auolezfzae+UgTMum1M+bLLIMK6XZeQKOW3aXFybdMzEb3NUPUQxOE 05VQF7RoZ51ybbyMwKfOhkhyeXAfrHermm9iueUvHi7N7IMTpcN40Q== =7V3X -END PGP SIGNATURE- -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel
Re: [Geeqie-devel] Geeqie repositories
Hey, Klaus I just created an account on gitorious (xsdg as might be expected). Could you add me to geeqie-developers? Thanks, --xsdg On 04/15/2011 03:35 PM, Klaus Ethgen wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello Vladimir, Am Fr den 15. Apr 2011 um 14:54 schrieb Vladimir Nadvornik: Do I understand it correctly that now everybody is using his own branch and master is unchanged since December? So far until now. Who and when will merge the branches to master? Well, I think, if one feature is ready to go in the main branch it could be merged. I think that this should be done of the owner of the work but could be done by everyone that can commit. Does merging of one branch mean that the other branches should be rebased? I do not think that rebasing is the right way then. You can merge back the master to your branch or cherry-pick commits from there. The power of git is to handle multiple merges very well. It is also thinkable to delete the branch after full merge and recreate it later on as a new branch. That is the freedom you have with git. :-) Now for my patches. They are not 100% finished, but I want to publish them for testing, so I will push them to gitorious/nadvornik-stereo, OK? Right. If someone want to test, he can checkout that branch or do a (temporary) merge to his own local branch. But as I see correct, you have to be added to geeqie-developers. As I see, your account there is nadvornik so I added you. Can you please give me write permission for the project? Ah right, sorry, read sequential. ;) You should be an administrator now. I think the main persons are in that group now. Regards Klaus - -- Klaus Ethgenhttp://www.ethgen.ch/ pub 2048R/D1A4EDE5 2000-02-26 Klaus Ethgenkl...@ethgen.de Fingerprint: D7 67 71 C4 99 A6 D4 FE EA 40 30 57 3C 88 26 2B -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBTahlrp+OKpjRpO3lAQpbxQgAkisChVQwgsQovCT+Xbm1CUqhR4JbPSnD VtD1iPRLXM0Cb4io1MINevSHae6Sa38KhPPRa2/BuMulbfgGtW6RHB4AkfRGwFgS +8A9OPWPoH6s0xbbQcxlJVByQ6R2ICD+/cypwfGXj0JbXI5MdymkL94Qd2EVRpNA AQziYq+mfjgVKIMt8MA7NlfRg6/XutHzeLSQTjDr8yBUde2k2cf0PZOpYbOo68VJ Cx0f8EJdvkFc+i+G/qN6iUNedSavgWnifveaZmwUAysjefHI4qJl43NRT1lFQ9fR I2ROgPHm3XN4RyelN+raSRU/zwtWy+MdLnAky8b1xkOZvE4tGZk3tA== =/NeL -END PGP SIGNATURE- -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel
Re: [Geeqie-devel] Geeqie repositories
On Pá 15. dubna 2011, Klaus Ethgen wrote: Now for my patches. They are not 100% finished, but I want to publish them for testing, so I will push them to gitorious/nadvornik-stereo, OK? Right. If someone want to test, he can checkout that branch or do a (temporary) merge to his own local branch. But as I see correct, you have to be added to geeqie-developers. As I see, your account there is nadvornik so I added you. Can you please give me write permission for the project? Ah right, sorry, read sequential. ;) You should be an administrator now. Thanks. My branch is now on gitorious. Vladimir -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel
Re: [Geeqie-devel] Geeqie repositories
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Vladimir, Am Do den 14. Apr 2011 um 22:44 schrieb Vladimir Nadvornik: I started to hack Geeqie again and now I have a series of patches for stereo image support. The patches also implements a base for future improvements of image loading and rendering. Nice to see you back. The patches are currently in my local git. Since this is my first project with git, I would need some advice how to push it to Gitorious, whether use separate branch, etc. IMHO git provides too much flexibility here ;) Well, maybe I can give some hints. Ask if they are not detailed enough. - - Only tracking branches gets pushed to the server per default. You start a tracking branch by »checkout -b whatever origin/upstreambranch« or by editing .git/config. - - To push a completely new branch or only one, use it explicit: »git push origin yourgreatbranch« or »git push origin yourgreatlocalbranch:boringbranchnameinpublic« - - Stay at the edge of all remotes: »git remote update« (Do not push, only pull, but all remotes not only one.) - - Use branches local (not tracked) to implement a feature but merge it in the tracked branch after finishing. Afterwards you can delete your own branch but the full history can be seen when you push. - - Use rebase only on your own branches locally. Never rebase tracking branches after you push them. It produce a mess if you do as all others have your original branchhead. (However, that can be solved but you should omit.) - - Use origin/master for current development. And use a own origin branch for your own work that you want other to see too (experimental or not finished stuff. You might rebase on that but try to omit it as I explained above). I propose to use release branches for relased versions and fixes or release work. A real example. At the moment I have the following structure local: - - master -- My tracking branch for origin/master - - ke -- My private branch with stuff I open to other. As I pushed that name it is also the tracking branch for origin/ke. I use merges or even cherry-picks to populate that tree. To revoke commits that are erroneous I use revert. - - ke-lua -- My feature branch for the unfinished lua feature. As it might be interesting for other even in that early state I also pushed it. - - debian-529531 -- a local branch I use to fix a debian bug. I will never push it upstream but merge it into master when it is finished. I might use rebase or commit --amend here as it doesn't destroy pushed history. - - Then I have different remotes with all the branches they have: github git://github.com/zas/geeqie_zas.git (fetch) github g...@github.com:zas/geeqie_zas.git (push) gitorious g...@gitorious.org:geeqie/geeqie.git (fetch) gitorious g...@gitorious.org:geeqie/geeqie.git (push) origin ssh://tschil.ethgen.ch/~/git/geeqie.git (fetch) origin ssh://tschil.ethgen.ch/~/git/geeqie.git (push) sf git://geeqie.git.sourceforge.net/gitroot/geeqie/geeqie (fetch) sf m...@geeqie.git.sourceforge.net/gitroot/geeqie/geeqie (push) As you can see, origin points on my own server where I have a similar layout and a hook that pushes all my work to all (at the moment github and gitorious) upstream repositories. My config (the relevant parts) looks like: [remote origin] url = ssh://tschil.ethgen.ch/~/git/geeqie.git fetch = +refs/heads/*:refs/remotes/origin/* [remote github] url = git://github.com/zas/geeqie_zas.git pushurl = g...@github.com:zas/geeqie_zas.git fetch = +refs/heads/*:refs/remotes/github/* [remote sf] url = git://geeqie.git.sourceforge.net/gitroot/geeqie/geeqie fetch = +refs/heads/*:refs/remotes/sf/* pushurl = m...@geeqie.git.sourceforge.net/gitroot/geeqie/geeqie [remote gitorious] url = g...@gitorious.org:geeqie/geeqie.git fetch = +refs/heads/*:refs/remotes/gitorious/* pushurl = g...@gitorious.org:geeqie/geeqie.git [branch master] remote = origin merge = refs/heads/master [branch ke] remote = origin merge = refs/heads/ke [branch ke-lua] remote = origin merge = refs/heads/ke-lua Note the three branch sections, that are my tracking branches. You might use other names for remotes or your tracking branches. What I not mention here is to use special remotes like bundles or local available checkouts in $HOME of others to even have work that is shared between people not working in the global repository. Regards Klaus - -- Klaus Ethgenhttp://www.ethgen.ch/ pub 2048R/D1A4EDE5 2000-02-26 Klaus Ethgen kl...@ethgen.de Fingerprint: D7 67 71 C4 99 A6 D4 FE EA 40 30 57 3C 88 26 2B -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux)
Re: [Geeqie-devel] Geeqie repositories
On Pá 15. dubna 2011, Klaus Ethgen wrote: Hi Vladimir, Am Do den 14. Apr 2011 um 22:44 schrieb Vladimir Nadvornik: I started to hack Geeqie again and now I have a series of patches for stereo image support. The patches also implements a base for future improvements of image loading and rendering. Nice to see you back. The patches are currently in my local git. Since this is my first project with git, I would need some advice how to push it to Gitorious, whether use separate branch, etc. IMHO git provides too much flexibility here ;) Well, maybe I can give some hints. Ask if they are not detailed enough. - Use origin/master for current development. And use a own origin branch for your own work that you want other to see too (experimental or not finished stuff. You might rebase on that but try to omit it as I explained above). I propose to use release branches for relased versions and fixes or release work. Thanks for the hints. Do I understand it correctly that now everybody is using his own branch and master is unchanged since December? Who and when will merge the branches to master? Does merging of one branch mean that the other branches should be rebased? Now for my patches. They are not 100% finished, but I want to publish them for testing, so I will push them to gitorious/nadvornik-stereo, OK? Can you please give me write permission for the project? Thanks, Vladimir -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel
Re: [Geeqie-devel] Geeqie repositories
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello Vladimir, Am Fr den 15. Apr 2011 um 14:54 schrieb Vladimir Nadvornik: Do I understand it correctly that now everybody is using his own branch and master is unchanged since December? So far until now. Who and when will merge the branches to master? Well, I think, if one feature is ready to go in the main branch it could be merged. I think that this should be done of the owner of the work but could be done by everyone that can commit. Does merging of one branch mean that the other branches should be rebased? I do not think that rebasing is the right way then. You can merge back the master to your branch or cherry-pick commits from there. The power of git is to handle multiple merges very well. It is also thinkable to delete the branch after full merge and recreate it later on as a new branch. That is the freedom you have with git. :-) Now for my patches. They are not 100% finished, but I want to publish them for testing, so I will push them to gitorious/nadvornik-stereo, OK? Right. If someone want to test, he can checkout that branch or do a (temporary) merge to his own local branch. But as I see correct, you have to be added to geeqie-developers. As I see, your account there is nadvornik so I added you. Can you please give me write permission for the project? Ah right, sorry, read sequential. ;) You should be an administrator now. I think the main persons are in that group now. Regards Klaus - -- Klaus Ethgenhttp://www.ethgen.ch/ pub 2048R/D1A4EDE5 2000-02-26 Klaus Ethgen kl...@ethgen.de Fingerprint: D7 67 71 C4 99 A6 D4 FE EA 40 30 57 3C 88 26 2B -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBTahlrp+OKpjRpO3lAQpbxQgAkisChVQwgsQovCT+Xbm1CUqhR4JbPSnD VtD1iPRLXM0Cb4io1MINevSHae6Sa38KhPPRa2/BuMulbfgGtW6RHB4AkfRGwFgS +8A9OPWPoH6s0xbbQcxlJVByQ6R2ICD+/cypwfGXj0JbXI5MdymkL94Qd2EVRpNA AQziYq+mfjgVKIMt8MA7NlfRg6/XutHzeLSQTjDr8yBUde2k2cf0PZOpYbOo68VJ Cx0f8EJdvkFc+i+G/qN6iUNedSavgWnifveaZmwUAysjefHI4qJl43NRT1lFQ9fR I2ROgPHm3XN4RyelN+raSRU/zwtWy+MdLnAky8b1xkOZvE4tGZk3tA== =/NeL -END PGP SIGNATURE- -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel
Re: [Geeqie-devel] Geeqie repositories
Hi all, I started to hack Geeqie again and now I have a series of patches for stereo image support. The patches also implements a base for future improvements of image loading and rendering. The patches are currently in my local git. Since this is my first project with git, I would need some advice how to push it to Gitorious, whether use separate branch, etc. IMHO git provides too much flexibility here ;) Thanks, Vladimir Dne pondělí 14 Únor 2011 13:16:04 Klaus Ethgen napsal(a): Hi List, Am So den 13. Feb 2011 um 21:47 schrieb Omari Stephens: Having 10 different repositories doesn't do anyone any good. How about sending an email first so we're all on the same page? Yea, might be. Ashes to my head. But Gitorious is cool. ;-) It was also a way to play with multi pushes which, I have to say, seems to work pretty well now for me. But this is a bit egoistic, I know. Currently, there are geeqie git repositories at: github (started by zas) sourceforge (ported from sourceforge svn by someone; I forget who, but they sent email to the list) gitorious (started by klaus) We should pick a canonical one and stick with it. Personal I would vote for Gitorious for the following reasons: - The platform is open - The project is not bind to a special account, your root is the project. - You can define teams - It profit from social hacking (like forking, pull requests, ...) But I wouldn't be sad if a other platform makes the choice. Most important, we, the developers feel good about. By the way, zas, how did you get this nice little icon beside your name without having a own gitorious account until now? Regards Klaus Ps. Tore, I add you as commiter. -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel
Re: [Geeqie-devel] Geeqie repositories
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi List, Am So den 13. Feb 2011 um 21:47 schrieb Omari Stephens: Having 10 different repositories doesn't do anyone any good. How about sending an email first so we're all on the same page? Yea, might be. Ashes to my head. But Gitorious is cool. ;-) It was also a way to play with multi pushes which, I have to say, seems to work pretty well now for me. But this is a bit egoistic, I know. Currently, there are geeqie git repositories at: github (started by zas) sourceforge (ported from sourceforge svn by someone; I forget who, but they sent email to the list) gitorious (started by klaus) We should pick a canonical one and stick with it. Personal I would vote for Gitorious for the following reasons: - - The platform is open - - The project is not bind to a special account, your root is the project. - - You can define teams - - It profit from social hacking (like forking, pull requests, ...) But I wouldn't be sad if a other platform makes the choice. Most important, we, the developers feel good about. By the way, zas, how did you get this nice little icon beside your name without having a own gitorious account until now? Regards Klaus Ps. Tore, I add you as commiter. - -- Klaus Ethgenhttp://www.ethgen.ch/ pub 2048R/D1A4EDE5 2000-02-26 Klaus Ethgen kl...@ethgen.de Fingerprint: D7 67 71 C4 99 A6 D4 FE EA 40 30 57 3C 88 26 2B -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQEVAwUBTVkdBJ+OKpjRpO3lAQoh5gf/ZgzO94qowG0xNB23mTpWfyBuh4p7ILEg pm30xEGeOhiejI+usC3cuSC5Hi25cEm2L7T53WeRWoGq6mPJhR6oSVzup7wWIPS6 MFn8XG9/u+/03o3QtuszmxLZ/MqZ00K0gmNZoz1yYX9dicUHuSi2Jxw5bQdEzsgM Vq0l8Mg/0kSRikPI0Qs+CywHkXZ8LvIF3pPDTKY3y42xOs4RecTEKlb3cRvkMdN5 WzQNEbZJTTKwnN6wmYqDd8rJVIg6ksl5S1KKwYUK7ep3zaylZLFiZdpwqAEn9ddw 9Tgwr6fzoCjQAA0YxLjwYcOrto1hqgNRtqRr21PNtQPwL970G2K7vg== =W/o3 -END PGP SIGNATURE- -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel
Re: [Geeqie-devel] Geeqie repositories
Le 14/02/2011 13:16, Klaus Ethgen a écrit : By the way, zas, how did you get this nice little icon beside your name without having a own gitorious account until now? I just registred my committer/author email at gravatar.com, and associated an image. Regards, -- Zas -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel
Re: [Geeqie-devel] Geeqie repositories
Le 13/02/2011 21:47, Omari Stephens a écrit : Having 10 different repositories doesn't do anyone any good. How about sending an email first so we're all on the same page? Currently, there are geeqie git repositories at: github (started by zas) sourceforge (ported from sourceforge svn by someone; I forget who, but they sent email to the list) Petr Ostadal (one of the forkers from initial Gqview with Vladimir). gitorious (started by klaus) We should pick a canonical one and stick with it. I agree, i vote for gitorious, which is the best imho (sourceforge is a pain, github has patent issues). I put my stuff on github because i had an account there and svn activity was dead, this is not attended to store official geeqie. -- Zas -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb___ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel
Re: [Geeqie-devel] Geeqie repositories
Le 13/02/2011 21:47, Omari Stephens a écrit : ... I agree, i vote for gitorious, which is the best imho (sourceforge is a pain, github has patent issues). I put my stuff on github because i had an account there and svn activity was dead, this is not attended to store official geeqie. -- Zas I agree, voting for Gitorius / toer -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel
