public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: fche@redhat.com (Frank Ch. Eigler)
To: Li Guanglei <guanglei@cn.ibm.com>
Cc: "systemtap@sources.redhat.com" <systemtap@sources.redhat.com>
Subject: Re: change the way we found matching tapsets
Date: Thu, 23 Feb 2006 14:13:00 -0000	[thread overview]
Message-ID: <y0m3biaduz0.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <43FD7B0C.4040400@cn.ibm.com>

Li Guanglei <guanglei@cn.ibm.com> writes:

> [...] I found that the syscall table stays almost
> the same for each major kernel version, e.g. the syscall table of all
> 2.6.15.* are the same. So I want a directory 2.6.15 to handles all
> 2.6.15.* versions(including 2.6.15.1, 2.6.15.2 etc). [...]

Makes sense to me.  The current search path logic was chosen before
this newfangled four-level a.b.c.d version numbering scheme arrived.

- FChE

      reply	other threads:[~2006-02-23 14:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-23  9:06 Li Guanglei
2006-02-23 14:13 ` Frank Ch. Eigler [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=y0m3biaduz0.fsf@ton.toronto.redhat.com \
    --to=fche@redhat.com \
    --cc=guanglei@cn.ibm.com \
    --cc=systemtap@sources.redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).