Summary: | branch upstream-only runtime code | ||
---|---|---|---|
Product: | systemtap | Reporter: | Masami Hiramatsu <mhiramat> |
Component: | runtime | Assignee: | Unassigned <systemtap> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Host: | Target: | ||
Build: | Last reconfirmed: | ||
Bug Depends on: | |||
Bug Blocks: | 7042 |
Description
Masami Hiramatsu
2008-11-25 17:57:07 UTC
> I think we could branch git tree only for upstream kernel.
But which upstream kernel exactly?
How many of these branches should we maintain and/or distribute with systemtap?
(In reply to comment #1) > But which upstream kernel exactly? I think the latest -rc is good enough. > How many of these branches should we maintain and/or distribute with systemtap? Just one branch is enough, and update that code against the latest kernel. It's a kind of launch-pad for upstream code merging. (In reply to comment #2) > > Just one branch is enough, and update that code against the latest kernel. > It's a kind of launch-pad for upstream code merging. > I think just having one branch is a good idea. But we could keep tagging it to the kernel versions in the same branch so that a person trying to use a previous kernel would still have a way to use this branch (if and only if the latest systemtap at that time wouldn't work on a previous kernel) This is unlikely in the near term. |