git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: "Aaron S. Meurer" <asmeurer@gmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git bisect problems/ideas
Date: Tue, 18 Jan 2011 10:04:29 +0100	[thread overview]
Message-ID: <AANLkTi=A2Twepg3Jo_VYxtvghkhx6ixcpRH3332BoRQo@mail.gmail.com> (raw)
In-Reply-To: <54DED602-0BA7-4462-AC00-1DDEEF83068C@gmail.com>

On Mon, Jan 17, 2011 at 7:23 PM, Aaron S. Meurer <asmeurer@gmail.com> wrote:
> On Jan 17, 2011, at 2:38 AM, Christian Couder <christian.couder@gmail.com>
> wrote:
>
>> Hi,
>>
>> On Sat, Jan 15, 2011 at 8:33 AM, Aaron S. Meurer <asmeurer@gmail.com>
>> wrote:
>>>
>>> First off, do you guys have an issue tracker?
>>
>> No, we don't. We use the mailing list.
>>
>
> Well that's amazing to me. How on Earth fo you manage stuff?

Well, bugs are usually fixed within days after they have been
reported. Otherwise they are usually documented in the code or in the
documentation or in the test suite (with test_expect_failure).

For the rest we rely on people remembering what happened and on
people's mailing list searching skills ;-)

>> If more people want it, yeah, we can create such a shortcut. But you
>> can also use a git alias for that.
>>
>
> Can you alias "git bisect stop", or would you have to alias "git
> bisect-stop"?

I think you have to alias "git bisect-stop".

I am not sure because when I use aliases I prefer to use shell aliases like:

alias gst='git status'

>> Yeah, many people find it difficult to reverse the meaning of "bad"
>> and "good" when looking for a fix. There were some suggestions at some
>> points to do something about it. Some of the suggestions were to use
>> some aliases for "good" and "bad", but there was no agreement. Other
>> suggestions had a patch attached but the patch was not good enough or
>> something.
>>
>> Anyway, the restriction is that the "bad" commit cannot be an ancestor
>> of a "good" commit. But the "good" commits need not be all ancestors
>> of the "bad" commit. For example if you have a "master" branch and a
>> "dev" branch that was forked from the "master" branch at one point,
>> like that:
>>
>> A-B-C-D-E <-- master
>>     \F-G <-- dev
>>
>
> I don't understand how this can only be one way?  Isn't this symmetric?  In
> other words, how is it different from
>
> A-B-C-D-E <-- dev
>    \F-G <-- master
>
> as far as bisect is concerned? Or maybe I am not entirely clear on what you
> are saying.

Yes, it is symmetric, so we cannot just automatically reverse the
meanning because there is no "after" or "before" relationship between
"dev" and "master".

Best regards,
Christian.

  reply	other threads:[~2011-01-18  9:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-15  7:33 git bisect problems/ideas Aaron S. Meurer
2011-01-17  9:38 ` Christian Couder
2011-01-17 11:51   ` Jonathan Nieder
2011-01-17 13:38     ` SZEDER Gábor
2011-01-17 20:55       ` Jonathan Nieder
2011-01-18  9:05         ` Christian Couder
2011-01-17 18:27     ` Aaron S. Meurer
2011-01-17 18:23   ` Aaron S. Meurer
2011-01-18  9:04     ` Christian Couder [this message]
2011-01-18 18:34       ` Junio C Hamano
2011-01-19 13:15         ` Christian Couder
2011-01-19 19:15         ` Aaron S. Meurer
2011-01-19 19:29           ` Junio C Hamano
2011-01-19 19:44       ` Aaron S. Meurer
2011-01-21 13:18         ` Christian Couder
2011-01-21 22:04           ` Johannes Sixt
2011-01-22 14:52             ` Jakub Narebski

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='AANLkTi=A2Twepg3Jo_VYxtvghkhx6ixcpRH3332BoRQo@mail.gmail.com' \
    --to=christian.couder@gmail.com \
    --cc=asmeurer@gmail.com \
    --cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).