Re: [Evolution-hackers] Evolution Maintainership

2007-03-30 Thread Jeffrey Stedfast
On Thu, 2007-03-29 at 21:24 -0600, Hans Petter Jansson wrote:
 On Thu, 2007-03-29 at 15:15 +0530, Harish Krishnaswamy wrote:
 
  This mail is to announce that Srinivasa Ragavan (srag) is joining me
  to assume the responsibilites as maintainer of the Evolution project.
  
  [...]
 
 Congratulations, Srini! And a big thank you to Harish and the Evolution
 team for your hard work and dedication to the project. The truth is,
 with more than 7 years of development behind it, it's one of the best
 mailers around.
 

+1

You've done a fantastic job with Evolution :)

Jeff


___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list


name change for gnome-volume-manager?

2006-08-06 Thread Jeffrey Stedfast
I'd like to change the name of gnome-volume-manager to
gnome-device-manager.

discuss.

-- 
Jeffrey Stedfast
Evolution Hacker - Novell, Inc.
[EMAIL PROTECTED]  - www.novell.com

___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list


Re: [Evolution-hackers] Memory consumption and virtual machines

2006-07-19 Thread Jeffrey Stedfast
I have to wonder if it's even worth ever merging the mmap hack into
Evolution at all. If the plan is to finish Zucchi's disk-summary branch,
which also solves the memory problems (afaik) as well as:

1. introducing an API for using cursors to get at message infos
2. better designed on-disk format that uses B-Trees


the problem with philip's mmap file format is that the strings that will
be hit for sorting/viewing/etc are all spread out over a huge number of
pages. I just see this being re-examined later to try and design the
format to better optimise it by compacting all the strings into a strtab
type thing.

I also don't like how it has to reload the summary anytime new messages
arrive.

I just don't get the feeling this is really all that well thought out
and it scares me.

I'd just hate to see a rush job come out of this

Jeff


On Tue, 2006-07-18 at 13:26 -0500, Federico Mena Quintero wrote:
 On Tue, 2006-07-18 at 18:29 +0200, Philip Van Hoof wrote:
 
  I'm waiting for the decision (yours) of making this optional using a
  compilation flag or at run-time.
 
 Let's do this in the usual manner:
 
 0. Polish the patch in the usual way:  make sure it follows the
 indentation and naming conventions of the surrounding code, etc.
 
 1. Branch evolution-data-server into HEAD (development, with Philip's
 patch), and the stable branch (without the patch).
 
 2. Make the patch *mandatory* in HEAD, so that it gets a good amount of
 testing.
 
 3. ???
 
 4. Profit!!!
 
 I'd suggest that (3) become write a good stress-test suite for Camel,
 independent of Evolution.  We need that anyway.
 
 Novell already has a bunch of LDTP stuff to test the Evo mailer from the
 user's viewpooint - run those tests on the patched version to see how
 well they work.  [Varadhan, those tests are already part of our QA
 process, aren't they?]
 
   Federico
 
 ___
 Evolution-hackers mailing list
 Evolution-hackers@gnome.org
 http://mail.gnome.org/mailman/listinfo/evolution-hackers
-- 
Jeffrey Stedfast
Evolution Hacker - Novell, Inc.
[EMAIL PROTECTED]  - www.novell.com

___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list


Re: String freeze break in gnome-volume-manager

2006-02-27 Thread Jeffrey Stedfast
Would another accepted solution be to fix all the msgid strings in the
po files to reflect the change made?

e.g.

s/_Ignore/Ig_nore/ ?

Jeff

On Mon, 2006-02-27 at 17:13 +0100, Danilo Ĺ egan wrote:
 Hi Jeffrey,
 
 Your commit on February 24th to gnome-volume-manager broke the string
 freeze: 
 
 http://cvs.gnome.org/viewcvs/gnome-volume-manager/src/manager.c?r1=1.130r2=1.131
 
 
 Please revert this change and instead consider:
 
  - branching for Gnome 2.14 before introducing this change
  - asking for string freeze break approval (highly unlikely to get
one from me, if the sole reason is the one in bug #326955[1]),
following the procedure outlined on:
  http://live.gnome.org/ReleasePlanning/Freezes
  - putting a patch in Bugzilla and marking it as
accepted_commit-after-freeze and committing it when you branch
  
 
 Cheers,
 Danilo
 
 
 [1] http://bugzilla.gnome.org/show_bug.cgi?id=326955
 
-- 
Jeffrey Stedfast
Evolution Hacker - Novell, Inc.
[EMAIL PROTECTED]  - www.novell.com

___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list