All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Timur Tabi <timur.tabi@ammasso.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux.bkbits.net question: mapping cset to kernel version?
Date: Wed, 18 May 2005 09:51:48 -0700	[thread overview]
Message-ID: <20050518165148.GC17307@kroah.com> (raw)
In-Reply-To: <428B6BF8.2010303@ammasso.com>

On Wed, May 18, 2005 at 11:23:20AM -0500, Timur Tabi wrote:
> 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.

Yes, and that tagging worked just fine.  You can see this too if you
want to check out a tree based on a tag.

> What does he do now?

Uses git, which will have the same issues as you are facing :)

Please remeber, with a distributed development system like this, going
off of the "date" means _nothing_.  What matters is when that patch and
branch is merged into his tree, and to determine that, you will have to
dig around a bit.

And since you have raw patches, and know what you are looking for, the
solution should be very simple (hint, grep...)

Good luck,

greg k-h

  reply	other threads:[~2005-05-18 16:55 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
2005-05-18 16:51     ` Greg KH [this message]
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=20050518165148.GC17307@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=timur.tabi@ammasso.com \
    /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.