All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Zielcke <fzielcke@z-51.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: 2273 lines in 170 files consists of only space and tabulators
Date: Sat, 01 Aug 2009 15:54:03 +0200	[thread overview]
Message-ID: <1249134843.3651.6.camel@fz.local> (raw)
In-Reply-To: <E1MXBTM-0006oH-VA@fencepost.gnu.org>

Am Samstag, den 01.08.2009, 06:05 -0400 schrieb Alfred M. Szmidt:
> Uhm I thought this wasn't needed because the actual code didn't
>    change.  But okay GCS talks about all changes made to source files
>    so you're probable right.
> 
> Usually, such changes do not need to be mentioned in the ChangeLog,
> since they do not change the behaviour of anything.  The same goes for
> any formating changes, and comment fixes.
> 

Pavel once told me about 6.8.3 in GCS which says:

When you change just comments or doc strings, it is enough to write an
entry for the file, without mentioning the functions. Just “Doc fixes”
is enough for the change log

So at least comment changes should be documented.

-- 
Felix Zielcke
Proud Debian Maintainer




      reply	other threads:[~2009-08-01 13:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-06 10:25 2273 lines in 170 files consists of only space and tabulators Felix Zielcke
2009-06-06 13:43 ` Felix Zielcke
2009-06-07  1:48   ` Vladimir 'phcoder' Serbinenko
2009-06-07  1:59     ` Pavel Roskin
2009-06-07 14:32       ` Felix Zielcke
2009-06-07  1:53 ` Pavel Roskin
2009-06-10 21:04   ` Felix Zielcke
2009-07-28 18:19     ` Robert Millan
2009-07-28 21:09       ` Felix Zielcke
2009-07-31 15:39         ` Robert Millan
2009-07-31 15:45           ` Felix Zielcke
2009-07-31 16:02             ` Felix Zielcke
2009-07-31 16:24               ` Robert Millan
2009-08-01 10:05             ` Alfred M. Szmidt
2009-08-01 13:54               ` Felix Zielcke [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1249134843.3651.6.camel@fz.local \
    --to=fzielcke@z-51.de \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.