Re: [Midnight Commander] #126: Merge ./lib/ChangeLog with ./ChangeLog
On Sun, Jan 04, 2009 at 08:54:33PM -, Ticket System wrote: This is also an issue which should be fixed in 4.6.2 ( a mostly bugfix release) uhm, either it is a pure bugfix release and gets called 4.6.2 or it contains features (or internal reorganization) and gets called 4.7. looks all like 4.7 to me ... ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #130: FHS-Break: global config belongs into ${sysconfdir}/mc
#130: FHS-Break: global config belongs into ${sysconfdir}/mc
--+-
Reporter: metux| Owner:
Type: defect | Status: new
Priority: minor| Milestone:
Component: mc-core | Version: 4.6.1
Resolution: |Keywords:
Blocking: | Blockedby:
--+-
Comment(by slavazanko):
See global-config-into-sysconfdir-rev1.patch.
This patch will agregate ideas from Fedora-10 and ru-mc-fork patches.
--
Ticket URL: www.midnight-commander.org/ticket/130#comment:1
Midnight Commander www.midnight-commander.org
Midnight Development Center
___
Mc-devel mailing list
http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #65: savannah: Pascal syntax highlighting update
#65: savannah: Pascal syntax highlighting update --+- Reporter: slavazanko | Owner: winnie Type: enhancement | Status: accepted Priority: minor| Milestone: 4.6.2 Component: mc-core | Version: Resolution: |Keywords: Blocking: | Blockedby: --+- Comment(by Enrico Weigelt): For what language specification is this patch ? Back from my old pascal times (about 10yrs ago), there was neither anything like finalisation nor overloading. (read|write)(ln|) always have been normal functions, just Borland broke the standard by adding some compiler magic, IMHO ... cu -- Ticket URL: /ticket/65#comment: Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #65: savannah: Pascal syntax highlighting update
#65: savannah: Pascal syntax highlighting update --+- Reporter: slavazanko | Owner: winnie Type: enhancement | Status: accepted Priority: minor| Milestone: 4.6.2 Component: mc-core | Version: Resolution: |Keywords: Blocking: | Blockedby: --+- Comment(by slavazanko): I think we also should add keywords from delphi and freepascal to this file.. Just add those keywords and attach new patch (you may make new branch). Is this okay? Any idea okay, IMHO :) -- Ticket URL: www.midnight-commander.org/ticket/65#comment:8 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #144: Add procmail syntax highlighting
#144: Add procmail syntax highlighting ---+ Reporter: Patrick Winnertz win...@debian.org | Owner: winnie Type: defect| Status: new Priority: major | Milestone: 4.6.2 Component: mc-core | Version: 4.6.1 Resolution:|Keywords: Blocking:| Blockedby: ---+ Changes (by Patrick Winnertz): * owner: = winnie * milestone: = 4.6.2 Comment: Last try to set owner and milestone via email. -- Ticket URL: www.midnight-commander.org/ticket/144#comment: Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #137: [PATCH] (git) Fixup homepage url
#137: [PATCH] (git) Fixup homepage url ---+ Reporter: enrico.weig...@zaphod.local, metux IT service weig...@metux.de | Owner: metux Type: task | Status: assigned Priority: critical | Milestone: 4.6.2 Component: mc-core | Version: Resolution: |Keywords: Blocking: | Blockedby: ---+ Comment(by slavazanko): Reassing of ticket mean other developer (or visitor) need to rework patch, give more info in comment, continue working with ticket, etc... After this complete, ticket reassigning back. Or not reassign back, in this case assigner (if developer) need to apply patch (create branch). About named of branches... I think, simply to 'Summary' of ticket... or simular to patch name... For example:[[BR]] git-branch 'fixup-homepage-url' # all letters in lower case[[BR]] or[[BR]] git-branch 'git08123111-new-homepage'[[BR]] P.S. This additional to workflow in mail list... details appear in the process of works:) -- Ticket URL: www.midnight-commander.org/ticket/137#comment:6 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #99: enable git checkout via http
#99: enable git checkout via http -+-- Reporter: winnie | Owner: winnie Type: task| Status: closed Priority: minor | Milestone: Component: adm | Version: Resolution: fixed |Keywords: Blocking: | Blockedby: -+-- Changes (by winnie): * status: testing = closed -- Ticket URL: www.midnight-commander.org/ticket/99#comment:4 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #135: [PATCH] Drop bundled libintl
#135: [PATCH] Drop bundled libintl --+- Reporter: metux| Owner: metux Type: enhancement | Status: accepted Priority: minor| Milestone: 4.6.2 Component: mc-core | Version: 4.6.1 Resolution: |Keywords: Blocking: | Blockedby: --+- Comment(by Enrico Weigelt): * Ticket System tick...@midnight-commander.org schrieb: ACK. The patch isn't that big+complicated. -- Ticket URL: www.midnight-commander.org/ticket/135#comment: Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #139: compatibility_move_mc_files() still needed ?
#139: compatibility_move_mc_files() still needed ? --+- Reporter: metux| Owner: slavazanko Type: task | Status: accepted Priority: minor| Milestone: 4.6.2 Component: mc-core | Version: 4.6.1 Resolution: |Keywords: Blocking: | Blockedby: --+- Changes (by slavazanko): * owner: winnie = slavazanko Comment: See attached patch. Also, branch 'compatibility_move_mc_files' was created. -- Ticket URL: www.midnight-commander.org/ticket/139#comment:4 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #139: compatibility_move_mc_files() still needed ?
#139: compatibility_move_mc_files() still needed ? --+- Reporter: metux| Owner: Type: task | Status: new Priority: minor| Milestone: 4.6.2 Component: mc-core | Version: 4.6.1 Resolution: |Keywords: Blocking: | Blockedby: --+- Comment(by Patrick Winnertz): Am Sonntag 04 Januar 2009 10:28:37 schrieb Ticket System: This function was created back in 2002 (merged with function do_compatibility_move which exists longer). As the logs suggested this move to .mc was done at least in 1998 (see commit 551dec7a7fd7c555f20774418c6f1c13cec9ab48). This is more than 10 years ago... I think we can remove this function without doing anything bad. Is someone uncomfortable with this? Greetings Winnie -- Ticket URL: www.midnight-commander.org/ticket/139#comment: Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #139: compatibility_move_mc_files() still needed ?
#139: compatibility_move_mc_files() still needed ? --+- Reporter: metux| Owner: winnie Type: task | Status: accepted Priority: minor| Milestone: 4.6.2 Component: mc-core | Version: 4.6.1 Resolution: |Keywords: Blocking: | Blockedby: --+- Changes (by winnie): * owner: = winnie * status: new = accepted -- Ticket URL: www.midnight-commander.org/ticket/139#comment:3 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #126: Merge ./lib/ChangeLog with ./ChangeLog
#126: Merge ./lib/ChangeLog with ./ChangeLog --+- Reporter: metux| Owner: Type: defect | Status: new Priority: trivial | Milestone: 4.6.2 Component: mc-core | Version: 4.6.1 Resolution: |Keywords: Blocking: | Blockedby: --+- Changes (by winnie): * milestone: = 4.6.2 Comment: This is also an issue which should be fixed in 4.6.2 ( a mostly bugfix release) -- Ticket URL: www.midnight-commander.org/ticket/126#comment:1 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #14: savannah: Cannot copy to a directory called *
#14: savannah: Cannot copy to a directory called * -+-- Reporter: slavazanko | Owner: Type: defect | Status: new Priority: major | Milestone: VFS Standardisation Component: vfs | Version: Resolution: |Keywords: Blocking: | Blockedby: -+-- Changes (by winnie): * milestone: = VFS Standardisation -- Ticket URL: www.midnight-commander.org/ticket/14#comment:1 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #139: compatibility_move_mc_files() still needed ?
#139: compatibility_move_mc_files() still needed ? --+- Reporter: metux| Owner: Type: task | Status: new Priority: minor| Milestone: 4.6.2 Component: mc-core | Version: 4.6.1 Resolution: |Keywords: Blocking: | Blockedby: --+- Changes (by winnie): * milestone: = 4.6.2 Comment: Does anybody know when the files were not in .mc/ ? Since I use linux (7 years ago) this stuff was in .mc/ -- Ticket URL: www.midnight-commander.org/ticket/139#comment:1 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
[Midnight Commander] #144: Add procmail syntax highlighting
#144: Add procmail syntax highlighting --+- Reporter: Patrick Winnertz win...@debian.org | Owner: Type: defect| Status: new Priority: major | Milestone: Component: mc-core | Version: 4.6.1 Keywords:|Blocking: Blockedby:| --+- Hey, This patch enables syntaxhighlighting for procmail files, This patch has it's origin also in debian. Please review and comment. Greetings Winnie -- Ticket URL: www.midnight-commander.org/ticket/144 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #136: ***ignore me***
#136: ***ignore me*** ---+ Reporter: enrico.weig...@zaphod.local, metux IT service weig...@metux.de | Owner: metux Type: task | Status: testing Priority: trivial | Milestone: Component: adm | Version: Resolution: invalid |Keywords: Blocking: | Blockedby: ---+ Comment(by Patrick Winnertz): Hey Enrico, Next time simply close it as invalid before you assign or accept it. After accepting or assigning a ticket it's not longer possible to mark it as closed. Then you've to go through testing. :) It's not optimal but I guess the best. Greetings Winnie -- Ticket URL: /ticket/136#comment: Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #131: ***TRASH*** (was: FHS-Break: global config belongs into ${sysconfdir}/mc)
#131: ***TRASH*** +--- Reporter: metux | Owner: metux Type: defect | Status: testing Priority: minor | Milestone: Component: mc-core| Version: 4.6.1 Resolution: duplicate |Keywords: Blocking: | Blockedby: +--- -- Ticket URL: http://www.midnight-commander.org/ticket/131#comment:4 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #55: savannah: tab completion vs. spaces and escaping
#55: savannah: tab completion vs. spaces and escaping -+-- Reporter: slavazanko | Owner: Type: defect | Status: new Priority: major | Milestone: VFS Standardisation Component: mc-core | Version: Resolution: |Keywords: Blocking: | Blockedby: -+-- Changes (by winnie): * milestone: = VFS Standardisation -- Ticket URL: www.midnight-commander.org/ticket/55#comment:2 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #136: ***TRASH***
#136: ***TRASH*** ---+ Reporter: enrico.weig...@zaphod.local, metux IT service weig...@metux.de | Owner: metux Type: task | Status: closed Priority: trivial | Milestone: Component: adm | Version: Resolution: invalid |Keywords: Blocking: | Blockedby: ---+ Changes (by winnie): * status: testing = closed -- Ticket URL: http://www.midnight-commander.org/ticket/136#comment:7 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #139: compatibility_move_mc_files() still needed ?
#139: compatibility_move_mc_files() still needed ? --+- Reporter: metux| Owner: slavazanko Type: task | Status: accepted Priority: minor| Milestone: 4.6.2 Component: mc-core | Version: 4.6.1 Resolution: |Keywords: Blocking: | Blockedby: --+- Comment(by Patrick Winnertz): As written prior, I think we can savely remove this function, therefore: +1 -- Ticket URL: www.midnight-commander.org/ticket/139#comment: Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #141: [PATCH] Moving doc files (001)
#141: [PATCH] Moving doc files (001) ---+ Reporter: enrico.weig...@zaphod.local, metux IT service weig...@metux.de | Owner: slavazanko Type: defect | Status: accepted Priority: major | Milestone: Component: mc-core | Version: 4.6.1 Resolution: |Keywords: Blocking: | Blockedby: ---+ Changes (by slavazanko): * owner: = slavazanko * status: new = accepted Old description: This patch moves documentation files from toplevel to doc/ and manpages from doc/ to doc/man New description: This patch moves documentation files from toplevel to doc/ and manpages from doc/ to doc/man -- -- Ticket URL: www.midnight-commander.org/ticket/141#comment:2 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #137: [PATCH] (git) Fixup homepage url
#137: [PATCH] (git) Fixup homepage url ---+ Reporter: enrico.weig...@zaphod.local, metux IT service weig...@metux.de | Owner: metux Type: task | Status: assigned Priority: critical | Milestone: 4.6.2 Component: mc-core | Version: Resolution: |Keywords: Blocking: | Blockedby: ---+ Changes (by winnie): * owner: = metux * status: new = assigned Comment: Tested on master and works fine.. As far as I can see this were all places where the url has to be changed.. Therefore: +1 @Enrico? I've assigned you to the ticket. I guess this is what you wanted? :) Next time simply accept it ;-) -- Ticket URL: http://www.midnight-commander.org/ticket/137#comment:4 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #142: Syntax highlighting for debian specific files
#142: Syntax highlighting for debian specific files ---+ Reporter: Patrick Winnertz win...@debian.org | Owner: winnie Type: enhancement | Status: new Priority: major | Milestone: 4.6.2 Component: mc-core | Version: 4.6.1 Resolution:|Keywords: Blocking:| Blockedby: ---+ Changes (by Patrick Winnertz): * owner: = winnie * type: defect = enhancement * milestone: = 4.6.2 Comment: Am Montag 05 Januar 2009 14:23:24 schrieb Ticket System: -- Ticket URL: www.midnight-commander.org/ticket/142#comment: Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Trac - remove crap tickets
* Patrick Winnertz win...@debian.org schrieb: Am Sonntag 04 Januar 2009 09:44:43 schrieb Enrico Weigelt: Hi folks, is it possible to remove certain crap tickets (I mean those which are *really* crap, like testings, accidential double-posts, etc) ? Yes.. deleting via shell should be possible for me :) Which ticket should be removed? All those which are marked with ***TRASH***. You could hack up a little script for that which runs peridically. So removing a ticket is triggered just by renaming it to ***TRASH***. cu -- - Enrico Weigelt== metux IT service - http://www.metux.de/ - Please visit the OpenSource QM Taskforce: http://wiki.metux.de/public/OpenSource_QM_Taskforce Patches / Fixes for a lot dozens of packages in dozens of versions: http://patches.metux.de/ - ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #141: [PATCH] Moving doc files (001)
#141: [PATCH] Moving doc files (001) ---+ Reporter: enrico.weig...@zaphod.local, metux IT service weig...@metux.de | Owner: slavazanko Type: defect | Status: testing Priority: major | Milestone: Component: mc-core | Version: 4.6.1 Resolution: duplicate |Keywords: Blocking: | Blockedby: ---+ Changes (by slavazanko): * status: accepted = testing * resolution: = duplicate Comment: duplicate #140 -- Ticket URL: www.midnight-commander.org/ticket/141#comment:3 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #144: Add procmail syntax highlighting
#144: Add procmail syntax highlighting ---+ Reporter: Patrick Winnertz win...@debian.org | Owner: Type: defect| Status: new Priority: major | Milestone: Component: mc-core | Version: 4.6.1 Resolution:|Keywords: Blocking:| Blockedby: ---+ Comment(by Patrick Winnertz): Am Montag 05 Januar 2009 14:48:52 schrieb Ticket System: Maybe it works this way.. :) Greetings -- Ticket URL: www.midnight-commander.org/ticket/144#comment: Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #144: Add procmail syntax highlighting
#144: Add procmail syntax highlighting ---+ Reporter: Patrick Winnertz win...@debian.org | Owner: Type: defect| Status: new Priority: major | Milestone: Component: mc-core | Version: 4.6.1 Resolution:|Keywords: Blocking:| Blockedby: ---+ Comment(by Patrick Winnertz): I'll work on this.. Hopefully this works now (if not I've to read a bit more doku about email2trac. Greetings -- Ticket URL: www.midnight-commander.org/ticket/144#comment: Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #135: [PATCH] Drop bundled libintl
#135: [PATCH] Drop bundled libintl --+- Reporter: metux| Owner: metux Type: enhancement | Status: accepted Priority: minor| Milestone: 4.6.2 Component: mc-core | Version: 4.6.1 Resolution: |Keywords: Blocking: | Blockedby: --+- Changes (by winnie): * milestone: = 4.6.2 Comment: I think this should be fixed until we release 4.6.2. -- Ticket URL: www.midnight-commander.org/ticket/135#comment:5 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #144: Add procmail syntax highlighting
#144: Add procmail syntax highlighting ---+ Reporter: Patrick Winnertz win...@debian.org | Owner: winnie Type: defect| Status: accepted Priority: major | Milestone: 4.6.2 Component: mc-core | Version: 4.6.1 Resolution:|Keywords: Blocking:| Blockedby: ---+ Changes (by winnie): * status: new = accepted Old description: Hey, This patch enables syntaxhighlighting for procmail files, This patch has it's origin also in debian. Please review and comment. Greetings Winnie New description: Hey, This patch enables syntaxhighlighting for procmail files, This patch has it's origin also in debian. Please review and comment. Greetings Winnie -- -- Ticket URL: www.midnight-commander.org/ticket/144#comment:5 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: RFC: updated workflow [WAS: Re: git+patch workflow]
Am Montag 05 Januar 2009 15:13:48 schrieb Enrico Weigelt: * Oswald Buddenhagen o...@kde.org schrieb: Hi, delete *the* stable branch, but not the concept of stable branches per se. doing so would mean that once you merged a feature patch to master, you cannot do a bugfix release any more until you make a feature release (*). to keep the option of bugfix releases open Actually, I dislike that idea. Instead we should declare, that 'master' branch is *always* what becomes the next release. We just have to take care that it's always in a state that it could be released ASAP - so: *no* development there. New features only get committed if they're really ready to get into next release (which in theory could come any second). Well.. I like the idea of mc-4.6 stable branch quite much as we can then do point releases there which is only bugfixing and do active development in master on e.g. utf8 support or.. or or... This has this advantage: - we release mc-4.6.2 from mc-4.6 branch Tested utf8 very much and include it in master - there is now a smaller issue but we doesn't want to release e.g .4.7 (with utf8) yet -- make a pointrelease with that fix applied and work further on master With your scenario we have troubles here, because we can't make a smaller point release fixing only some bugs without introducing new big features which should be reserved for a new bigger release. Fixes done in mc-4.6 branches can then be merged back into master so that master contains always every patch. I hope that this sound logically for you and I we can work this way :) Greetings Winnie -- . '' ` . Patrick Winnertz win...@debian.org : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~winnie - http://www.der-winnie.de `- Debian - when you have better things to do than fixing systems signature.asc Description: This is a digitally signed message part. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
[Midnight Commander] #143: Updated sh syntax file
#143: Updated sh syntax file --+- Reporter: Patrick Winnertz win...@debian.org | Owner: Type: defect| Status: new Priority: major | Milestone: Component: mc-core | Version: 4.6.1 Keywords:|Blocking: Blockedby:| --+- This a patch to add some more keywords to the sh syntaxfile. this a patch which is in use inside debian for a long time already. Please review. Greetings Winnie -- Ticket URL: www.midnight-commander.org/ticket/143 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
[Midnight Commander] #141: [PATCH] Moving doc files (001)
#141: [PATCH] Moving doc files (001) --+ Reporter: enrico.weig...@zaphod.local, metux IT service weig...@metux.de | Owner: Type: defect| Status: new Priority: major | Milestone: Component: mc-core | Version: 4.6.1 Keywords:| Blocking: Blockedby:| --+ This patch moves documentation files from toplevel to doc/ and manpages from doc/ to doc/man -- Ticket URL: /ticket/141 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #142: Syntax highlighting for debian specific files
#142: Syntax highlighting for debian specific files ---+ Reporter: Patrick Winnertz win...@debian.org | Owner: winnie Type: enhancement | Status: accepted Priority: major | Milestone: 4.6.2 Component: mc-core | Version: 4.6.1 Resolution:|Keywords: Blocking:| Blockedby: ---+ Changes (by winnie): * status: new = accepted Old description: Hey, Currently there is no syntax highlighting for debian specific files at all.. This patch (which is in use inside debian for a long term) will fix this. Please review. Greetings Winnie New description: Hey, Currently there is no syntax highlighting for debian specific files at all.. This patch (which is in use inside debian for a long term) will fix this. Please review. Greetings Winnie -- -- Ticket URL: www.midnight-commander.org/ticket/142#comment:3 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: RFC: updated workflow [WAS: Re: git+patch workflow]
* Oswald Buddenhagen o...@kde.org schrieb: Hi, delete *the* stable branch, but not the concept of stable branches per se. doing so would mean that once you merged a feature patch to master, you cannot do a bugfix release any more until you make a feature release (*). to keep the option of bugfix releases open Actually, I dislike that idea. Instead we should declare, that 'master' branch is *always* what becomes the next release. We just have to take care that it's always in a state that it could be released ASAP - so: *no* development there. New features only get committed if they're really ready to get into next release (which in theory could come any second). Of course we should do stable tree releases quite frequently, *NOT* collecting too much which might introduce new bugs. We've already waited too long w/ 4.6.2. (and distributors really want that), Well, if distros want a bugfixed branch of older releases and don't want to take care all by themselves, they could simply join the OSS-QM project, which is meant as an bug-fixing overlay over existing *releases* (it's about QM exclusively, *NO* development). But according the lack of interest in all these years, the presure obviously can't be that hight ;-o cu -- - Enrico Weigelt== metux IT service - http://www.metux.de/ - Please visit the OpenSource QM Taskforce: http://wiki.metux.de/public/OpenSource_QM_Taskforce Patches / Fixes for a lot dozens of packages in dozens of versions: http://patches.metux.de/ - ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #139: compatibility_move_mc_files() still needed ?
#139: compatibility_move_mc_files() still needed ? --+- Reporter: metux| Owner: slavazanko Type: task | Status: accepted Priority: minor| Milestone: 4.6.2 Component: mc-core | Version: 4.6.1 Resolution: |Keywords: Blocking: | Blockedby: --+- Comment(by metux): +1 for commit -- Ticket URL: www.midnight-commander.org/ticket/139#comment:6 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #125: allocate and free memory via mc-wrappers
#125: allocate and free memory via mc-wrappers --+- Reporter: slavazanko | Owner: Type: enhancement | Status: new Priority: major| Milestone: 4.6.2 Component: mc-core | Version: 4.6.1 Resolution: |Keywords: memory Blocking: | Blockedby: --+- Comment(by Enrico Weigelt): * Ticket System tick...@midnight-commander.org schrieb: ACK. But I'd like to go some steps further: * introduce new macros MC_MEM_ALLOC_Z()- alloc on heap, zero'ing MC_MEM_ALLOC_U()- alloc on heap, uninitialized MC_MEM_FREE() - free from stack MC_MEM_REALLOC()- re-allocate (added space uninitialized) MC_STACK_ALLOC()- allocate on stack * replace all other calls to malloc()+friends, mc_alloc()+co, by calling these macros Could also be put into src/util.h (BTW: we dont need any .c file for that) ACK. What should this mcglib actually contain ? cu -- Ticket URL: www.midnight-commander.org/ticket/125#comment: Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
[Midnight Commander] #140: [PATCH] moving doc files
#140: [PATCH] moving doc files --+ Reporter: enrico.weig...@zaphod.local, metux IT service weig...@metux.de | Owner: Type: defect| Status: new Priority: major | Milestone: Component: mc-core | Version: 4.6.1 Keywords:| Blocking: Blockedby:| --+ This patch moves the manpages under their own subdirectory doc/man/ and several doc files from toplevel to doc/ -- Ticket URL: /ticket/140 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #2: savannah: UTF-8 locales not supported
#2: savannah: UTF-8 locales not supported -+-- Reporter: slavazanko | Owner: slavazanko Type: defect | Status: accepted Priority: major | Milestone: UTF8 Support Component: mc-core | Version: Resolution: |Keywords: Blocking: | Blockedby: -+-- Changes (by slavazanko): * owner: = slavazanko * status: new = accepted * milestone: Recode Support = UTF8 Support Comment: I propose this patches: http://www.fi.muni.cz/~xbenes5/projects/mc/mc- utf8.tar.gz Link from: http://mail.gnome.org/archives/mc- devel/2007-December/msg1.html IMHO, this more right patches than patches from Fedora, Suse etc (no stupid #ifdef..#else...#endif in many source files). BTW, my global idea: in future gather #ifdef...#endif in one place (mclib?); other source files must be cleaned from # ifdef ... # endif as is possible. Also, present branch 'utf-8' with this patches. -- Ticket URL: www.midnight-commander.org/ticket/2#comment:2 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #65: savannah: Pascal syntax highlighting update
#65: savannah: Pascal syntax highlighting update --+- Reporter: slavazanko | Owner: winnie Type: enhancement | Status: accepted Priority: minor| Milestone: 4.6.2 Component: mc-core | Version: Resolution: |Keywords: Blocking: | Blockedby: --+- Comment(by Patrick Winnertz): Hey, finalization is a keyword from delphi to be honest. So yes.. this is a addition which was done more or less by Borland.. overloading also... I think we also should add keywords from delphi and freepascal to this file.. Is this okay? Greetings Winnie -- Ticket URL: www.midnight-commander.org/ticket/65#comment: Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: mcedit - fancy tab handling
Enrico Weigelt said: (by the date of Mon, 5 Jan 2009 19:22:25 +0100) Hi folks, I've just seen that current mcedit (from git tree) has some fancy tab handling (shows -- symbols). When had this been introduced ? I noticed this after upgrading debian etch to lenny. I like it, but sometimes it's inconvenient when I want to copy/paste with mouse. (using shift-mouseclicks) The best if there's a way to turn it on/off. And if it's somewhere easily accessible with menu/shortcuts. -- Janek Kozicki | ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #140: [PATCH] moving doc files
#140: [PATCH] moving doc files ---+ Reporter: enrico.weig...@zaphod.local, metux IT service weig...@metux.de | Owner: Type: defect | Status: new Priority: major | Milestone: Component: mc-core | Version: 4.6.1 Resolution: |Keywords: Blocking: | Blockedby: ---+ Old description: This patch moves the manpages under their own subdirectory doc/man/ and several doc files from toplevel to doc/ New description: This patch moves the manpages under their own subdirectory doc/man/ and several doc files from toplevel to doc/ -- Comment(by slavazanko): hm... I think, need to enlarge quota of patch sizes... Is gzipped patch less than 262144 bytes? -- Ticket URL: www.midnight-commander.org/ticket/140#comment:2 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #137: [PATCH] (git) Fixup homepage url
#137: [PATCH] (git) Fixup homepage url ---+ Reporter: enrico.weig...@zaphod.local, metux IT service weig...@metux.de | Owner: metux Type: task | Status: assigned Priority: critical | Milestone: 4.6.2 Component: mc-core | Version: Resolution: |Keywords: Blocking: | Blockedby: ---+ Comment(by Enrico Weigelt): :) I'm not sure if that's the right way - shouldnt the ticket be assigned to someone with commit authority ? cu -- Ticket URL: www.midnight-commander.org/ticket/137#comment: Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
[Midnight Commander] #142: Syntax highlighting for debian specific files
#142: Syntax highlighting for debian specific files --+- Reporter: Patrick Winnertz win...@debian.org | Owner: Type: defect| Status: new Priority: major | Milestone: Component: mc-core | Version: 4.6.1 Keywords:|Blocking: Blockedby:| --+- Hey, Currently there is no syntax highlighting for debian specific files at all.. This patch (which is in use inside debian for a long term) will fix this. Please review. Greetings Winnie -- Ticket URL: www.midnight-commander.org/ticket/142 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #11: savannah: Cannot change into directory a:foobar
#11: savannah: Cannot change into directory a:foobar -+-- Reporter: slavazanko | Owner: Type: defect | Status: new Priority: major | Milestone: VFS Standardisation Component: mc-core | Version: Resolution: |Keywords: Blocking: | Blockedby: -+-- Changes (by winnie): * milestone: = VFS Standardisation -- Ticket URL: www.midnight-commander.org/ticket/11#comment:2 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #143: Updated sh syntax file
#143: Updated sh syntax file ---+ Reporter: Patrick Winnertz win...@debian.org | Owner: winnie Type: enhancement | Status: new Priority: major | Milestone: 4.6.2 Component: mc-core | Version: 4.6.1 Resolution:|Keywords: Blocking:| Blockedby: ---+ -- Ticket URL: www.midnight-commander.org/ticket/143 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: mcedit - fancy tab handling
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Janek Kozicki wrote: Enrico Weigelt said: (by the date of Mon, 5 Jan 2009 19:22:25 +0100) Hi folks, I've just seen that current mcedit (from git tree) has some fancy tab handling (shows -- symbols). When had this been introduced ? I noticed this after upgrading debian etch to lenny. I like it, but sometimes it's inconvenient when I want to copy/paste with mouse. (using shift-mouseclicks) The best if there's a way to turn it on/off. And if it's somewhere easily accessible with menu/shortcuts. mc-ru-fork have this feature. And toggle space/tabs view via CTRL+v hotkey in editor... I will make valid patch from mc-ru-fork for 'master' at near time. WBR, Slavaz. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklicpsACgkQb3oGR6aVLprpGACfXjpxS3FTwJ9Fl1e293TPllZo G2kAnjSwU7KODO1ZF+o6bU8nCu6OmtpQ =WpmA -END PGP SIGNATURE- ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #143: Updated sh syntax file
#143: Updated sh syntax file ---+ Reporter: Patrick Winnertz win...@debian.org | Owner: winnie Type: enhancement | Status: accepted Priority: major | Milestone: 4.6.2 Component: mc-core | Version: 4.6.1 Resolution:|Keywords: Blocking:| Blockedby: ---+ -- Ticket URL: www.midnight-commander.org/ticket/143 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #143: Updated sh syntax file
#143: Updated sh syntax file ---+ Reporter: Patrick Winnertz win...@debian.org | Owner: winnie Type: enhancement | Status: accepted Priority: major | Milestone: 4.6.2 Component: mc-core | Version: 4.6.1 Resolution:|Keywords: Blocking:| Blockedby: ---+ Changes (by winnie): * owner: = winnie * status: new = accepted * type: defect = enhancement * milestone: = 4.6.2 Old description: This a patch to add some more keywords to the sh syntaxfile. this a patch which is in use inside debian for a long time already. Please review. Greetings Winnie New description: This a patch to add some more keywords to the sh syntaxfile. this a patch which is in use inside debian for a long time already. Please review. Greetings Winnie -- -- Ticket URL: www.midnight-commander.org/ticket/143#comment:2 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #131: ***TRASH***
#131: ***TRASH*** +--- Reporter: metux | Owner: metux Type: defect | Status: closed Priority: minor | Milestone: Component: mc-core| Version: 4.6.1 Resolution: duplicate |Keywords: Blocking: | Blockedby: +--- Changes (by winnie): * status: testing = closed -- Ticket URL: www.midnight-commander.org/ticket/131#comment:5 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [Midnight Commander] #139: compatibility_move_mc_files() still needed ?
#139: compatibility_move_mc_files() still needed ? --+- Reporter: metux| Owner: slavazanko Type: task | Status: accepted Priority: minor| Milestone: 4.6.2 Component: mc-core | Version: 4.6.1 Resolution: |Keywords: Blocking: | Blockedby: --+- Comment(by slavazanko): or simply see changeset:5deebd49a8b60b9c7c21cdebe9cb252f788037d0 I see, it's better than attach patch... -- Ticket URL: www.midnight-commander.org/ticket/139#comment:5 Midnight Commander www.midnight-commander.org Midnight Development Center ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [r...@rover.dkm.cz: [repo.or.cz] midnight-commander clone completed]
On Sun, 2009-01-04 at 17:01 +0100, Enrico Weigelt wrote: * Pavel Roskin pro...@gnu.org schrieb: Hi, I really don't see the problem. The problem is that the mirror already existed on that site. Now we have two mirrors. It's confusing to the users. Some may be tracking my mirror now. Instead of giving you control over the existing mirror, I'll need to ask the site administration to remove my mirror. The users will have to switch to your repository. Why do you have to close your mirror ? I dont see any reason. Thousands of OSS projects get mirrored all around the world, even without explicit knowledge of the devs, and - as far as I know - nobody feels pissed about that. What's the problem ? I don't want to be responsible for an obsolete repository. I believe it's important that the project developers act as a team and coordinate their actions. What is there to coordinate on just some dumb unofficial mirror ? Its name and who is responsible for mirroring. I realize I'm not a team member anymore, but I've been maintaining the mirror for along time. Wait, you really feel kicked-away, just because your mirror isn't the only one anyomore ? Quite strange, IMHO. There is no need for two mirrors on one site. The only problem with the existing mirror was that you didn't control it. Otherwise, it was perfectly usable. I spent quite a lot of time mapping CVS authors to the real names, and that mapping is used in your repository. Right, and you did a great job. You volunteered to do an dirty, but important job, nobody else was willing to do. And I don't think anyone here won't appreciate that. So you *are* a valueable member of the team, and I don't see how some additional, uninteresting git mirror can change that fact. Thanks. I'm unsubscribing from the lists now and I'm not going to continue this discussion. -- Regards, Pavel Roskin ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
