From: Matthieu Moy <matthieu.moy@grenoble-inp.fr>
To: Michael Haggerty <mhagger@alum.mit.edu>
Cc: Jacopo Notarstefano <jacopo.notarstefano@gmail.com>,
git@vger.kernel.org,
Christian Couder <christian.couder@gmail.com>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: An idea for "git bisect" and a GSoC enquiry
Date: Thu, 27 Feb 2014 13:09:52 +0100 (CET) [thread overview]
Message-ID: <239563375.177900.1393502992014.JavaMail.zimbra@imag.fr> (raw)
In-Reply-To: <530F1F11.7060403@alum.mit.edu>
----- Original Message -----
> I don't understand the benefit of adding a new command "mark" rather
> than continuing to use "good", "bad", plus new commands "unfixed" and
> "fixed". Does this solve any problems?
I think it could be interesting to allow arbitrary words here. For example, I recently walked through history to find a performance regression, it would have been natural to use slow/fast instead of bad/good (bad/good would actually do the job, but slightly less naturally). One can look for a change which is neither a fix nor a bug (e.g. when did command foo start behaving like that? when did we start using such or such feature in the code).
I wouldn't fight for it, but I think it makes sense.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2014-02-27 12:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 8:28 An idea for "git bisect" and a GSoC enquiry Jacopo Notarstefano
2014-02-26 19:58 ` Junio C Hamano
2014-02-28 9:00 ` Jacopo Notarstefano
2014-02-27 11:18 ` Michael Haggerty
2014-02-27 12:09 ` Matthieu Moy [this message]
2014-02-28 9:03 ` Jacopo Notarstefano
2014-02-28 18:31 ` Junio C Hamano
2014-03-01 11:31 ` Jacopo Notarstefano
2014-03-03 18:34 ` Junio C Hamano
2014-03-12 1:32 ` Jacopo Notarstefano
2014-03-12 18:31 ` Junio C Hamano
2014-03-13 17:19 ` Michael Haggerty
2014-03-13 18:47 ` Junio C Hamano
[not found] ` <CAL0uuq3TGb2wjaqNxwXYa++E5rjVoozox5mZbzTaE17OKtsVTg@mail.gmail.com>
[not found] ` <a8cf74b4-bae1-4511-a45e-d4ca90e3c3e1@email.android.com>
2014-02-28 9:07 ` Jacopo Notarstefano
2014-02-28 9:13 ` Jacopo Notarstefano
2014-02-27 14:47 ` Christian Couder
2014-02-27 22:46 ` Andrew Ardill
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=239563375.177900.1393502992014.JavaMail.zimbra@imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jacopo.notarstefano@gmail.com \
--cc=mhagger@alum.mit.edu \
/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).