emacs-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Emacs-commit] emacs/src ChangeLog


From: Pavel Janík
Subject: Re: [Emacs-commit] emacs/src ChangeLog
Date: Thu, 25 Oct 2001 11:52:47 +0200
User-agent: Gnus/5.090004 (Oort Gnus v0.04) Emacs/21.1.50 (i386-suse-linux-gnu)

   From: Eli Zaretskii <address@hidden>
   Date: Thu, 25 Oct 2001 11:34:18 +0200 (IST)

   > IMHO, yes: sometimes ChangeLog changes are real.  But I can understand
   > why someone would like to avoid that, so maybe we should have an
   > option to do that.

Yes, sometimes yes. I did not thought about this case.

   > The problem is that, currently, the script which sends these
   > notifications is global: it doesn't depend on the addressee.  So if
   > the majority doesn't want to see ChangeLog's in this list, we will
   > have to force the minority to yield ;-)  Or we could have two mailing
   > list, with and without that option.

This is an administrative overhead, I think that administrators have better
things to do :-)

   > > b. what about adding differences between revisions directly to the 
message?
   > > Do you want to see them directly in the body of message?
   > 
   > Richard already asked for that.
   > 
   > Personally, I find the current mode very convenient: most of the
   > changes are not interesting enough for me to look at the diffs.

Maybe an additional list here can be helpful - I too understand that people
with full IP connection all the time do not want to receive both patches
and the same thing again weh doing cvs up.

   > Note that, as far as I understand, the diffs are not computed until
   > you point your browser at the URL that you see in the emacs-commit
   > message.  It's not that the diffs are stored somewhere, waiting for
   > you to look at them: the URL actually invokes CVS to produce them when
   > you ask for them.  So the current arrangement saves some processing
   > load as well.

Of course - this is how viewcvs works. It is not problem to put a line in
commitinfo CVS file to send the patch attached.
-- 
Pavel Janík

I have decided to leave lkml because everybody else is doing it too.
                  -- Matthew Fredrickson in lkml



reply via email to

[Prev in Thread] Current Thread [Next in Thread]