2010/5/30 Panos Filip panosfi...@gmail.com
But you would need to make a new PKGBUILD for every new branch, 2.1, 2.2,
2.3 and so on.
You're right. Should I create kmess-stable-git now (and ask for
kmess2.0.x-git removal) or should I wait next stable branch switch?
I'd prefer the second one, as
On Sun 30 May 2010 12:54 +0200, Federico Chiacchiaretta wrote:
2010/5/30 Panos Filip panosfi...@gmail.com
But you would need to make a new PKGBUILD for every new branch, 2.1,
2.2, 2.3 and so on.
You're right. Should I create kmess-stable-git now (and ask for
kmess2.0.x-git removal) or
2010/5/30 Loui Chang louipc@gmail.com
I say get it over with as soon as possible. Less people will have to
worry about switching then.
Ok, I uploaded a new pkg kmess-stable-git, so I'm asking for removal of
kmess2.0.x-git [1]. I'll leave a comment on the new pkg's page to explain
the
Hi all,
I'm asking for removal of both kmess-svn [1] and kmess-svn-stable [2], these
are packages of mine but are no longer useful because Kmess' devs switched
to git a few days ago, and svn repo is no longer updated. I'm providing new
version of both based on new kmess git repo yet (kmess-git and
On Sat, 29 May 2010 18:52:00 +0200
Federico Chiacchiaretta federico.c...@gmail.com wrote:
Hi all,
I'm asking for removal of both kmess-svn [1] and kmess-svn-stable
[2], these are packages of mine but are no longer useful because
Kmess' devs switched to git a few days ago, and svn repo is no
2010/5/29 Thorsten Töpper atsut...@freethoughts.de
Done.
In my opinion kmess-stable-git would be a better name instead of the
one including the version.
--
Jabber: atsut...@freethoughts.de Blog: http://atsutane.freethoughts.de/
Key: 295AFBF4 FP: 39F8 80E5 0E49 A4D1 1341 E8F9 39E4 F17F
On Sat, May 29, 2010 at 8:29 PM, Federico Chiacchiaretta
federico.c...@gmail.com wrote:
2010/5/29 Thorsten Töpper atsut...@freethoughts.de
Done.
In my opinion kmess-stable-git would be a better name instead of the
one including the version.
--
Jabber: atsut...@freethoughts.de
