You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(43) |
Nov
(6) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2006 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
(1) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(6) |
2007 |
Jan
(4) |
Feb
(4) |
Mar
|
Apr
|
May
(4) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Mitch D. <mj...@al...> - 2003-10-14 17:31:17
|
Benjam=EDn Albi=F1ana P=E9rez wrote: > > Here I'm updating everyday the source from the cvs (and making a > tar.bz2 at midnight, in order to put it in bastardo's web), and > compiling it. Thank you. > It runs smoothly in debian unstable with a minor > problem, I must change permissions on /usr/local/share/qvwm to > allow access to the users to conf, sounds a images. I think it is a > problem of my umask (027 in my systems), not qvwm.=20 That's good to hear. At the moment, what's in CVS is stock 1.1.12 as Mr. Kenichi-san released it. > BTW, there are no changes since the last two days, right? That's right. I'm looking at Ali's changes tonight. > The qvwm-11102003.tar.gz is the one in the SF pages? No. That's his snapshot for you to try out if you're brave. You can find it here: http://www.linuxprogramlama.com/index.php?sayfa=3Dqvwm.htm My comments are relative to Ali's snapshot, not to what's in CVS. My intention (subject to what y'all think) is for stuff to be reviewed here before it goes into CVS. Thank you for your mail! :-) Mitch. |
From: <be...@hi...> - 2003-10-14 17:03:33
|
Cuando: mi=E9, 15 de oct de 2003, a las 01:38:45 +1000 Quien: Mitch Davis Que: [qvwm-devel] Test of qvwm-11102003.tar.gz: some notes > I give you these comments in the time honoured tradition of peer > review: Not to put you down but to help make better software. > I am also wondering whether I am the only one to have these > problems, or whether others have also had them. Guys? =20 Here I'm updating everyday the source from the cvs (and making a tar.bz2 at midnight, in order to put it in bastardo's web), and compiling it. It runs smoothly in debian unstable with a minor problem, I must change permissions on /usr/local/share/qvwm to allow access to the users to conf, sounds a images. I think it is a problem of my umask (027 in my systems), not qvwm.=20 BTW, there are no changes since the last two days, right? The qvwm-11102003.tar.gz is the one in the SF pages? --=20 Benjam=EDn Albi=F1ana P=E9rez =BFQu=E9 parte de "apt-get remove --purge emacs20" no entiendes? |
From: Mitch D. <mj...@al...> - 2003-10-14 15:38:49
|
Hi Ali, Thankyou for putting together your snapshot. I tried it out tonight, and here are some things I noticed. The first one in particular stops qvwm working properly for me, because qvwm does not set its resources up properly (can't access /root, because I'm not running it as root). I give you these comments in the time honoured tradition of peer review: Not to put you down but to help make better software. I am also wondering whether I am the only one to have these problems, or whether others have also had them. Guys? - When I start qvwm, I get a bunch of console warnings about unable to copy files from /root. I guess this is qvwm trying to set up some resources, and is related to you running as root on your box. In particular, initalize_user_conf_files() looks quite hard coded to /root. Any ideas? Should qvwm copy from /usr/share/qvwm or similar instead? - qvwm-11102003.tar.gz has a symlink "base/qvwm/man/qvwm.1x" which points to ".././man". The symlink shouldn't be in the file, because it is generated by AC_LINK_FILES in configure.in. - After I run configure, man/qvwm.1x ends up pointing to ".././man" (same as yours) which is not sensible on my machine. It should point to the right man page for the selected locale. Not sure how to fix this one... I look forward to further snapshots from you. Your work is going well. Regards, Mitch. |
From: Mitch D. <mj...@al...> - 2003-10-12 16:55:39
|
Hi Guys, >>I'm not doing this to point the finger at anyone, because >>really, any of us could have made the same mistake. > > I've made some minor changes to es.msg, and make a cvs commit. But I > have not touched anything else. Was my fault? :( I hesitate to use the word "fault". It's too strong! It was a simple mistake and easily fixed. I think what happened is you have at some time typed tar -cvfj * ... forgetting the name of the .tar.bz2 file after the -cvfj. And "aclocal.m4" is the first expansion of "*", and the bzipped tarfile got written to aclocal.m4. When you did the commit (which I suggest you did without specifying the file to commit), CVS picked up ALL modified files, which included aclocal.m4. One way to avoid this tar problem is to use "." rather than "*". That way, if you forget the name of the tar file, tar will say "cowardly refusing to create an empty archive". The other bonus is that it will also pick up "dot" files. > Ok, I've made an alias cvs='echo "stop right now, you stupid"' Hey, don't be so harsh on yourself! :-) If we start calling ourselves (and each other) names, we'll never get anywhere. Here are some ideas: - Make a regular habit of doing a "cvs diff -u" *before* you commit. That way, you know what will go into the repository. - When you do a commit, explicitly specify the names, eg, "cvs ci es.msg". That way, if there are some files that you don't want to commit, they won't get commited. - The CVS commit process asks you for a comment saying why you're making the change. But it also shows you a list of the files that will be committed. Have a look at this list! If you see something that shouldn't be there, quit the editor without saving. CVS will ask you if you want to abort the commit. Also, I would like to encourage everyone to make good checkin comments. We've all heard about this style of commenting: i++ // Add one to I. Well yeah, we can all see that! :-) The problem with this is it tells you WHAT the change is, not WHY the change is happening. The same goes for checkin comments. Without wanting to point fingers, "fixed a problem on line 28" doesn't say WHY line 28 needed changing. As a suggestion, it could have been followed with "because ... " and then the problem you observed. (Also, CVS will also add the date itself, saving you the trouble...) Well enough of my lecturing! (wake up guys, all I hear is snoring!) I'll catch y'all around. Mitch. |
From: <be...@hi...> - 2003-10-12 14:29:04
|
Cuando: dom, 12 de oct de 2003, a las 11:17:10 +1000 Quien: Mitch Davis Que: [qvwm-devel] Re: qvwm-cvs digest, Vol 1 #4 - 2 msgs =20 > The corruption happened because someone checked in a new > version of the file. The new version is actually a bzipped > tar file!!! :-( >=20 > I'm not doing this to point the finger at anyone, because > really, any of us could have made the same mistake. But > it indicates that we have to be a little more careful > with public resources (like a website or CVS) than if we're > only working with our own files. I've made some minor changes to es.msg, and make a cvs commit. But I have not touched anything else. Was my fault? :( > One way to do this is to send your changes to the qvwm-devel > mailing list as a "diff". Then everyone can comment on it. Ok, I've made an alias cvs=3D'echo "stop right now, you stupid"' My apologizes.=20 --=20 Benjam=EDn Albi=F1ana P=E9rez =2E..debian should remove all editor packages other than vim!! Jared Johnson, in linux.debian.devel |
From: Mitch D. <mj...@al...> - 2003-10-12 13:17:14
|
qvw...@li... wrote: > To: qvw...@li... > Date: Fri, 10 Oct 2003 13:35:04 -0700 > Subject: [qvwm-cvs] qvwm aclocal.m4,1.5,1.6 > Reply-To: > > Update of /cvsroot/qvwm/qvwm > In directory sc8-pr-cvs1:/tmp/cvs-serv5589/qvwm > > Modified Files: > aclocal.m4 > Log Message: > > vie oct 10 22:33:27 CEST 2003 > fix an error in line 28 > > > Index: aclocal.m4 > =================================================================== > RCS file: /cvsroot/qvwm/qvwm/aclocal.m4,v > retrieving revision 1.5 > retrieving revision 1.6 > diff -C2 -d -r1.5 -r1.6 > Binary files /tmp/cvsiWrEtM and /tmp/cvsIzIGSp differ Hi guys, Has anyone done a "cvs update" and tried to compile the result? It doesn't work because aclocal.m4 has become corrupted. The corruption happened because someone checked in a new version of the file. The new version is actually a bzipped tar file!!! :-( I'm not doing this to point the finger at anyone, because really, any of us could have made the same mistake. But it indicates that we have to be a little more careful with public resources (like a website or CVS) than if we're only working with our own files. One way to do this is to send your changes to the qvwm-devel mailing list as a "diff". Then everyone can comment on it. There are two advantages of doing this. First, if you know people will look closely at your changes, you become more careful, and this leads to much higher code *quality*. Second, looking at the changes someone else did to implement a particular feature or fix a particular bug is a really excellent way of quickly learning more about the system. So if we all have an increased familiarity with the system, that leads to higher code *quantity*. I have seen this work in industry and it really works. You make a diff like this: cd qvwm cvs diff -u > my-changes.diff You can then mail this to qvw...@li... for us to look at. Also include a few lines on WHY you're making this change! :-) See you all in IRC or ICQ sometime soon. Regards, Mitch. PS: I've fixed the CVS problem... |
From: Mitch D. <mj...@al...> - 2003-10-07 18:29:37
|
Hi Guys, SF have put the CVS repository I built online, so we can now use CVS to synchronize our programming efforts. General information on how to use CVS can be found here: http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1 http://sourceforge.net/docman/display_doc.php?docid=768&group_id=1 Information specific to qvwm on SourceForge can be found here: http://sourceforge.net/cvs/?group_id=91158 The documentation refers to a "modulename". This will be "qvwm" for the latest 1.1.12 source, and "qvwm-web" for the website. In other news, you can try here if you like: http://qvwm.sf.net/ Regards, Mitch. |
From: Mitch D. <mj...@al...> - 2003-10-07 01:14:05
|
Hello/Hola!, You're reading this mail because you've expressed interest in reviving the "qvwm" window manager program. In case you didn't know or have forgotten, qvwm is a very fast and lightweight X Windows window manager, which gives the user a very "Windows"-like experience. The home of qvwm is at http://www.qvwm.org/, but the original author of qvwm hasn't replied to emails for several months. Since there are a few people who have expressed interest in continuing development of qvwm, we've decided to rehost qvwm somewhere else. (To be more specific, a joint SourceForge/EcolNet operation). If you're interested in qvwm, you'll probably want to be subscribed to the two mailing lists. And I've taken the presumptuous liberty of subscribing you! :-) qvw...@li... Developer's mailing list qvw...@li... CVS changes mailing list If you don't want to assist, you can unsubscribe yourself here: http://lists.sourceforge.net/mailman/listinfo/qvwm-devel http://lists.sourceforge.net/mailman/listinfo/qvwm-cvs These mailing lists are not just for EcolNet members, so it shouldn't be assumed that everyone will be able to read Spanish. qvwm's users are global and the software has been localized for 7 languages, so messages are acceptable in any language. However, I suspect you'll maximise "message interoperability" if you write them in English, or English AND your language of choice. While I've started moving some qvwm stuff to SourceForge, it's not intended to be just a SourceForge project. We would like to harness the power of both SourceForge and EcolNet to build a better qvwm. Likewise, it's not MY project, it's yours. Anything you want to do, you can do it - just ask! The usuall Open Source rules apply of course! We store our stuff in CVS (website included), and it's highly recommended that you send a diff of your qvwm changes to the mailing list for review before checkin. Also, if you have a moment, could you reply to this message and tell the other list members of your name, your experience (if any) with qvwm, your SourceForge username (for CVS access) and what you would like to help with? (see below) Many thanks, Mitch. PS: My name (if you haven't guessed) is Mitch Davis. I have administered a number of Open Source projects (including rescuing Freeciv from obscurity way back in 1997). I have used qvwm since 2000, and while I might not have much time to cut code, I still think I can add value by doing project admin work. My SourceForge username is "mjd". |
From: Sinner f. t. P. <si...@es...> - 2003-10-06 12:50:45
|
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Yes, this is a test. Can you hear me now? -- Good Salut, Sinner =2D --=20 Visit my website! http://www.ibiblio.org/sinner/=20 Running on Mandrake Linux 9.0 - Kernel 2.4.19smp Linux User # 89976 =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE/gWUgSGQa4/zQ9e8RAqH0AJ0YMlcUbP54XYDVIOsepj77UpH1xwCgvrE7 43CR/vlWH0y8hboMWvyJHjk=3D =3D5D+V =2D----END PGP SIGNATURE----- |