All of lore.kernel.org
 help / color / mirror / Atom feed
From: bill4carson@gmail.com (bill4carson)
To: kernelnewbies@lists.kernelnewbies.org
Subject: how to use git bisect on such seanario
Date: Mon, 24 Dec 2012 11:03:39 +0800	[thread overview]
Message-ID: <50D7C60B.50907@gmail.com> (raw)
In-Reply-To: <CAJydemmm-WXgbavfwNfSfV37USS9_DPV3bQZRiaxKBEsjU_=4w@mail.gmail.com>

thanks, I know what you mean, let the good be "bad",and the bad be "good"????


On 2012?12?24? 10:57, Subramaniam Appadodharana wrote:
> It should work the same way as for finding a bug. Only the "bad" commit would simply be the one to solve the bug
> 
> On Sunday, December 23, 2012, bill4carson <bill4carson at gmail.com <mailto:bill4carson@gmail.com>> wrote:
>  > Hi, list
>  >
>  > Usually, we use git bisect to identify which commit causes trouble,
>  >
>  > while how do I do when need to find out which commit solve problem?
>  > for example, it's know there is an bug since commit A, but I find out
>  > the newest version (commit B)is good, so one commit between commit A and
>  > B solve the problem,
>  >
>  >
>  > thanks
>  >
>  > --
>  > ?????????
>  >
>  > --bill
>  >
>  > _______________________________________________
>  > Kernelnewbies mailing list
>  > Kernelnewbies at kernelnewbies.org <mailto:Kernelnewbies@kernelnewbies.org>
>  > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>  >

-- 
?????????

--bill

      reply	other threads:[~2012-12-24  3:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-24  2:35 how to use git bisect on such seanario bill4carson
2012-12-24  2:57 ` Subramaniam Appadodharana
2012-12-24  3:03   ` bill4carson [this message]

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=50D7C60B.50907@gmail.com \
    --to=bill4carson@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.