What I do is to follow along with things on the shortlog:
http://source.winehq.org/git/?p=wine.git;a=shortlog
Lets say you want to move your current branch to my recent patch
"riched20: Rewrite of scrolling and some redrawing code." - you'd
click the link "commit" to the right of it. In the page that you'll be
taken to, you'll see a line like this:
commit abecd9e393925e008449a80ec14682790b29042c
you can then do a "git reset --hard abecd9e393925e008449a80ec14682790b29042c"
and your git will be moved to the point in time right after that
commit. If you then want to manually apply a patch, click "commitdiff"
to the right of it's entry in the shortlog, followed by "plain" on the
top - this will take you to a plaintext diff of the patch, which you
could save to a file and apply with the patch command. ("patch -p1 <
thepatch.diff" usualy works well for me)
--Matt
On 9/9/06, Kapila De Silva <[EMAIL PROTECTED]> wrote:
Hi all,
Hope this is the right place to post this, if not, my apologies.
Im trying to track down an issue that occurred between 0.9.19 and
0.9.20, and am using git bisect to track the issue. In the process of
trying to identify the cause of the issue, I would like to be able to
get the code up till a certain patch, and then apply patches one by one
as well.
I have not been able to find out how to do this, despite several web
searches and man pages. Can anyone give me any pointers to this please?
Thanks in advance
Kapila
