* [Bug runtime/7052] New: branch upstream-only runtime code
@ 2008-11-25 17:58 mhiramat at redhat dot com
2008-11-25 18:02 ` [Bug runtime/7052] " fche at redhat dot com
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: mhiramat at redhat dot com @ 2008-11-25 17:58 UTC (permalink / raw)
To: systemtap
I think we could branch git tree only for upstream kernel. that is good for
upstream kernel developers.
In this branch, we should;
- remove all autoconf-*.
- use new kernel functions/macros.
Then, it could be easy to port upstream kernel.
--
Summary: branch upstream-only runtime code
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: mhiramat at redhat dot com
OtherBugsDependingO 7042
nThis:
http://sourceware.org/bugzilla/show_bug.cgi?id=7052
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
^ permalink raw reply [flat|nested] 5+ messages in thread* [Bug runtime/7052] branch upstream-only runtime code
2008-11-25 17:58 [Bug runtime/7052] New: branch upstream-only runtime code mhiramat at redhat dot com
@ 2008-11-25 18:02 ` fche at redhat dot com
2008-11-25 18:08 ` mhiramat at redhat dot com
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: fche at redhat dot com @ 2008-11-25 18:02 UTC (permalink / raw)
To: systemtap
------- Additional Comments From fche at redhat dot com 2008-11-25 18:01 -------
> 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?
--
http://sourceware.org/bugzilla/show_bug.cgi?id=7052
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
^ permalink raw reply [flat|nested] 5+ messages in thread* [Bug runtime/7052] branch upstream-only runtime code
2008-11-25 17:58 [Bug runtime/7052] New: branch upstream-only runtime code mhiramat at redhat dot com
2008-11-25 18:02 ` [Bug runtime/7052] " fche at redhat dot com
@ 2008-11-25 18:08 ` mhiramat at redhat dot com
2008-11-27 16:29 ` srikar at linux dot vnet dot ibm dot com
2010-09-07 19:21 ` fche at redhat dot com
3 siblings, 0 replies; 5+ messages in thread
From: mhiramat at redhat dot com @ 2008-11-25 18:08 UTC (permalink / raw)
To: systemtap
------- Additional Comments From mhiramat at redhat dot com 2008-11-25 18:07 -------
(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.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=7052
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug runtime/7052] branch upstream-only runtime code
2008-11-25 17:58 [Bug runtime/7052] New: branch upstream-only runtime code mhiramat at redhat dot com
2008-11-25 18:02 ` [Bug runtime/7052] " fche at redhat dot com
2008-11-25 18:08 ` mhiramat at redhat dot com
@ 2008-11-27 16:29 ` srikar at linux dot vnet dot ibm dot com
2010-09-07 19:21 ` fche at redhat dot com
3 siblings, 0 replies; 5+ messages in thread
From: srikar at linux dot vnet dot ibm dot com @ 2008-11-27 16:29 UTC (permalink / raw)
To: systemtap
------- Additional Comments From srikar at linux dot vnet dot ibm dot com 2008-11-27 16:28 -------
(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)
--
http://sourceware.org/bugzilla/show_bug.cgi?id=7052
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug runtime/7052] branch upstream-only runtime code
2008-11-25 17:58 [Bug runtime/7052] New: branch upstream-only runtime code mhiramat at redhat dot com
` (2 preceding siblings ...)
2008-11-27 16:29 ` srikar at linux dot vnet dot ibm dot com
@ 2010-09-07 19:21 ` fche at redhat dot com
3 siblings, 0 replies; 5+ messages in thread
From: fche at redhat dot com @ 2010-09-07 19:21 UTC (permalink / raw)
To: systemtap
------- Additional Comments From fche at redhat dot com 2010-09-07 19:20 -------
This is unlikely in the near term.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
http://sourceware.org/bugzilla/show_bug.cgi?id=7052
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2010-09-07 19:21 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-11-25 17:58 [Bug runtime/7052] New: branch upstream-only runtime code mhiramat at redhat dot com
2008-11-25 18:02 ` [Bug runtime/7052] " fche at redhat dot com
2008-11-25 18:08 ` mhiramat at redhat dot com
2008-11-27 16:29 ` srikar at linux dot vnet dot ibm dot com
2010-09-07 19:21 ` fche at redhat dot com
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).