Re: [e-users] using cvs with E

2008-03-28 Thread Robin
> 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

Re: [e-users] using cvs with E

2008-03-28 Thread Massimiliano Calamelli
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

Re: [e-users] using cvs with E

2008-03-28 Thread Massimo Maiurana
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

Re: [e-users] using cvs with E

2008-03-28 Thread Robin
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,

Re: [e-users] using cvs with E

2008-03-28 Thread 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

Re: [e-users] using cvs with E

2008-03-28 Thread Ravenlock
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)