From: Ryan Anderson <ryan@michonline.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Matthias Andree <matthias.andree@gmx.de>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.11
Date: Thu, 3 Mar 2005 00:20:21 -0500 [thread overview]
Message-ID: <20050303052021.GK7828@mythryan2.michonline.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0503020738300.25732@ppc970.osdl.org>
On Wed, Mar 02, 2005 at 07:46:05AM -0800, Linus Torvalds wrote:
> (In contrast the full ChangeLog was missing because the generation script
> I use is not exactly the smart way, so it's O(slow(n)), where slow is n**3
> or worse, so the log from the last -rc release is fast, but going back all
> the way to 2.6.10 took long long enough that I didn't wait for it).
Is there some reason why
bk changes -aem -rv2.6.10..+ | shortlog
isn't sufficient?
I'd guess your script will want to calculate the 2.6.10 part
automatically, but that seems to run in a second or so on my machine,
from a largely cold cache. I *think* this gets all the changes where a
-d (date) based method gets very confused by parallel trees. Am I
missing something?
--
Ryan Anderson
sometimes Pug Majere
next prev parent reply other threads:[~2005-03-03 5:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-02 8:02 Linus Torvalds
2005-02-28 18:44 ` key bounce problem with 2.6.11-rc5 Jan Niehusmann
2005-03-02 20:06 ` bouncing keys and skipping sound with 2.6.11 Jan Niehusmann
2005-03-06 18:55 ` Jan Niehusmann
2005-03-07 7:26 ` Stefan Seyfried
2005-03-12 11:13 ` Jan Niehusmann
2005-03-02 10:31 ` Linux 2.6.11 Matthias Andree
2005-03-02 11:01 ` Jesper Juhl
2005-03-02 15:46 ` Linus Torvalds
2005-03-02 16:47 ` Matthias Andree
2005-03-02 17:35 ` Linus Torvalds
2005-03-03 5:20 ` Ryan Anderson [this message]
2005-03-03 12:21 ` Matthias Andree
2005-03-02 12:47 ` Herbert Poetzl
2005-03-02 14:06 ` Michael Tokarev
2005-03-03 0:54 ` Herbert Poetzl
2005-03-02 16:18 ` John Cherry
2005-03-02 23:24 ` Jan Dittmer
2005-03-06 0:19 ` J.A. Magallon
2005-03-06 5:48 ` Trond Myklebust
2005-03-06 6:03 ` Neil Brown
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=20050303052021.GK7828@mythryan2.michonline.com \
--to=ryan@michonline.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.andree@gmx.de \
--cc=torvalds@osdl.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
Powered by JetHome