git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Marco Costalba" <mcostalba@gmail.com>
To: "Junio C Hamano" <junkio@cox.net>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: Possible regression in git-rev-list --header
Date: Tue, 2 Jan 2007 23:29:14 +0100	[thread overview]
Message-ID: <e5bfff550701021429j1587949fgfe19effcaf74e6df@mail.gmail.com> (raw)
In-Reply-To: <7vps9xrs9y.fsf@assigned-by-dhcp.cox.net>

On 1/2/07, Junio C Hamano <junkio@cox.net> wrote:
>
> > And Marco has to fix the header parsing anyway.
>
> No question about that.  If iconv() punts, qgit will see
> "encoding" header to deal with even when the re-coding is in
> effect.  I think it may be a sensible thing for qgit to replace
> the log message and show "log message in this encoding, which
> cannot be shown in this window" instead in such a case, but that
> is up to Porcelain.
>

Yes, git-rev-list output is stored in memory as a big chunk of row
bytes, conversion
to utf8 (the internal format used by Qt string class) is done _only_
for displayed items, just
before to show them to user so is not performance critical. I agree
with Junio, that info could be used to teach Qt string conversion
function how to handle the data. Something like:

         convertWithCodec(const char* data, codec* codecName)

So perhaps if Qt is better then iconv we could display a good log
message anyway.

  parent reply	other threads:[~2007-01-02 22:29 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-30 17:56 Possible regression in git-rev-list --header Marco Costalba
2006-12-30 18:30 ` Jakub Narebski
2006-12-30 18:57 ` Johannes Schindelin
2006-12-30 20:20   ` Junio C Hamano
2006-12-30 22:19     ` Junio C Hamano
2006-12-31  1:13       ` Johannes Schindelin
2006-12-31  1:45         ` Junio C Hamano
2006-12-31 11:45           ` Marco Costalba
2006-12-31 15:27             ` Johannes Schindelin
2006-12-31 15:43               ` Marco Costalba
2007-01-01  3:21                 ` Junio C Hamano
2007-01-02 21:32                   ` Johannes Schindelin
2007-01-02 22:13                     ` Junio C Hamano
2007-01-02 22:28                       ` Johannes Schindelin
2007-01-02 22:29                       ` Marco Costalba [this message]
2007-01-03  9:21                   ` Marco Costalba
2007-01-03 10:10                     ` Junio C Hamano
2007-01-03 10:21                     ` Lars Hjemli
2007-01-03 10:35                       ` Marco Costalba
2007-01-03 11:14                         ` Lars Hjemli
2007-01-04 15:21                           ` Andreas Ericsson
2007-01-04 15:18                         ` Andreas Ericsson
2007-01-03 10:38                       ` Lars Hjemli
2006-12-31  0:37     ` Johannes Schindelin
2006-12-30 20:22   ` [PATCH] Move commit reencoding parameter parsing to revision.c Junio C Hamano
2006-12-31  1:10     ` Johannes Schindelin

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=e5bfff550701021429j1587949fgfe19effcaf74e6df@mail.gmail.com \
    --to=mcostalba@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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).