git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Marco Costalba" <mcostalba@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: git@vger.kernel.org, proski@gnu.org
Subject: Re: [ANNOUNCE] qgit 1.1.1
Date: Mon, 20 Mar 2006 17:32:16 +0100	[thread overview]
Message-ID: <e5bfff550603200832h4373dcb4vda4a6c622d9ab6bc@mail.gmail.com> (raw)
In-Reply-To: <20060320144613.GA25617@elte.hu>

On 3/20/06, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Marco Costalba <mcostalba@gmail.com> wrote:
>
> > The wrong command is git-diff-tree -r -c -p 46571...
> >
> > I think it's about the quite new option -c of git-diff-tree.
> >
> > Please upgrade your git to latest version, better upstream one, but
> > 1.2.4 should be enough.
>
> ok, that did the trick.
>
> there's a weird rendering artifact as well, see the white line in the
> screenshot [that i'll send you in a separate mail]. It goes away if i
> drag another window in front of the qgit window. It happens if i
> double-click a 'merge' branch, exit qgit and start it again [and the
> separator line needs to obscur the commit line just partially]. This is
> an uptodate FC4 installation.
>
Yes, sometimes I see it either. To remove I use the scrollbar to
hide/unhide the line,
i.e. to force a repaint.

I think it is something related to Qt rendering engine, I doubt I
could do something about it.

BTW someone off list suggested me to implement a 'git version check'
control and related message box to avoid your troubles to someone
else: I'm surely going to do it.

Marco

      reply	other threads:[~2006-03-20 16:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-19 16:53 [ANNOUNCE] qgit 1.1.1 Marco Costalba
2006-03-19 21:49 ` Ingo Molnar
2006-03-19 22:01   ` Marco Costalba
2006-03-19 22:04     ` Marco Costalba
2006-03-20 10:20       ` Ingo Molnar
2006-03-20 12:13         ` Marco Costalba
2006-03-20 14:46           ` Ingo Molnar
2006-03-20 16:32             ` Marco Costalba [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=e5bfff550603200832h4373dcb4vda4a6c622d9ab6bc@mail.gmail.com \
    --to=mcostalba@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=proski@gnu.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).