git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Brian Zitzow <bzitzow@gmail.com>,
	git@vger.kernel.org,
	Christopher Cameron <christopher.cameron@live.com>,
	Henrik Tidefelt <tidefelt@isy.liu.se>
Subject: Re: fatal: BUG: dashless options don't support arguments
Date: Fri, 8 Oct 2010 00:11:00 -0400	[thread overview]
Message-ID: <20101008041100.GA3272@sigill.intra.peff.net> (raw)
In-Reply-To: <20101008031818.GC992@burratino>

On Thu, Oct 07, 2010 at 10:18:18PM -0500, Jonathan Nieder wrote:

> > Ki:$ git checkout master
> > fatal: BUG: dashless options don't support arguments
> 
> Strange indeed.  Here's what I would suggest:
> 
> 1. For debugging output:
> 
>  $ echo 'prefix=/usr/local' >>config.mak; # or whatever prefix you use
>  $ git describe
>  $ gcc --version
>  $ wget 'http://download.gmane.org/gmane.comp.version-control.git/128067/128068'
>  $ git am -3 128068
>  $ make
>  $ bin-wrappers/git checkout m

Yeah, I would be curious to see the output of that. Interesting, too,
that it seems to happen with multiple commands (it looked like it
happened with "git push foo" in the pastebin from the irc log).

> 2. To track down the issue, if you like to read assembler:
> 
>  $ make builtin/checkout.s
>  $ vi checkout.s

Ugh. I think a better course of action is to find out which option is
being munged (from step 1 above), and then try running it under gdb with
a watch set on that option struct. Assuming it's easily reproducible of
course.

-Peff

  reply	other threads:[~2010-10-08  4:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTi=xscHHPTBtTJ3uXPO9y9gpQTBF4AWTe47C9njU@mail.gmail.com>
2010-10-08  0:06 ` fatal: BUG: dashless options don't support arguments Brian Zitzow
2010-10-08  3:18   ` Jonathan Nieder
2010-10-08  4:11     ` Jeff King [this message]
2010-10-08  6:59   ` Johannes Sixt

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=20101008041100.GA3272@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=bzitzow@gmail.com \
    --cc=christopher.cameron@live.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=tidefelt@isy.liu.se \
    /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).