public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Chris Wright <chrisw@osdl.org>,
	Moritz Muehlenhoff <jmm@inutil.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.11.6
Date: Sun, 27 Mar 2005 13:59:03 -0500	[thread overview]
Message-ID: <20050327185902.GC708@redhat.com> (raw)
In-Reply-To: <20050327185259.GD5164@mythryan2.michonline.com>

On Sun, Mar 27, 2005 at 01:52:59PM -0500, Ryan Anderson wrote:
 > On Sat, Mar 26, 2005 at 01:27:53AM -0800, Chris Wright wrote:
 > > > Could you please add CAN IDs to the stable changelog for already assigned
 > > > vulnerabilities?
 > > 
 > > That's what I did for .5 -> .6.  We can't retroactively update changeset
 > > comments, and I'm not sure we have any other candidates in -stable.
 > > We'll certainly continue to add them as we have them.
 > 
 > bk helptool comments
 > 
 > You can, actually.

"Nota  bene:  if  the  deltas  being  commented have been committed to a
 changeset and have been pulled out  of  this  repository,  the  comment
 changes  will  not  propagate on the next bk pull.  It is strongly sug-
 gested that you use this only on  uncommitted  deltas  which  have  not
 been  pulled  or cloned.  In the future, we will add a way of enforcing this."

That would suggest otherwise.

		Dave


  reply	other threads:[~2005-03-27 18:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050326024616.GM28536@shell0.pdx.osdl.net>
2005-03-26  3:39 ` Linux 2.6.11.6 Chris Wright
2005-03-26  3:41   ` Chris Wright
2005-03-26  3:47     ` Hua Zhong
2005-03-26  3:56       ` Kyle Moffett
2005-03-26  3:58       ` Chris Wright
2005-03-26  8:50   ` Moritz Muehlenhoff
2005-03-26  9:27     ` Chris Wright
2005-03-27 18:52       ` Ryan Anderson
2005-03-27 18:59         ` Dave Jones [this message]
2005-03-27 19:59         ` Chris Wright

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=20050327185902.GC708@redhat.com \
    --to=davej@redhat.com \
    --cc=chrisw@osdl.org \
    --cc=jmm@inutil.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox