Go for branching! :D
It's really useful and brings no pain at all. As kakaroto pointed out, the
best way to do it (and most extended) is to work in /trunk, create branches
for experimental work or released major versions that u still wanna mantain
(which we don't do) and use tags for released v
Hey mate!
Gorgeous stuff! I think that's what aMSN needs to go away of that old MSN 4.0
look. If u can get that kind of modern and friendly interface and make it
compatible with the level of customization we have... it would be a success.
Of course, a huge amount of work would be needed :P
Kee
No answers yet? It would be great if we could join the programme, but the
deadline is set for tomorrow...
On Thursday 20 April 2006 11:02, Karel Demeyer wrote:
> I just sent a mail to propose aMSN for the summer of code of Google.
> I'll keep you informed when a reply arrives.
>
> Karel.
>
>
>
>
Hi Phil!
If SELinux is not the default there, I suppose the ones who choose it know
what they are doing and so they know how to fetch a tgz and compile it, so
for me the 'proper fix' is just add a note in the wiki or even a simple check
in aMSN which warns the user: 'You are using a SELinux enab
I don't think we need an ebuild for Gentoo. I use Gentoo and I have to say
that they are pretty fast getting things into portage, and I think aMSN got a
new mantainer which is quite active, maybe we just need to tell him by email.
As it would be a matter of hours to have it on portage (officially
I volunteer for Q&A so, contact me if u want.
Alberto
El Tuesday, 13 de December de 2005 05:57, Youness Alaoui escribió:
> ok, ok everyone, relax... I already said in a previous email that I had a
> plan to organize all this and that it would be (partially) based on the
> system we use at my job.
(WARNING: This is a long, boring mail :P)
Well, maybe I am the only one who doesn't feel it like a totally postitive
thing... First of all, aMSN is far from being stable on its own. Maybe it's
better to polish what we currently have than coming up with a new core and
adapting some pieces of our
(WARNING: This is a long, boring mail :P)
Well, maybe I am the only one who doesn't feel it like a totally postitive
thing... First of all, aMSN is far from being stable on its own. Maybe it's
better to polish what we currently have than coming up with a new core and
adapting some pieces of our
Well, I think the main question here is: are they going to drop support for
lower versions as they did once before, denying connection to such clients?
If not, then we shouldn't worry a lot. It'd be just another bump of the
protocol, and we will implement it as soon as we can. If it is the other
