humm... well, even daily is ok, but in a digest, will we get the diff too
? yes, and that's the problem, it's a pain in the ass to go looking for
the comments individually...
anyways, now, I'm just looking at what CIA-13 has to say on the amsn IRC
channel.. it gives me a summary
KaKaRoTo
On Sat, 26 Nov 2005 06:30:09 -0500, Arieh Schneier
<[EMAIL PROTECTED]> wrote:
I was going to say to go to:
http://lists.sourceforge.net/lists/listinfo/amsn-commits
and set your option to digest, but then realised the digest is daily
instead
of weekly.
Lio.
----- Original Message -----
From: "Youness Alaoui"
oups.. ok, sorry :)
I don't read the commits because I filter them, get them to another
directory (Opera names that a filter) and mark them as read.. if I don't,
I'll have too much to look into and I don't have time to look at normal
emails, so imagine with the commits...
it would be nice to have a digest of all commits once per week so we can
look at what was done, but only get the message that was sent, not the
diff...
maybe CIA would be a place to look at for this thing, but I don't know if
they have a "send me weekly summaries of the activities..." I'll have to
look into that.
KaKaRoTo
On Fri, 25 Nov 2005 16:25:21 -0500, Jérôme Gagnon-Voyer
<[EMAIL PROTECTED]> wrote:
Hey, you should read the amsn-commits list, it was done on 17th
november ;-0
De : [EMAIL PROTECTED]
Objet : [Amsn-commits] msn autoupdate.tcl,1.32,1.33
Date : 17 novembre 2005 22:07:57 HNE
À : [EMAIL PROTECTED]
Update of /cvsroot/amsn/msn
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv26417
Modified Files:
autoupdate.tcl
Log Message:
Fixed: autoupdate now checks for all 'sections' of release numbers
Index: autoupdate.tcl
===================================================================
RCS file: /cvsroot/amsn/msn/autoupdate.tcl,v
retrieving revision 1.32
retrieving revision 1.33
diff -C2 -d -r1.32 -r1.33
*** autoupdate.tcl 17 Sep 2005 16:32:31 -0000 1.32
--- autoupdate.tcl 18 Nov 2005 03:07:55 -0000 1.33
***************
*** 530,539 ****
set yourver [split $version "."]
! if { [lindex $lastver 0] > [lindex $yourver 0] } {
! set newer 1
! } else {
! # Major version is at least the same
! if { [lindex $lastver 1] > [lindex $yourver 1] } {
set newer 1
}
}
--- 530,537 ----
set yourver [split $version "."]
! for {set x 0} {$x<[llength "$lastver"]} {incr x} {
! if {[lindex $lastver $x] > [lindex $yourver $x]} {
set newer 1
+ break
}
}
Le 05-11-25 à 16:12, Youness Alaoui a écrit :
one more TODO item and pretty important :
Make sure the auto-updater recognizes 0.94 < 0.95 < 0.95.1 < 0.95.2
< 0.95.10 < 0.96
KKRT
On Fri, 25 Nov 2005 15:56:18 -0500, Youness Alaoui
<[EMAIL PROTECTED]> wrote:
Yes, I do agree.. as I said, December 1st, if nothing major
appears, we release 0.95... if we can't fix the bug by december
1st, we'll use the orkaround and that's it...
Harry, maybe you didn't get the latest change because the
anonymous CVS wasn't up to date... JUST IN CASE, I would suggest
you get the latest cvs again and do a `make clean all`... if the
bug still happens, i would really appreciate it if you did like
you did at first : give us the backtrace of the segfault ...
without the backtrace from gdb, we can't find where the new bug
happens...
Thanks,
KaKaRoTo
On Fri, 25 Nov 2005 15:06:19 -0500, Jérôme Gagnon-Voyer
<[EMAIL PROTECTED]> wrote:
Don't forget we just have to re-enable the check for the PWC driver
at the start of aMSN. That way, the config buttons will just be
disabled so nobody will get a seg fault, that's not a "serious bug"
for a release because we can prevent the bug from happening (yes
it's
better to fix the bug but at least we can prevent it)
Le 05-11-25 à 14:09, Harry Vennik a écrit :
That is to say, we thought it would be fixed now, but it is not.
At this moment I don't think anyone understands why the change by
Phil didn't
fix it. I tried to find it out this morning, but no success. I will
try again
tomorrow, if I don't get it again, and neither does anyone else,
then I think
we should not have this prevent us from releasing 0.95, even though
I regard
it as quite a serious bug.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel
--
KaKaRoTo
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel
