Indenting...

[Randy Terbush <ra...@zyzzyva.com>]

Seems like enough time has passed to raise this fun topic again. 
Since I am looking for things to procrastinate with, I would like 
to suggest applying indentation changes. I've verified that the 
current .indent.pro does what we had agreed upon. Submitting a 
patch is out of the question since it is a wholesale change. I'll 
get in there and start commiting these changes if we agree.

We probably should have done this after branching. With talk of 
tree reorganization, perhaps we should do it at that time. I could 
coordinate with Paul if that is the direction we go. It kind of 
concerns me to start yet another repository. Seems we have our 
hands full with the current situation.

-Randy

Re: Indenting...

[Marc Slemko <ma...@worldgate.com>]

I think the time for reindenting and reorg will come at the same time, and
I'm not sure it is necessary in the 1.3 tree.

On Sun, 29 Jun 1997, Dean Gaudet wrote:

> I'm ok with another repository, I'm doing *most* of my branch stuff using
> the email log of everything.  patch is such a wonderful thing, it groks
> patches which are indented by two spaces.  It tells you "patch was
> indented two spaces", how kind of it!  The only thing I'm using
> traditional CVS branch tricks for are the docs.  Where I do: 
> 
> cvs update -j dg_last_1_2_doc_merge -j 1
> 
> and then retag the head after the merge. 
> 
> But I can just as easily keep all the doc changes in my apache-cvs mailbox
> like I do with source changes and then merge them into a different tree. 
> 
> Doing a re-indent will make 1.2.x merging a lot harder ... I'm only +0 on
> doing a re-indent.  I can read Ben's code if I squint hard enough ;)
> 
> Dean
> 
> On Sun, 29 Jun 1997, Randy Terbush wrote:
> 
> > Seems like enough time has passed to raise this fun topic again. 
> > Since I am looking for things to procrastinate with, I would like 
> > to suggest applying indentation changes. I've verified that the 
> > current .indent.pro does what we had agreed upon. Submitting a 
> > patch is out of the question since it is a wholesale change. I'll 
> > get in there and start commiting these changes if we agree.
> > 
> > We probably should have done this after branching. With talk of 
> > tree reorganization, perhaps we should do it at that time. I could 
> > coordinate with Paul if that is the direction we go. It kind of 
> > concerns me to start yet another repository. Seems we have our 
> > hands full with the current situation.
> > 
> > -Randy
> > 
> > 
> > 
> > 
> > 
> 

Re: Indenting...

[Dean Gaudet <dg...@arctic.org>]

I'm ok with another repository, I'm doing *most* of my branch stuff using
the email log of everything.  patch is such a wonderful thing, it groks
patches which are indented by two spaces.  It tells you "patch was
indented two spaces", how kind of it!  The only thing I'm using
traditional CVS branch tricks for are the docs.  Where I do: 

cvs update -j dg_last_1_2_doc_merge -j 1

and then retag the head after the merge. 

But I can just as easily keep all the doc changes in my apache-cvs mailbox
like I do with source changes and then merge them into a different tree. 

Doing a re-indent will make 1.2.x merging a lot harder ... I'm only +0 on
doing a re-indent.  I can read Ben's code if I squint hard enough ;)

Dean

On Sun, 29 Jun 1997, Randy Terbush wrote:

> Seems like enough time has passed to raise this fun topic again. 
> Since I am looking for things to procrastinate with, I would like 
> to suggest applying indentation changes. I've verified that the 
> current .indent.pro does what we had agreed upon. Submitting a 
> patch is out of the question since it is a wholesale change. I'll 
> get in there and start commiting these changes if we agree.
> 
> We probably should have done this after branching. With talk of 
> tree reorganization, perhaps we should do it at that time. I could 
> coordinate with Paul if that is the direction we go. It kind of 
> concerns me to start yet another repository. Seems we have our 
> hands full with the current situation.
> 
> -Randy
> 
> 
> 
> 
>