Re: [Quilt-dev] status query for patch description feature

[martin . quinson]

Selon Andreas Gruenbacher <address@hidden>:

> Hello,
> 
> On Wednesday 30 June 2004 04:15, Joe Green wrote:
> > Yasushi SHOJI wrote:
> > > could you briefly explain how you implemented "quilt header", if
> > > possible? or send me the patch?
> >
> > Patch is attached.
> 
> thanks for the patch.
> 
> I strongly dislike keeping the header in a separate file. This can only cause
> trouble.
>
> The header templates and comments are a nice idea. One possible extension 
> would be to always add the comments when editing, and to remove them when 
> saving. This would require a structured header format that is less general, 
> though.
> 
> This is all pretty policy dependent. I've mentioned before that I'm not keen
> on dragging too much policy into quilt, so I'll definitely not blindly add 
> this command. This could easily discuss users who would otherwise find quilt
> pretty useful.

I'm not sure I got what you mean. 

I seem to understand that you first say that you don't like something which the
patch does not do (header in separate file), then that you like the features
offered by the patch.

Then, you propose an extension, and that that since it's impossible to implement
this extension without bringing more policy into the header format, you will not
accept the proposed patch (althrought it's not about this extension).

In short, I didn't understood what you don't like about the patch. I read that,
and it looks like a rather interesting solution to the problem. It's minimal,
configurable and self contained. At least, that's my feeling, but I should be
wrong...

> Maybe it's time for adding some "extras" or "add-ons" that can be 
> configure-enabled?

Erm. If possible, not ./configure enabled but ~/.quiltrc enabled. Think about
the poor guys out there who distribute binary distribution of the project...

Thanks, Mt.