* Miguel de Icaza mig...@novell.com schrieb:
The Midnight Commander development community is small and it is in
my opinion a step backwards to fragment it at this point.
Funny that you mention this, as it was *YOU* who forced another fork ;-o
cu
--
* Miguel de Icaza mig...@novell.com schrieb:
I agree with Pavel here. mc-dev has been for the most part dormant,
and some terrible decisions (like that whole mhl fiasco) could have
been avoided.
I wouldn't call it fascio, rather a good lection that even the
OSS world isn't free of
* Miguel de Icaza mig...@novell.com schrieb:
Hi,
Your approach to development is my way or the high way. The
consensus is that glib should stay, and even your concern about
using glib was addressed by pointing you to eglib and I even
ported mc and posted a patch to use eglib.
First of
* Enrico Weigelt weig...@metux.de schrieb:
oh, forgot the link ;-o
*1) git://git.metux.de/free-mc.git
cu
--
-
Enrico Weigelt== metux IT service - http://www.metux.de/
Hello,
It was *YOU* destroyed that by climbing out of your deep dark tomb
and behaving like the old king coming back which everyone has to
submit to. It was you caused a lot of wasting resources (not just
computer's but also human's) for your personal crusade against
a lot of things we've done
Hello,
You went light on the details, other than saying 'you totally'
repeatedly.
* you totally ignored recommendation for defering this decision
until eglib becomes production-ready
It is very simple. The majority of people to not have a problem
with glib, and the size is not an issue.
*1) git://git.metux.de/free-mc.git
Thanks for the link. I guess we can go and pick any
good changes from there and merge them into mc now.
Miguel.
___
Mc-devel mailing list
http://mail.gnome.org/mailman/listinfo/mc-devel
On Fri, Feb 13, 2009 at 7:20 PM, Pavel Tsekov ptse...@gmx.net wrote:
You might not be aware but I am (still) one of the two official MC
maintainers.
De jure, maybe you are. De facto, the project is an orphan.
How many more times do I need to submit my patches
to get your attention?
How many
Hello Denys,
Monday, February 16, 2009, 3:15:45 PM, you wrote:
On Fri, Feb 13, 2009 at 7:20 PM, Pavel Tsekov ptse...@gmx.net wrote:
You might not be aware but I am (still) one of the two official MC
maintainers.
De jure, maybe you are. De facto, the project is an orphan.
How many more
On Mon, Feb 16, 2009 at 3:02 PM, Pavel Tsekov ptse...@gmx.net wrote:
Hello Denys,
Monday, February 16, 2009, 3:15:45 PM, you wrote:
On Fri, Feb 13, 2009 at 7:20 PM, Pavel Tsekov ptse...@gmx.net wrote:
You might not be aware but I am (still) one of the two official MC
maintainers.
De jure,
Hi Denys,
Would you please cool down a little bit? Don't you think we can resolve
this peacefully w/o further mutual accusations, don't we? I think that
both parties will benefit from this... It's crystal clear that current
development model desperately needs a change. But Pavel has some valid
Hello,
It is very common in every project I participate to use different
mailing list for these different goals: users, developer discussion,
bug tracking and commits. It makes it easier to filter, and it
allows for people that care about one particular area to focus on that
area.
Hello,
I am not really unavailable. In fact if someone bothered to ping me
personally I would have noticed immediately. The list traffic was
stalled for quite some time and I haven't been reading it on a regular
basis for a while so I missed the interesting part.
I agree with Pavel here.
On Monday 16 February 2009 20:17, Pavel Tsekov wrote:
So you want to bitch... I really cannot help you with that.
How much did I bitch in these years while the patch
was lying around? URL please.
In case you did not notice, I want to code.
I want to help MC to improve and sligtly more
than
On Fri, Feb 13, 2009 at 08:20:29PM +0200, Pavel Tsekov wrote:
You don't become a project member and developer by just waiting for
the right moment, appearing on the scene and taking over of
everything.
would you bet?
you may be the best maintainer on earth (you aren't, but wth), but by
being
Hey,
to the new ones: get the trac vs. the mailinglist thing sorted.
the current situation practically excludes everyone who cannot be
bothered to poll your trac often enough, which basically is everyone who
has some real experience (and thus has a day job, etc.).
The plan is to move the trac
On Sat, Feb 14, 2009 at 04:38:31PM +0100, Patrick Winnertz wrote:
to the new ones: get the trac vs. the mailinglist thing sorted.
The plan is to move the trac mails together with git commit messages
to an own mailinglist.
but you want to continue using mc-devel as well? i don't think the
Am Samstag 14 Februar 2009 17:21:22 schrieb Oswald Buddenhagen:
On Sat, Feb 14, 2009 at 04:38:31PM +0100, Patrick Winnertz wrote:
to the new ones: get the trac vs. the mailinglist thing sorted.
The plan is to move the trac mails together with git commit messages
to an own mailinglist.
On Sat, Feb 14, 2009 at 05:43:55PM +0100, Patrick Winnertz wrote:
Well.. I would like to have some place to discuss everything.
of course.
If this is too much it would be worth to move this to a separate
mailinglist.
yes - *if*. but that's not going to be the case. i cannot imagine that
Hello Oswald,
Saturday, February 14, 2009, 4:47:44 PM, you wrote:
On Fri, Feb 13, 2009 at 08:20:29PM +0200, Pavel Tsekov wrote:
You don't become a project member and developer by just waiting for
the right moment, appearing on the scene and taking over of
everything.
would you bet?
Yes,
Hello Slava,
You might not be aware but I am (still) one of the two official MC
maintainers.
Thursday, December 18, 2008, 2:23:07 AM, you wrote:
Hello, dear developers! It is no secret that the recent console manager
Midnight Commander stopped in its development. We do not know the
reasons
Hello,
I agree with the sentiments expressed by Pavel Tsekov. If you guys
have collected a new set of patches to Midnight Commander, let us get
those patches posted to the tracking software in midnight-commander.org
and discuss those changes as a community.
Pavel is right that many
* Slava Zanko slavaza...@gmail.com schrieb:
Hi,
you meant: mcvfs = model ?
No. model = any data source. mcvfs - one of sources for mc.
Which other datasources do you have in mind ?
yeah, even sockets:
cat tcp://somehost:port/
(I'll add this to libmvfs in the next days ...)
Cool.
* Slava Zanko slavaza...@gmail.com schrieb:
Hi,
Is it a good idea to make git-branch Stable based on 4.6.1 and
git-branch Current based of the current cvs-code (4.6.2-pre1)?
I'd really suggest forking the stable tree on 4.6.1 release and
let it be the rc for 4.6.2, then step by step merge
Am Montag 29 Dezember 2008 18:33:44 schrieb Miguel de Icaza:
Hellom
IMHO we should start with the latest stable release (4.6.1 ?) and apply
all the vendor/distro patches floating around step by step (*1). Once
that's done, we should make a new official release very soon.
I agree with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Enrico Weigelt wrote:
* Slava Zanko slavaza...@gmail.com schrieb:
Hi,
huh, I'm not sure whether mvc fits in here.
mcvfs - VIEW; core (signal handling, User events etc) - CONTROLLER,
slang,mcslang,ncurses - VIEWs.. Why not? :)
you meant: mcvfs
Hellom
IMHO we should start with the latest stable release (4.6.1 ?) and apply
all the vendor/distro patches floating around step by step (*1). Once
that's done, we should make a new official release very soon.
I agree with this approach, we should start by reviewing those patches
as well,
On Mon, Dec 29, 2008 at 12:33:44PM -0500, Miguel de Icaza wrote:
Hellom
IMHO we should start with the latest stable release (4.6.1 ?) and apply
all the vendor/distro patches floating around step by step (*1). Once
that's done, we should make a new official release very soon.
I agree
* Roland Illig roland.il...@gmx.de schrieb:
Hi,
I'd like to. If there is some more action in mc development (like in
2005, when it was great fun), I'm definitely willing to invest some time
into it.
:)
Maybe we even get all the different UTF-8 patches incorporated into mc.
If that's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Enrico Weigelt wrote:
huh, I'm not sure whether mvc fits in here.
mcvfs - VIEW; core (signal handling, User events etc) - CONTROLLER,
slang,mcslang,ncurses - VIEWs.. Why not? :)
Well, if we say everything's a file and the model is the vfs
* Slava Zanko slavaza...@gmail.com schrieb:
Hi,
huh, I'm not sure whether mvc fits in here.
mcvfs - VIEW; core (signal handling, User events etc) - CONTROLLER,
slang,mcslang,ncurses - VIEWs.. Why not? :)
you meant: mcvfs = model ?
Well, if we say everything's a file and the model is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Enrico Weigelt wrote:
I propose to establish two branches: stable and current (in git, of
course).
Stable branch will contain all founded patches (Fedora, Debian/Ubuntu,
Gentoo,...), new ideas and features.
The stable branch will provide the
* Slava Zanko slavaza...@gmail.com schrieb:
Hi,
Absolutly yes. Maintainers of distros should not include any patches of
security in packages that are based on the stable branch. If any patch
of security or stability is included into package (not in repro) - our
work is a bad.
Glad you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Enrico Weigelt wrote:
I think the most important is to have official tree as global reference
and release point. Everyone else should work relative to the lastest
official release and submit his patches against it. These patches should
go to
Enrico Weigelt wrote:
Ops... sorry my mistake:
- - Stable branch will contain all founded patches (Fedora, Debian/Ubuntu,
- - Current branch will contain all founded patches (Fedora,
Debian/Ubuntu,
Gentoo,...), new ideas and features.
Fixed. :)
___
* Slava Zanko slavaza...@gmail.com schrieb:
Hi,
I propose to establish two branches: stable and current (in git, of
course).
Stable branch will contain all founded patches (Fedora, Debian/Ubuntu,
Gentoo,...), new ideas and features.
The stable branch will provide the solutions that were
Hi folks,
I think the most important is to have official tree as global reference
and release point. Everyone else should work relative to the lastest
official release and submit his patches against it. These patches should
go to this list, be discussed here and then, if considered good, be
Am Monday 22 December 2008 21:02:21 schrieben Sie:
Patrick Winnertz wrote:
If yes I'll set up a trac on my private server until I find a better
solution. If this repro is ready I'll ping you and we can start to
migrate you patches into the git repro. Is this okay for you (and the
rest of
2008/12/23 Patrick Winnertz win...@debian.org:
Am Monday 22 December 2008 21:02:21 schrieben Sie:
Patrick Winnertz wrote:
If yes I'll set up a trac on my private server until I find a better
solution. If this repro is ready I'll ping you and we can start to
migrate you patches into the git
Hey,
[removed some private stuff]
1) why not asking for git on savannah?
As trac needs a local git.
2) is it mc on savannah doomed?
Well.. the bugtracker there is ugly.. there is too much spam, cvs is very
ancient, git is so much better.
3) Why not officially close it?
My intention is to set
Am Friday 19 December 2008 05:28:56 schrieben Sie:
Hello, Miguel!
Quoting Miguel de Icaza mig...@ximian.com:
I would personally like to see mc move to git, there are nice hosting
services like github, it is easy to fork and it is easy to review
patches from third parties.
I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Patrick Winnertz wrote:
It's updated automatically. It can be just cloned for further
development. I took care to provide full names of all committers ever
committing anything to the mc repository.
Yes.. this would be great.
Would it be
Many patches(Fedora, debian) applied in one revision at start of
project, sorry. Many own patches is relative to previous patches.
Is it possible to migrate? Gm... Nothing is impossible :) But this will
require much effort and time.
Well,, this should be quite easy.
Have a look on the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Patrick Winnertz wrote:
Well,, this should be quite easy.
Have a look on the git-svn tool. You should be able to create a git checkout
from your svn stuff.. After this it's very easy to pick each commit and apply
it on the new git repro. This
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Patrick Winnertz wrote:
If yes I'll set up a trac on my private server until I find a better solution.
If this repro is ready I'll ping you and we can start to migrate you patches
into the git repro. Is this okay for you (and the rest of the
On Thu, Dec 18, 2008 at 08:26:17AM +0100, Patrick Winnertz wrote:
Am Thursday 18 December 2008 07:39:30 schrieben Sie:
Slava Zanko said: (by the date of Thu, 18 Dec 2008 02:23:07 +0200)
Alex Custov
Andrew Savchenko
Denis Frolov
Dmitry Korzhevin
Pavel Vasil'ev
Slava Zanko
Well,
As I see there are plenty of people who would like to work further on mc, it
would be very sad if these people will work on different versions, as this is
ineffective, and tend to end in even more dead projects.
My suggestion would be to have at first a look who wants to help to develop
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Patrick Winnertz wrote:
Well,
As I see there are plenty of people who would like to work further on mc, it
would be very sad if these people will work on different versions, as this is
ineffective, and tend to end in even more dead projects.
Patrick Winnertz schrieb:
So: At first the people who would like to work on mc should send a: I would
like to do something.
I'd like to. If there is some more action in mc development (like in
2005, when it was great fun), I'm definitely willing to invest some time
into it.
Maybe we even get
Hello,
My suggestion would be to have at first a look who wants to help to develop
mc
further and then where to do this.
Agreed, this initial post is light on the details as to what the changes
are, ChangeLog entries and the documentation.
The site is in Russian which does not help very
Hello, Miguel!
Quoting Miguel de Icaza mig...@ximian.com:
I would personally like to see mc move to git, there are nice hosting
services like github, it is easy to fork and it is easy to review
patches from third parties.
I'm maintaining a git mirror of the mc repository:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello, dear developers! It is no secret that the recent console manager
Midnight Commander stopped in its development. We do not know the
reasons why this is happening, but we badly want to see its further
development. In fact, the Midnight Commander
Slava Zanko said: (by the date of Thu, 18 Dec 2008 02:23:07 +0200)
Alex Custov
Andrew Savchenko
Denis Frolov
Dmitry Korzhevin
Pavel Vasil'ev
Slava Zanko
Isn't Patrick Winnertz part of your newly formed development team?
I guess that he wants to be! He just asked for write access to
Am Thursday 18 December 2008 07:39:30 schrieben Sie:
Slava Zanko said: (by the date of Thu, 18 Dec 2008 02:23:07 +0200)
Alex Custov
Andrew Savchenko
Denis Frolov
Dmitry Korzhevin
Pavel Vasil'ev
Slava Zanko
Isn't Patrick Winnertz part of your newly formed development team?
I
54 matches
Mail list logo
