Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: ghaskins@novell.com (Gregory Haskins)
Subject: [ltt-dev] Problems with merging patch-2.6.30-rc2-lttng-0.126
Date: Thu, 23 Apr 2009 15:21:47 -0400	[thread overview]
Message-ID: <49F0BFCB.9080506@novell.com> (raw)
Message-ID: <20090423192147.23mHYMqMemWoZjdkn6YmLN6UA1BsimVoVsTRG7Rw5WI@z> (raw)
In-Reply-To: <20090423191243.GA22770@Krystal>

Mathieu Desnoyers wrote:
> * Gregory Haskins (ghaskins at novell.com) wrote:
>   
>> Mathieu Desnoyers wrote:
>>     
>>> * Gregory Haskins (ghaskins at novell.com) wrote:
>>>   
>>>       
>>>> Hi all,
>>>>   I am trying to apply 2.6.30-rc2-lttng-0.126 to a clean 2.6.30-rc2 and
>>>> I am getting lots of rejects.  I went through one time and resolved all
>>>> the rejects, but the resulting kernel did trace properly so I perhaps
>>>> had some fuzz issues.  What kernel base should I be using for this series?
>>>>
>>>>     
>>>>         
>>> Hrm, weird, I may have messed up the packaging. I just released LTTng
>>> 0.127 which should not have such conflicts.
>>>   
>>>       
>> Hi Mathieu,
>>  I am seeing more or less the same thing with 0.127.  The series has a
>> ton of conflicts against 30-rc2 and even itself.  Its as if the patches
>> are based on a different tree. 
>>
>> Its probably operator error, but I cannot see what I am doing wrong. 
>> Its the same procedure I have always used to bring your tree in.
>>
>>     
>
> Hmmmmm... it works here... (just tested it again to make sure)
>
> Can you give me the exact sequence of operation you use to apply the
> patchset ? (getting kernel.org tarballs/git, unpacking the lttng
> patchset, using quilt...)
>   

Sure, I am using git as the base, and then stgit "import" to pull the
series in.  Here is a dump of my history from my current attempt:

 1070  git clone -l linux-2.6 linux-2.6-ltt
 1071  cd linux-2.6-ltt/
 1072  wget
http://ltt.polymtl.ca/files/lttng/patch-2.6.30-rc2-lttng-0.127.tar.bz2
 1073  tar -jxvf patch-2.6.30-rc2-lttng-0.127.tar.bz2
 1074  git branch
 1075  git checkout -b master v2.6.30-rc2
 1076  git log
 1077  stg init
 1078  stg import --ignore -s patch-2.6.30-rc2-lttng-0.127/series

I have confirmed that Linus' 2.6.30-rc2 tag is the ancestor that
immediately precedes the first LTT patch.  I have used this same
procedure for years successfully, including working with LTT.  I'm sure 
I am doing something wrong, but I can't see it.

-Greg


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 266 bytes
Desc: OpenPGP digital signature
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20090423/805fff1c/attachment-0002.pgp>


  parent reply	other threads:[~2009-04-23 19:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23 13:53 Gregory Haskins
2009-04-23 17:39 ` Mathieu Desnoyers
2009-04-23 17:39   ` Mathieu Desnoyers
2009-04-23 17:53   ` Gregory Haskins
2009-04-23 17:53     ` Gregory Haskins
2009-04-23 18:55   ` Gregory Haskins
2009-04-23 18:55     ` Gregory Haskins
2009-04-23 19:12     ` Mathieu Desnoyers
2009-04-23 19:12       ` Mathieu Desnoyers
2009-04-23 19:21       ` Gregory Haskins [this message]
2009-04-23 19:21         ` Gregory Haskins
2009-04-23 19:34         ` Mathieu Desnoyers
2009-04-23 19:34           ` Mathieu Desnoyers
2009-04-23 19:54           ` Gregory Haskins
2009-04-23 19:54             ` Gregory Haskins
2009-04-23 20:58           ` Gregory Haskins
2009-04-23 20:58             ` Gregory Haskins
2009-04-23 21:17             ` Mathieu Desnoyers
2009-04-23 21:17               ` Mathieu Desnoyers
2009-04-23 19:09   ` Gregory Haskins
2009-04-23 19:09     ` Gregory Haskins
2009-04-23 19:18     ` Mathieu Desnoyers
2009-04-23 19:18       ` Mathieu Desnoyers

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=49F0BFCB.9080506@novell.com \
    --to=ghaskins@novell.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