On Tue, Jul 11, 2006 at 09:37:50PM +0200, Thomas Anders wrote:
> Guy Harris wrote:
> > when trying to open a file in the Wireshark configuration file
> > directory, if it's not found there, check in the Ethereal
> > configuration file directory and, if it's found there, copy it to
> > the
Guy Harris wrote:
> Is there any reason why
>
> when trying to open a file in the Wireshark configuration file
> directory, if it's not found there, check in the Ethereal configuration
> file directory and, if it's found there, copy it to the Wireshark
> configuration file directory
>
>
Anders Broman (AL/EAB) wrote:
> In my opinion it depends on how big the problem you are trying to solve
> realy is and how complicated it will be
> To design a well working solution, sometimes the cure is worse than the
> illnes.
Is there any reason why
when trying to open a file in the
Don't want to start a flaming or anything like that there ;)
> That's not a very user friendly point of view.
>
> "Why should I take care of the preference settings, I was
> able to copy
> things over so others can do this as well"
>From what I can watch in real life Wireshark/Ethereal usage,
other couple of weeks...
Best regards
Anders
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ulf Lamping
Sent: den 11 juli 2006 14:00
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Release early, release often? - What about
a new re
Jacques, Olivier (OpenCall Test Infra) wrote:
> I don't see that as a pre-requisite. IMHO we should keep things simple
> and have only a mention in the release notes that Ethereal preferences
> are not retrieved.
>
That's not a very user friendly point of view.
"Why should I take care of the p
> > > No one has had the time to get the ethereal/wireshark
> configuration
> > > reading stuff sorted out. Anyone have any idea how
> invasive that would be?
> > > Maybe a waiting point for 0.99.2 branch, which cannot be
> released without
> > > this anyway, IMHO.
I don't see that as a pre-req
Jaap Keuter wrote:
> Hi Ulf,
>
> Will that be a permanent solution? I mean, it will have to stay in the
> installer since we never know when an Ethereal user is upgrading to a
> version (0.99.2, 0.99.3, 1.0, 1.1 ) of Wireshark. What happens when
> the Ethereal stuff isn't removed but 0.99.3 is
Hi Ulf,
Will that be a permanent solution? I mean, it will have to stay in the
installer since we never know when an Ethereal user is upgrading to a
version (0.99.2, 0.99.3, 1.0, 1.1 ) of Wireshark. What happens when
the Ethereal stuff isn't removed but 0.99.3 is installed after 0.99.2?
Will i
Jaap Keuter wrote:
> Hi,
>
> No one has had the time to get the ethereal/wireshark configuration
> reading stuff sorted out. Anyone have any idea how invasive that would be?
> Maybe a waiting point for 0.99.2 branch, which cannot be released without
> this anyway, IMHO.
>
I've already committed
Hi,
No one has had the time to get the ethereal/wireshark configuration
reading stuff sorted out. Anyone have any idea how invasive that would be?
Maybe a waiting point for 0.99.2 branch, which cannot be released without
this anyway, IMHO.
Thanx,
Jaap
On Mon, 10 Jul 2006, Gerald Combs wrote:
>
Done:
http://wiki.wireshark.org/Development/IljasBugList
I've made a pass through the list and checked in changes, but it would
be nice if others could do so.
I'll create the 0.99.2 trunk later today, along with 0.99.2pre1.
ronnie sahlberg wrote:
> can you put iljas list on a wikiso one
can you put iljas list on a wikiso one can remove each item from
the list as they are addresses?
On 7/10/06, Ulf Lamping <[EMAIL PROTECTED]> wrote:
> Hi List!
>
> The current release situation is unsatisfying IMHO.
>
> The last official release is the Ethereal 0.99.0 version from April 24,
>
Hi List!
The current release situation is unsatisfying IMHO.
The last official release is the Ethereal 0.99.0 version from April 24,
2006 which is about 10 weeks ago and contains some frequently reported
(and quite annoying) bugs in the win32 export functions (and obviously
elsewhere).
The of
14 matches
Mail list logo
