git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: git@vger.kernel.org
Subject: [BUG] git bisect should not expand file globs in log
Date: Tue, 12 Feb 2008 20:23:28 +0100	[thread overview]
Message-ID: <200802122023.28879.elendil@planet.nl> (raw)

Hi,

During a git bisect session I ended up with the following in the
.git/BISECT_LOG:

# bad: [38a382ae5dd4f4d04e3046816b0a41836094e538] Kobject: convert 
arch/alpha arch/arm arch/avr32 arch/blackfin arch/cris arch/frv arch/h8300 
arch/ia64 arch/m32r arch/m68k arch/m68knommu arch/mips arch/parisc 
arch/powerpc arch/ppc arch/s390 arch/sh arch/sh64 arch/sparc arch/sparc64 
arch/um arch/v850 arch/x86 arch/x86_64 arch/xtensa from 
kobject_unregister() to kobject_put()
git-bisect bad 38a382ae5dd4f4d04e3046816b0a41836094e538

>From the following command you can see shat happened: the 'arch/*' from the 
commit log was expanded in the comment line in the bisect log file.

$ git bisect bad
38a382ae5dd4f4d04e3046816b0a41836094e538 is first bad commit
commit 38a382ae5dd4f4d04e3046816b0a41836094e538
Author: Greg Kroah-Hartman <gregkh@suse.de>
Date:   Thu Dec 20 08:13:05 2007 -0800

    Kobject: convert arch/* from kobject_unregister() to kobject_put()

git version: 1.5.4 (current Debian unstable)

Cheers,
FJP

             reply	other threads:[~2008-02-12 19:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-12 19:23 Frans Pop [this message]
2008-02-12 19:50 ` [BUG] git bisect should not expand file globs in log Johannes Schindelin
2008-02-12 21:10   ` Frans Pop
2008-02-12 20:06 ` [PATCH] Fix shell quoting in git-bisect Alex Riesen

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=200802122023.28879.elendil@planet.nl \
    --to=elendil@planet.nl \
    --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.
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 NNTP newsgroup(s).