From: "Marco Costalba" <mcostalba@gmail.com>
To: "Yann DIRSON" <yann.dirson@sagem.com>
Cc: "Marco Costalba" <mcostalba@yahoo.it>,
ydirson@altern.org, git@vger.kernel.org
Subject: Re: qgit: failed assertion involving unapplied stgit patches
Date: Fri, 20 Jul 2007 19:45:45 +0200 [thread overview]
Message-ID: <e5bfff550707201045s270e0ae1p206ad62cd02ebea4@mail.gmail.com> (raw)
In-Reply-To: <OF2EB5CD3A.5A6F9DF7-ONC125731E.004BD62A-C125731E.004FCEC9@sagem.com>
On 7/20/07, Yann DIRSON <yann.dirson@sagem.com> wrote:
>
> qgit 1.5.6 cannot show me the blame window for a given file, it complains
> with the following errors:
>
Hi Yann,
Yes. I confirm it's a bug.
A patch has been pushed both for qgit 1.5.6 and for new qgit4.
> However, I'm not sure why it walks this part of the tree, since the
> per-file history view does not show unapplied patches (it would be great to
> see them, though, as well as showing applied patches as such).
>
Regarding to show unapplied patch it seems a little bit difficult
because git-log /git-rev-list does not know them, after a quick look
it would seem easier to me to show applied patches as such...I will
investigate.
BTW if you use file history viewer I would suggest to switch to new
qgit4 (git://git.kernel.org/pub/scm/qgit/qgit4.git) it requires Qt4.3
but annotation is much more powerful, follows file renames (check
against vastly renamed git repository files) and it's an order of
magnitude faster.
Marco
next prev parent reply other threads:[~2007-07-20 17:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 14:31 qgit: failed assertion involving unapplied stgit patches Yann DIRSON
2007-07-20 17:45 ` Marco Costalba [this message]
2007-07-21 7:14 ` Marco Costalba
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=e5bfff550707201045s270e0ae1p206ad62cd02ebea4@mail.gmail.com \
--to=mcostalba@gmail.com \
--cc=git@vger.kernel.org \
--cc=mcostalba@yahoo.it \
--cc=yann.dirson@sagem.com \
--cc=ydirson@altern.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).