All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Vignaud <tvignaud@mandriva.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Re: [alsa-cvslog] alsa-kernel: New ChangeSet 4251:05f8dd80b37c
Date: Thu, 18 May 2006 17:15:02 +0200	[thread overview]
Message-ID: <m2wtcjfjpl.fsf@vador2.mandriva.com> (raw)
In-Reply-To: <s5hhd3nz7qr.wl%tiwai@suse.de> (Takashi Iwai's message of "Thu, 18 May 2006 17:13:16 +0200")

Takashi Iwai <tiwai@suse.de> writes:

> > > But I agree that the current subject is fairly useless.  Maybe
> > > the first commit-log line would be best for the subject line,
> > > too.  It's used for the subject line of patches, so why not for
> > > notification mails, too.
> > 
> > why not? that would be as nice as knowing what was altered.
> 
> Basically I object to (automatic) inclusion of modifies files /
> directories in the summary.  I want to know more about what the
> change is for rather than which files are modified.  Usually the
> changelog summary (the first) line mentions which component is
> changed (if not, it's wide spread).  That should suffice.

i'm fine with that. i'll be better than current status :-)


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

      reply	other threads:[~2006-05-18 15:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ALOGGER1147857168.87@alsa-project.org>
2006-05-17 14:13 ` [alsa-cvslog] alsa-kernel: New ChangeSet 4251:05f8dd80b37c Thierry Vignaud
2006-05-17 14:14   ` Thierry Vignaud
2006-05-18 13:27     ` Takashi Iwai
2006-05-18 15:04       ` Thierry Vignaud
2006-05-18 15:13         ` Takashi Iwai
2006-05-18 15:15           ` Thierry Vignaud [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=m2wtcjfjpl.fsf@vador2.mandriva.com \
    --to=tvignaud@mandriva.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /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.