Replacement of identity.kde.org
Hi, We are currently preparing the replacement of the current software used for identity.kde.org (GOSA). We will replace it with brand new software, developed by Ben Cooksley himself, it's called Solena. The idea is still the same: one place to create a username/password and use that service on several other sites we roll out within KDE. The most important advantage with the new software is that we get a sane user experience, identity.kde.org has a bad user interface, resulting in several problems. We will convert all existing accounts automatically. Why this mail? To announce the new software and to announce that this weekend we will do the conversion to new system and make that active. That means that identity.kde.org will not be 100% up this weekend, and it might be that at some points we are making some minor adjustments to the sites which rely on the authentication done by identity.kde.org, resulting that you can not login into such a site for short periods of time. Any questions (or beta-testers!) are still welcome in #kde-sysadmin. Best, Tom Albers KDE Sysadmin
Reactivate your KDE bugs.kde.org account before March 30th 2012
Hi, We have recently installed a new update of the bugzilla software and we would like to ask you to reactivate your accounts. This can be done in one simple step: login on the http://bugs.kde.org site. If you don't reactivate your account before March 30th we will block your account from logging in until the password reset feature is used to set a new password. Sorry for the trouble, but we hope you will enjoy the upgrade. Best, Tom Albers KDE Sysadmin
Bugzilla upgrade.
Hi, Our bugzilla instance is an old version. We are preparing to upgrade it to a recent version. This will go in two stages. First we will perform a test upgrade. This will happen on Saturday Februari 25th. We will start at 8PM CET. We expect little inpact, though during the database conversion we expect the current bugzilla to be slower as usual. If this will becomes unworkable, we will close bugs.kde.org during this conversion. If all goes well, we want to do the final conversion on Friday March 2nd. We will start at 8PM CET. During the conversion bugs.kde.org will be unavailable. We expect a downtime of a few hours. We will know more after the test. All work will be coordinated via the #kde-sysadmin. If you want to test the new bugzilla before it goes live (/me waves at the dr.konqi developers) talk to us. Also when you have any other concerns or questions about the upgrade. Best, Tom Albers KDE Sysadmin ps. Any replies which include the word 'Redmine' will be ignored.
Re: Enabling the wiki on projects.kde.org ?
- Original Message - Hi, I'm not sure which mailing list is appropriate for this, so I try here. projects.kde.org is Redmine, and Redmine has a wiki. AFAIK the wiki is currently disabled on projects.kde.org (or can I enable it on a per-project basis and I just didn't find it ?). Can we enable the wiki please ? I created the SuperBuild project there after the Platform sprint, and having the wiki right there would IMO be a perfect place to put documentation etc. I wouldn't have to go to yet another wiki, or set up a whole website, etc. So, what's the state with the wiki on projects.kde.org ? Alex We have 3 wiki's already, techbase, userbase and communitybase. Please use those... Best, Toma -- Tom Albers KDE Sysadmin
Re: Enabling the wiki on projects.kde.org ?
- Original Message - communitybase is more for temporary stuff, as I understand it. No. Communitybase is for your project internals, like sprint organisation, meeting notes, todo lists, etc. Userbase is the interface for the users and techbase for developers. The information you provide is targeted at developers, so techbase is a perfect fit there (imho). Best, Toma -- Tom Albers KDE Sysadmin
Re: Requested Moratorium on hard to build dependency bumps for KDE 5
- Original Message - IMHO it is out of the question to ask a developer to not implement a great new feature just because the dependancies are too young. I disagree completely. I would very much welcome a policy that states that you can only depend on stuff that is available in the newest release of Fedora KUbuntu other KDE friendly distro's. Toma
Re: Rules to be approved as part of KDE Frameworks
- Original Message - On Tuesday, June 07, 2011 02:00:20 AM Aaron J. Seigo wrote: On Monday, June 6, 2011 19:41:15 Maksim Orlovich wrote: * all new features will be developed using the recommended git workflow (pending publication; Cornelius is working on that one); Those rules might seem like a strong departure from what we're used to. On the other hand, if you look at them closely, they are merely making explicit changes to our habits which already happened a while ago during the Qt 3 to Qt 4 port These two things don't really go well together now, do they? a documented git workflow is new, but needed. Yes, yes, yes. 100 %. We really need that. For git newbies (like me) and to avoid total chaos. And so that it stays possible to contribute to any KDE projects without having to figure out for each single project how they prefer to use git and branches etc. That's not what is happening. It's a workflow for the frameworks, the rest of KDE is invited to follow. So you still have to find out for each single project how they prefer to use git and branches. (afaics) Best, -- Tom Albers KDE Sysadmin
Objections to stop creating nightly tarballs from svn?
Hi, As known, sysadmin is trying to transfer services away from ktown. One of the current tasks of ktown is to provide nightly snapshots of svn to this location: ftp://ftp.kde.org/pub/kde/unstable/snapshots/ We are wondering if it is worth to move this service or to stop it. Arguments to stop it are: 1) needs svn checkout on the replacement server and 2) less and less usage of it as svn is 'old' technology. The only user we know of these snapshots is kdesrc-build, and I'm pretty sure that app will cope fine without the tarballs. If there are other users, we would like to know. Does anyone feel this service should remain? If so, that's fine, but we just need some arguments for it. projects.kde.org does create tarballs for the git repo's and will continue to do so. This is only about the svn counterpart. Best, -- Tom Albers KDE Sysadmin
Upcoming freezes KDE 4.7
Hi, Just to let you all know that some freezes are coming up next week in preparation of the first 4.7 beta release. Some items of importance: -- Thursday, May 12, 2011: KDE 4.7 Dependency Freeze From this moment on it is not allowed to add new dependencies or bump dependencies versions. It is possible to get an exception for this. Post the patch to reviewboard and add the release-team as reviewer. We will check if the dependency is needed and is available on all platforms. In other words: If you have a feature that requires a new dependency or a version of a dependency that is higher than currently checked for in the build system, you need to have committed this change before this date. Thursday, May 12, 2011: KDE 4.7 Hard Feature Freeze Trunk is frozen for all feature commits, even those listed in the planned feature document. Only bug fixes are allowed. Thursday, May 19, 2011: KDE 4.7 Beta 1 Tagging Trunk is frozen for beta release tagging. Only urgent fixes, such as those fixing compilation errors, should be committed. The usual beta rules apply as soon as the Beta tarballs have been generated. Wednesday, May 25, 2011: KDE 4.7 Beta 1 Release The beta becomes available for general consumption. -- The rest of the schedule is available at: http://techbase.kde.org/Schedules/KDE4/4.7_Release_Schedule Or add a reference to the always up-to-date ics file to your calendar-app: http://www.kde.org/releaseschedule.ics Best, -- Tom Albers KDE Sysadmin
Re: Top 15 Mailinglists with messages in moderation May 1st
- Original Message - [Tom Albers - Sonntag, 1. Mai 2011 16:00:57] Hi, New month, new list. If lists are unused, let me know, I will delete them. If someone wants to help with moderation for any of these list, let me know as well. 19 kde-news-de You can put me in change here. I will look into the moderation list ... but the list itself seems pretty dead so, let's see how it turns out. I will contact you, if I figured it out. Great, password sent in a private mail. Best. -- Tom Albers KDE Sysadmin
Re: Empty merges per release
- Original Message - (oh well, who cares, given all that scripty crap in the history) I consider our translations very important for KDE. Would be nice if people -in general- do not consider translations and the contributors working on that as second class community members. Calling the scripty commits 'crap' is weird, really. Best, -- Tom Albers KDE Sysadmin
Re: Replacement for Qt's Undo Framework
- Original Message - On Monday, April 25, 2011 22:12:55 Alexander Potashev wrote: What do you think about inclusion of KUndo*2 into kdelibs? we really don't want more duplication of code and effort between Qt and kdelibs, and we certainly don't want forks of Qt code in kdelibs. Forks? It does sound like to me as we take the base class from Qt and improve it for usage within KDE. We've done that for years and years. Does this now imply that that's bad practice and kdelibs is closed for such classes? Best, -- Tom Albers KDE Sysadmin
Shell access to ktown.kde.org will be shut down.
Hi, In the past sysadmin has given personal shell access [1] to ktown.kde.org to some people. Currently we are making inventory on ktown and would like to know if these shell accounts are still used and for what reason. Please reply to sysad...@kde.org if you have access and indicate the reason. It's important that you reply if you have access or had access in the past, since ktown is end of life and you will lose access / data otherwise. Best, -- Tom Albers KDE Sysadmin [1] packagers have access on ktown too, you don't have to respond to this email in that case.
Thursday, April 28, 2011: KDE 4.7 Soft Feature Freeze
Hi, Just a reminder that the soft feature freeze is rapidly approaching: http://techbase.kde.org/Schedules/KDE4/4.7_Release_Schedule#Thursday.2C_April_28.2C_2011:_KDE_4.7_Soft_Feature_Freeze Add your features to the Feature Plan so you can work on it until the hard freeze here: http://techbase.kde.org/Schedules/KDE4/4.7_Feature_Plan For the complete schedule, now and in the future, add the ics to your favorite calendaring app: http://www.kde.org/releaseschedule.ics Best, Toma -- Tom Albers KDE Sysadmin
Re: 4.6 branches created in git again
- Original Message - Come to think of it, perhaps it's the Release Team who should have final say on the branch naming, they may have requirements that we haven't thought of? I think I can say on behalf of the release-team, that we don't care much as long as it is consistent over all git repo's and ideally done before 4.6.2 has to be tagged (31st) iow, don't delay the renaming, just do it IMHO. Though if it needs a reclone for everyone we need to pick a date and *communicate* it. Let's say this weekend? Best, -- Tom Albers KDE Sysadmin
Re: 4.6 branches created in git again
- Original Message - On Mon, Mar 21, 2011 at 05:57:03PM +, Tom Albers wrote: Though if it needs a reclone for everyone we need to pick a date and *communicate* it. Let's say this weekend? reclone? hello? I think I've stated my question in a way that makes clear that I did not know the answer. I did not know if the renaming of branches would make the existing shasums invalid. Hence my formulation. Git might be known by you inside out, but please note that is not the case for everyone. I personally think it's inappropriate to make fun of someone less knowledgeable. If you want to be short, just leave out your whole line 'reclone? hello?' and keep the instructions. It brings the point across too and I feel less dumb. Best, -- Tom Albers KDE Sysadmin
Re: 4.6 branches created in git again
- Original Message - On Mon, Mar 21, 2011 at 07:06:51PM +, Tom Albers wrote: Git might be known by you inside out, but please note that is not the case for everyone. it's one thing not to know everything inside out and another not to understand what a ref actually is ... I'm a team player, that means I trust on others to educate me, correct me and that also means I don't have to learn git. It seems the 'KDE Community' feeling I once appreciated being part of is declining by the day. -- Tom Albers KDE Sysadmin
Re: 4.6 branches created in git again
- Original Message - On Mon, Mar 21, 2011 at 08:24:24PM +, Tom Albers wrote: I'm a team player, that means I trust on others to educate me, correct me you may have noticed that all the job ads looking for team players also emphasize independence and self-motivation. i.e., the ability to complete day-to-day tasks on your own. My day-to-day task was to be helpful in this thread. And I could complete that just fine without knowing what a ref is. The only part I was not sure of I clearly indicated that someone else needs to look at it. that also means I don't have to learn git. hearing that from a sysadmin makes me *really* scared. The sysadmin team has knowledge enough about git and I'm happy to leave the things I don't know to them. but then, kde always had the culture of fixing mistakes instead of avoiding them (as in, stuff that gets committed). Yes, this is different than a commercial company indeed. we have about 500 backups (clones) of the repositories and nobody except me seems to care whether the scm history is useful anyway. From close by I've seen several git repo's being declined by fellow sysadmins and people from kde-git, because the history was incomplete or stuff was missing. I've seen several discussions about what would be the 'right' history and a lot of people cared. I think you are mistaken here. so whatever - let's have fun! had your daily pull --rebase screwup already? no? way to go ... Let me be clear: I'm very careful about the stuff I do with git and I understood the discussion about the --rebase problem just fine, after this list made clear I had to watch out for that. I actually did research and talked to people to understand it, because the discussion was a bit confusing to me. Best, -- Tom Albers KDE Sysadmin
Re: Top 15 Mailinglists with messages in moderation
Hi, - Original Message - On March 10, 2011 12:49:16 John Layt wrote: I've offered previously to mod those lists, I'd be happy to take them on now. I think I also previously said we can get rid of the kde-print list, it's had about 5 mails in the 18 months so I don't think it will be missed. I'd rather keep the devel list going for bug triage, and I will have news about possible new development work on printing in the near future for which the list may be useful. Tom, from my part, I believe it is indeed better to go with John's suggestions. While being there, removing my contact from the admins of kde- print-devel ml would be very much appreciated. Thanks a lot. -- Cristian Tibirna KDE developer .. tibi...@kde.org .. http://www.kde.org I've deleted kde-print mailinglist and made John the admin of kde-print-devel. Password sent in private mail. Thanks both! Best, -- Tom Albers KDE Sysadmin
FYI: Jamaica down this Saturday
Hi, jamaica (which hosts www.kde.org and a dozen more sites, not dot.kde.org, forum.kde.org or planet) will be without power between 10:00 and 17:00 CET this Saturday. The sysadmins there say they will be replacing a UPS, another source says they will move the datacenter. In any case I guess the server won't be reachable. I will try to move www.kde.org to another box, but it is uncertain we will manage to do this in time. This could also cause an occasional longer delay in DNS resolving. Best, -- Tom Albers KDE Sysadmin
Re: Top 15 Mailinglists with messages in moderation
- Original Message - Tom Albers t...@kde.org writes: 34 kfm-devel I could help with this one. Awesome, password mailed in separate mail. Best, -- Tom Albers KDE Sysadmin
Bugzilla and identity.kde.org down this Saturday.
Hi, We've received a note that immanuel.kde.org will be down this Saturday. From 7.30h CET up to 16h CET the hosting provider has planned work on the power supply to the hosting location. The services affected are: bugs, identity, docs, promo, events, games, home and rsync.kde.org A nasty side effect is that identity.kde.org is providing authentication services to several other sites, like git.reviewboard.kde.org and projects.kde.org. This means logged in users are lucky, but you can not log in if you are logged out. Unfortunately we have not had time to setup a replication for identity.kde.org and it's not going to happen before this outage. Best, -- Tom Albers KDE Sysadmin
Re: A Qt replacement for KGlobal::ref and deref
I agree, as long as the reference count is tied to the window count. People should understand that a GUI application running with no GUI makes no sense and should be avoided. RSIBreak has no GUI, only a stats window and a config window. It only has a tray icon. Probably the famous exception to the rule? Do I need to change anything in my app for this? Best, -- Tom Albers
Re: reminder: git workflow irc meeting on Sunday
- Original Message - hi all... just a quick and friendly reminder that the git workflow irc meeting is on for Sunday the 13th starting at 20:00 UTC on irc.freenote.net in #kde-git. see you all there! :) -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks Hi, Is there an agenda for the meeting, or some documentation? If everyone gets a chance to explain their preferred git workflow and we are going to be a discussion afterwards and pick one, I bet this is a meeting that will take forever with loads of frustration and chaos. Any thoughts on that? Best, -- Tom Albers KDE Sysadmin
Re: splitting up kdebase in git
- Original Message - Hi, Our default wallpapers used to be part of kdebase/workspace, but during the git migration they've been removed from workspace due the size of that directory. Wallpapers can't be kept in a git repository because every time a git repository is cloned all the history (including old wallpapers) is cloned. So actually wallpapers are nowhere, should we move wallpapers back to trunk/KDE/kdebase/workspace? Bye, Davide Bettio. Maybe just a tarball somewhere? SVN won't stay around, so we need another solution i think. Best, -- Tom Albers KDE Sysadmin
Re: splitting up kdebase in git
- Original Message - On Saturday, February 12, 2011 19:12:41 Tom Albers wrote: - Original Message - Hi, Our default wallpapers used to be part of kdebase/workspace, but during the git migration they've been removed from workspace due the size of that directory. Wallpapers can't be kept in a git repository because every time a git repository is cloned all the history (including old wallpapers) is cloned. So actually wallpapers are nowhere, should we move wallpapers back to trunk/KDE/kdebase/workspace? Bye, Davide Bettio. Maybe just a tarball somewhere? SVN won't stay around, so we need another solution i think. I thought we were keeping SVN around for translations? Or will they simply migrate after the rest of the modules have? I personally have no intention to maintain two revision control systems. -- Tom Albers KDE Sysadmin
Re: Top 15 Mailinglists with messages in moderation
Ok. Thanks for that. kmobiletools has been removed now. Best, Toma - Original Message - Hi, I've talked to current maintainer (Quentin Denis) about this. And this is his response: anything related to KMT can be removed, the code is now pure playground I dont need that mailing list. So I guess one can remove it. Cheers, Dinesh On Wed, Feb 2, 2011 at 4:37 AM, John Layt johnl...@googlemail.com wrote: On Tuesday 01 February 2011 13:45:27 George Goldberg wrote: 41 kdelibs-bugs This is a very useful list for bug triagers - I can volunteer to moderate it if no-one else is currently doing it. ditto, if more than 1 or 2 mods are needed. John. -- Tom Albers KDE Sysadmin
Re: Top 15 Mailinglists with messages in moderation
- Original Message - On Tuesday 01 February 2011 13:01:32 Tom Albers wrote: 29 kde-java I think we can safely delete that one. We don't have Java bindings anymore and the main bindings ML is kde-bindings. A quick glance at those mails would still be cool (can I somehow view them?). It was only spam, facebook and linkedin friend requests, and up to 80% discount on some medicine. I've deleted the list. Best, -- Tom Albers KDE Sysadmin
Re: Top 15 Mailinglists with messages in moderation
- Original Message - On Tuesday 01 February 2011 13:45:27 George Goldberg wrote: 41 kdelibs-bugs This is a very useful list for bug triagers - I can volunteer to moderate it if no-one else is currently doing it. ditto, if more than 1 or 2 mods are needed. Added. Thanks! -- Tom Albers KDE Sysadmin
Re: Top 15 Mailinglists with messages in moderation
- Original Message - 20 kde-embedded The maintainers email (p...@kde.org) is bouncing. Do we need this list? I see almost no activity for the last months.. Best, -- Tom Albers KDE Sysadmin
Re: Review Request: Workaround for the hang (freeze) when opening VLC's file dialog under KDE...
- Original Message - It is when I have to unnecessarily type more than I have to. Seriously this is getting to be annoying and I do not mean you personally. These rigid and brittle coding styles. One project says no braces for single line statements and another says the complete opposite. I have no problem with some common sense coding style rules, but please spare me from such nonsense micro management of each and every line of code, specially since the people working on kdelibs should in the least be well versed about the pitfalls of using or not using braces, even for single line statements. For new code, we very much like to follow: http://techbase.kde.org/Policies/Kdelibs_Coding_Style Which can be different in other area's within KDE, which I hope one day will not be the case. And before you ask, yes, I very much would like a 'astyle' run on all the code in kdelibs to settle this once and for all. Best, -- Tom Albers
Fwd: Top 15 Mailinglists with messages in moderation
The monthly overview - Forwarded Message - 342 decibel 80 kmobiletools 47 kde-contests 46 kde-i18n-pt 43 kgraphviewer-devel 41 kdelibs-bugs 32 kde-usability 31 dot-stories 29 plasma-bugs 29 kde-java 20 kde-embedded 19 kde-openserver 19 kde-news-de 19 kde-france-ca 18 season-of-kde -- Tom Albers KDE Sysadmin
anongit.kde.org now updating instantly sorry
Hi All, An apology is in place. I blamed all you guys for cloning from the wrong server in below mails, but in fact it looks like a problem on our side with the way we updated the anongit mirrors. We have changed it now. Old situation: anongit was pulling the changes every 5 minutes. which actually took 6 minutes to complete, hence the increase in load. Especially when people were pushing, which made the negative loop accelerate. New situation: the commits are now instantly pushed to the anongit mirrors. This means that whenever you push, the anongit mirrors directly have that change. No 5 minutes delay anymore. Unless a connectivity problem arises, but that will be corrected after 20 minutes or so. Again, sorry for blaming you guys. Instead I can now say: bring it on :) Best, Toma Sysadmin team - Original Message - Hi, git.kde.org will no longer accept clone requests. It will give you an error. I will leave this in place for the next week or so, until everyone has their clones. Best, Toma - Original Message - Hi, Before git.kde.org goes down I like to urge everyone to stop doing clones from git.kde.org. Please use anongit.kde.org for reads and git.kde.org only for writes as explained here: http://community.kde.org/Sysadmin/GitKdeOrgManual#Let_Git_rewrite_URL_prefixes The system is now on the edge of breaking. Best, -- Tom Albers KDE Sysadmin Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe -- Tom Albers KDE Sysadmin -- Tom Albers KDE Sysadmin
Re: kdelibs, kdebase moving to Git this Saturday
- Original Message - On 1/30/2011 1:17 PM, Marco Martin wrote: in the runtime repository, the pics directory doesn't seem available, but the main CMakelist.txt still looks for it. kde-runtime is currently set read-only for that and other reasons, the conversion seems to be flawed. Unfortunately the guys writing the conversion script are in bed or afk right now. Additionally we've made kde-workspace read-only too, as #kwin found a missing file, which means we have a problem there too. I'ld like to ask everyone to check the repo's NOW, so the conversion people can have a full list of problems and we don't have to repush 3 times this week, but only once. Best, -- Tom Albers KDE Sysadmin
Re: Usefulness of Subject-header of git commit mails
- Oorspronkelijk bericht - On 1/23/2011 9:30 PM, Milian Wolff wrote: What was broken? Nothing as far as Commitfilter is concerned. Commitfilter actually acts on the X-Commit-Directories headers, not the mail subject. This header was actually somewhat broken in the old mails, it has been fixed now as part of the hooks rewrite that also brought with it the mail subject format change. In total the rewrite fixed numerous bugs, many of which were in the emails (the old implementation wasn't written by the sysadmin team): There were problems with keyword parsing, CCMAIL recipients were not all CC'd to the kde-commits mail but rather individual, new mails were sent, headers with non-Unicode characters in them weren't en- coded properly, authors didn't get CC'd if the hook found something unsafe in the diff, license detection for new files was suboptimal, etc. The rewrite also improved performance by orders of magnitude, especially in the auditing steps, and added new features. For example the mails now mention who pushed a commit. Yet all we hear about is rather aggressive whining about the mail subjects ... yep, being a sysadmin is tons of fun. Hey, look at it differently. If everyone is talking about the subject as the biggest problem, Ben really, really did a great job. I was expecting a hell of a lot more bugs in the brand new code. People complaining about the subject made me smile actually. It is like building a gigantic big house and the owners are complaing about the color of the doorbell. Ill settle for that. Best, toma
kde-qt will move from gitorious and end of life for kde-developers
Hi, As announced last month, kdelibs and kdebase will move real soon now to git (this weekend?). At the same time kdelibs moves to git, sysadmin will also move kde-qt[1] from gitorious to git.kde.org. You would need to fix your setup anyway, so doing that for both at the same time makes sense. This will be the only announcement about this. At the same time we will also remove the kde-developers group from gitorious. The remaining KDE projects *have* to migrate to git.kde.org before that. More specific, as far as we know this is about: silk, owncloud and direction (that one abandoned?). They are free to continue on gitorious of course, but without the kde-developers group, which gives most of access to those repo's. We've tried to approach all of them without success in the past. Best. Toma [1] http://qt.gitorious.org/+kde-developers/qt/kde-qt -- Tom Albers KDE Sysadmin
Re: [Digikam-devel] Suspending mailinglists due to lack of moderators.
- Original Message - On Saturday 01 January 2011 21:25:23 Tom Albers wrote: 28 dot-stories What's the differences between that list and kde-promo? Do we really need a dot-stories mailing list? Regards Damnshock I think it is an internal list where new dot submissions end up, not sure though. -- Tom Albers KDE Sysadmin
Re: Suspending mailinglists due to lack of moderators.
- Original Message - Note that if you object, you are volunteering for taking over moderation. 42 quanta 32 quanta-devel Make me the admin/moderator of these two please. Done. Thanks. -- Tom Albers KDE Sysadmin
Re: release schedule calendar
- Original Message - It would be helpful if the dates would include version numbers so e.g. todays freeze would be Documentation freeze for 4.6.0 or something like that. Yes, the schedule generation software does not include the version number yet. I will add it, so it will be fixed for the 4.7 schedule. Also I only see the 4.6 dates in there, the next 4.5 dates seem to be missing completely. Yes, the 4.5 schedule was not generated with the software. 4.6 was the first... Best, -- Tom Albers KDE Release Team
Re: wrong diffs for python on the kde-commits list
- Original Message - but in Python, leading whitespace has a meaning, and the diff on kde-commits is just wrong. We have chosen that the advantages of -b are more than the disadvantages of it. For more details browse this lists archive. So - does anybody actually apply those diffs? No. Best, -- Tom Albers KDE Sysadmin
