git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Sixt <j.sixt@viscovery.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>,
	Alejandro Riveira <ariveira@gmail.com>,
	git@vger.kernel.org
Subject: Re: [PATCH] gitk: fix 'can't read "notflag"'
Date: Thu, 04 Dec 2008 16:59:21 +0100	[thread overview]
Message-ID: <4937FE59.2030906@viscovery.net> (raw)
In-Reply-To: <alpine.DEB.1.00.0812041609150.7045@racer>

Johannes Schindelin schrieb:
> On Thu, 4 Dec 2008, Johannes Schindelin wrote:
> 
>> diff --git a/gitk-git/gitk b/gitk-git/gitk
> 
> D'oh.  Please apply with -p2.

No; pull -s subtree before you write this patch ;) It's already fixed in
upstream gitk.

-- Hannes

      reply	other threads:[~2008-12-04 16:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-03 11:20 [BUG] git bisect visualize crash Alejandro Riveira
2008-12-04 14:34 ` [PATCH] gitk: fix 'can't read "notflag"' Johannes Schindelin
2008-12-04 15:09   ` Johannes Schindelin
2008-12-04 15:59     ` Johannes Sixt [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=4937FE59.2030906@viscovery.net \
    --to=j.sixt@viscovery.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=ariveira@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=paulus@samba.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).