From: Timur Tabi <timur.tabi@ammasso.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux.bkbits.net question: mapping cset to kernel version?
Date: Wed, 18 May 2005 11:23:20 -0500 [thread overview]
Message-ID: <428B6BF8.2010303@ammasso.com> (raw)
In-Reply-To: <20050518160930.GA16756@kroah.com>
Greg KH wrote:
> But that's how you have to do it, sorry. You have the patches, why
> can't you just use grep? :)
What does Linus do to keep track of these changes? Granted, he's not using BitKeeper any
more, but it does support release management, so I would presume he was tagging the
releases with it. What does he do now?
--
Timur Tabi
Staff Software Engineer
timur.tabi@ammasso.com
One thing a Southern boy will never say is,
"I don't think duct tape will fix it."
-- Ed Smylie, NASA engineer for Apollo 13
next prev parent reply other threads:[~2005-05-18 16:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 14:11 linux.bkbits.net question: mapping cset to kernel version? Timur Tabi
2005-05-18 15:00 ` Hugh Dickins
2005-05-18 15:01 ` Timur Tabi
2005-05-18 15:14 ` Hugh Dickins
2005-05-18 16:09 ` Greg KH
2005-05-18 16:23 ` Timur Tabi [this message]
2005-05-18 16:51 ` Greg KH
2005-05-18 23:13 ` Linus Torvalds
2005-05-18 16:36 ` patrick mcmanus
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=428B6BF8.2010303@ammasso.com \
--to=timur.tabi@ammasso.com \
--cc=greg@kroah.com \
--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