luke - I updated 677 with these:

commit 35e802c3de7d22e040ed2ad9b5dedbf8f8178efa is OK
commit 271a8aa2344cabe34680d4d345975012242ebeea breaks things

Could you explain what git commands I should now run to attempt to get the
HEAD minus this particular bad revision?  Do I stop here or should I start
"branching" a custom solution?  I apologize that I'm not familiar with git
or "best practices" for submitting a patch.  Could you provide a sample set
of git workflow commands that you would now do if you were me, and wanted
to fix this myself?

thanks,
mike

On Thu, Jan 12, 2012 at 10:50 AM, lkcl luke <[email protected]> wrote:

> On Thu, Jan 12, 2012 at 3:21 PM, Michael Yang <[email protected]>
> wrote:
> > Could anyone tell me what git commands to run to get a working version of
> > 0.8a1 on Mac OS X?  Whichever one is listed on SF is
> > causing http://code.google.com/p/pyjamas/issues/detail?id=677
>
>  ok if you do "git log", you will see a list of references.  use
> binary search to cut the list in half each time, using "git checkout
> {NNNNN}" and rebuild each time (remember to do git clean -f to remove
> everything before-hand).
>
>  if the build works, take the top half of the list.  if it fails, take
> the other half.  very very quickly you will have only 2 git checkins
> left.
>
>  please add those checkin numbers to the bugreport.
>
>  l.

Reply via email to