git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Marco Costalba" <mcostalba@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: Possible BUG in 'git log --parents'
Date: Sat, 7 Jul 2007 12:14:30 +0200	[thread overview]
Message-ID: <e5bfff550707070314q3b78ac65p9a8ff3130a7bfaef@mail.gmail.com> (raw)
In-Reply-To: <7vps348qzi.fsf@assigned-by-dhcp.cox.net>

On 7/7/07, Junio C Hamano <gitster@pobox.com> wrote:
>
> Line wrapping in the middle of a single object name makes it
> hard to read doesn't it?
>

Sorry!

> I recall we added an extra logic in rev-list side to squash the
> parent commits that artificially becomes duplicate due to this
> history simplification logic, which we might want to port to
> git-log.  However, I have a slight suspicion that we earlier
> decided not to do so on purpose with git-log and for a good
> reason.  I do not have much energy left tonight to dig into this
> right now, but mailing list log and commit log messages for
> rev-list.c, builtin-log.c and builtin-rev-list.c might tell you
> more.
>

I will take a look hoping to *not* find anything important, now that
qgit rely on git log instead of git-rev-list to show the graph, I
would really hope that it is possible to patch git-log in the same way
then git-rev-list.

Thanks
Marco

  reply	other threads:[~2007-07-07 10:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-07  9:49 Possible BUG in 'git log --parents' Marco Costalba
2007-07-07 10:09 ` Junio C Hamano
2007-07-07 10:14   ` Marco Costalba [this message]
2007-07-07 22:17     ` Marco Costalba
2007-07-08  7:59       ` Junio C Hamano
2007-07-08  9:32         ` Marco Costalba
2007-07-08 10:33           ` 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=e5bfff550707070314q3b78ac65p9a8ff3130a7bfaef@mail.gmail.com \
    --to=mcostalba@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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).