linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "David H. Lynch Jr." <dhlii@dlasys.net>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: how to get individual patches
Date: Sun, 16 Jul 2006 23:46:22 -0400	[thread overview]
Message-ID: <44BB080E.6060107@dlasys.net> (raw)
In-Reply-To: <528646bc0607141122t53adeb30h8c2acb4e26ba0ddf@mail.gmail.com>

Grant Likely wrote:
> On 7/14/06, David H. Lynch Jr. <dhlii@dlasys.net> wrote:
>
> AFAIK, yes you will have to repatch every time; I typically write a
> little helper script to lessen the pain:
>
> git bisect good|bad # depends on whether it works or not
> patch < [patchfile]
> compile, test, etc
> cg restore -f     # Remove the patches
> git bisect good|bad   # lather, rinse, repeate
>
    Alright, I have bisected my way down to the problem.
    Well sort of.
    I think the real problem I started looking for eventually got fixed
in the kernel tree on its own.

    But I did find a real problem. I have found my own work around - but
this problem may effect others.

    The zlib library was updated within the past month.
    The new zlib code does not work in my environment.
    I have guesses as to why, but I am not a zlib expert and not looking
to be one.
    I have solved my personal problem by reverting to the older zlib code.
    With that I have 2.6.18-rc4 or whatever is in the linux-2.6 git tree
as of today working for me.
    I was stuck at 2.6.16.21 before.
   
    So my questions:

    How/where do I report a problem ? I would be perfectly happy to help
whoever is responsible for zlib to work this out.
    But I am not up to doing it myself.

    git bisect got me down to a good/bad scenario. But I could not
provoke git to either pull the offending patch or export the change as a
patch so that I could back it out myself.
    Now that the final git bisect screen is gone all I have (besides a
fixed 2.6.18-xx kernel) is I guess the sha has number for the particular
commit.
    I suspect that would have been enough to yank just that patch but I
googled every permutation of git backout or similar things I could think
of and browsed the git tutorials etc.
    and could not seem to decipher how to do anything usefull with the
sha id of a single patch.
    I am sure that is a knowledge problem.






-- 
Dave Lynch 					  	    DLA Systems
Software Development:  				         Embedded Linux
717.627.3770 	       dhlii@dlasys.net 	  http://www.dlasys.net
fax: 1.253.369.9244 			           Cell: 1.717.587.7774
Over 25 years' experience in platforms, languages, and technologies too numerous to list.

"Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction."
Albert Einstein

  reply	other threads:[~2006-07-17  3:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-27 18:38 Lite5200 MTD partitions in 2.6 build Rowan, Chad
2006-06-27 19:24 ` White
2006-06-28  7:49   ` how to get individual patches David H. Lynch Jr.
2006-06-28  8:32     ` Alex Zeffertt
2006-06-28 16:22       ` David H. Lynch Jr.
2006-06-28  9:09     ` Grant Likely
2006-06-28 16:18       ` David H. Lynch Jr.
2006-07-14 18:13       ` David H. Lynch Jr.
2006-07-14 18:22         ` Grant Likely
2006-07-17  3:46           ` David H. Lynch Jr. [this message]
2006-07-17  5:30             ` Grant Likely

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=44BB080E.6060107@dlasys.net \
    --to=dhlii@dlasys.net \
    --cc=dhlii@comcast.net \
    --cc=grant.likely@secretlab.ca \
    --cc=linuxppc-embedded@ozlabs.org \
    /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 NNTP newsgroup(s).