Hello,
In the Message;
Subject: Re: [e-users] bug in e16-0.16.8.13-0.01?
Message-ID : <[EMAIL PROTECTED]>
Date & Time: Thu, 27 Mar 2008 00:32:46 +0100
[Kim] == Kim Woelders <[EMAIL PROTECTED]> has written:
Me>> Today, the problem occurred again. I searched the error message/backtrace
Гусев Фёдор,
On Mar 28 03:01, Гусев Фёдор wrote:
> Attached patch fixes that.
Correct me if I'm mistaken but I don't see an attached patch.
Sincerely,
--
Antony Jepson / <[EMAIL PROTECTED]> / GPG Key: 0xFA10ED80
-
Check o
> 2008/3/28, Robin <[EMAIL PROTECTED]>:
>
> > On 28/03/2008, Wido <[EMAIL PROTECTED]> wrote:
> > >
> > > but you never got the "some file is int the way" conflict? i got a
> > > lot of those and some times, when compile somethigns, it just
> > > dones't works
> > >
> > > On Fri, Mar 28, 200
easy_e17 -u -f works fine for me.
massimiliano
2008/3/28, Robin <[EMAIL PROTECTED]>:
> On 28/03/2008, Wido <[EMAIL PROTECTED]> wrote:
> >
> > but you never got the "some file is int the way" conflict? i got a
> > lot of those and some times, when compile somethigns, it just
> > dones't w
Wido, il 28/03/2008 17:15, scrisse:
> but you never got the "some file is int the way" conflict? i got a
> lot of those and some times, when compile somethigns, it just
> dones't works
I've never had any problem.
I have to say I have a cvs account, but I've never heard about
problems usin
On 28/03/2008, Wido <[EMAIL PROTECTED]> wrote:
>
> but you never got the "some file is int the way" conflict? i got a
> lot of those and some times, when compile somethigns, it just
> dones't works
>
> On Fri, Mar 28, 2008 at 9:26 AM, Massimo Maiurana <[EMAIL PROTECTED]>
> wrote:
> > Wido,
but you never got the "some file is int the way" conflict? i got a
lot of those and some times, when compile somethigns, it just
dones't works
On Fri, Mar 28, 2008 at 9:26 AM, Massimo Maiurana <[EMAIL PROTECTED]> wrote:
> Wido, il 28/03/2008 06:43, scrisse:
>
> > Hi all there, folks. This
On 03/28/2008 00:43, Wido wrote:
> Hi all there, folks. This is probably one of the silliest question
> here but..what is the best way to keep cvs up to date? i've tried
> the common "cvsup", then diferent options, like "cvs up -dPAR", but
> always have conflicts with *.po (which i dont bother)
