Re: My CT branch experience

2006-10-08 Thread Andre Poenitz
On Fri, Oct 06, 2006 at 08:11:29PM +0200, Michael Gerz wrote: > Andre Poenitz wrote: > > >*shrug* > > > >I still wouldn't mind a single big chunk. > > > > > But I don't have a single chunk. Some parts of my former work got lost, > because Abdel moved code from one file to another. Other CT code

Re: My CT branch experience

2006-10-06 Thread Abdelrazak Younes
Michael Gerz wrote: Andre Poenitz wrote: *shrug* I still wouldn't mind a single big chunk. But I don't have a single chunk. Some parts of my former work got lost, because Abdel moved code from one file to another. Man, I have warned you multiple times ;-) More seriously I had the impress

Re: My CT branch experience

2006-10-06 Thread Michael Gerz
Andre Poenitz wrote: *shrug* I still wouldn't mind a single big chunk. But I don't have a single chunk. Some parts of my former work got lost, because Abdel moved code from one file to another. Other CT code hasn't even been fixed in my branch (due to a lack of time at that time). All I

Re: My CT branch experience

2006-10-06 Thread Andre Poenitz
On Thu, Oct 05, 2006 at 08:09:30PM +0200, Michael Gerz wrote: > Hello everybody, > > I finally synchronized my branch with the trunk. The result is something > that certainly will not work and cannot be committed in one chunk. > > Now how can I proceed? > > Actually, I will go through the same

Re: My CT branch experience

2006-10-06 Thread Michael Gerz
Michael Gerz wrote: To give you an impression of what I am going to do, here comes a first patch. It changes two variables in conformance to the LyX coding rules and - on that occasion - fixes a couple of places and adds FIXME markers to a couple of other places. If I am not allowed to do such

Re: My CT branch experience

2006-10-06 Thread Michael Gerz
Jean-Marc Lasgouttes wrote: Michael> When I started to relabel a few variables, I noticed that Michael> many of their uses will be removed in the long run. If I am Michael> able to remove their use instantly (breaking CT sooner than Michael> later), this will make thing much easier for me. Why

Re: My CT branch experience

2006-10-06 Thread Jean-Marc Lasgouttes
> "Michael" == Michael Gerz <[EMAIL PROTECTED]> writes: Michael> So I am free to break things as long as only CT is affected? Michael> Fine! This is not exactly what I had in mind... And I do not have much say about what should happen in 1.5 (meaning: I am not the one to give a "go ahead and

Re: My CT branch experience

2006-10-06 Thread Michael Gerz
Jean-Marc Lasgouttes wrote: Michael> Actually, I will go through the same process that I went Michael> through a few month ago: I will pick those parts of the Michael> complete patch first that are purely cosmetic, do not change Michael> semantics, or which somehow describe a logical piece of co

Re: My CT branch experience

2006-10-06 Thread Jean-Marc Lasgouttes
> "Michael" == Michael Gerz <[EMAIL PROTECTED]> writes: Michael> Actually, I will go through the same process that I went Michael> through a few month ago: I will pick those parts of the Michael> complete patch first that are purely cosmetic, do not change Michael> semantics, or which somehow

My CT branch experience

2006-10-05 Thread Michael Gerz
Hello everybody, I finally synchronized my branch with the trunk. The result is something that certainly will not work and cannot be committed in one chunk. Now how can I proceed? Actually, I will go through the same process that I went through a few month ago: I will pick those parts of the