All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Eugene Sajine <euguess@gmail.com>
Cc: Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org
Subject: Re: cannot find hash in the log output
Date: Fri, 3 Dec 2010 14:55:34 -0600	[thread overview]
Message-ID: <20101203205534.GA15658@burratino> (raw)
In-Reply-To: <AANLkTin94XN8_+q8a1EdfY3ySqJpx_j9megQYsq8a8ux@mail.gmail.com>

Eugene Sajine wrote:

> ::SourceMode1 SourceMode2 resultMode Source1-SHA1 Source2-SHA1 resultingSHA1 MM path/to/file
[...]
> 1. a) Why this exact output is not provided in "git log --raw" or in
> "git whatchanged" for the merge commits? b) Can it be provided?

Sorry to be opaque.  "git log" et al accept -c too, of course. :)  I pointed
to diff-tree because it seems you are scripting, so its simplicity and
better guarantees about long-term compatibility might be appealing.

Cheers,
Jonathan

  reply	other threads:[~2010-12-03 20:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-02 19:57 cannot find hash in the log output Eugene Sajine
2010-12-02 20:48 ` Junio C Hamano
2010-12-02 21:07   ` Eugene Sajine
2010-12-03 17:41     ` Eugene Sajine
2010-12-03 17:52       ` Jeff King
2010-12-03 20:10         ` Eugene Sajine
2010-12-03 20:29           ` Jonathan Nieder
2010-12-03 20:53             ` Eugene Sajine
2010-12-03 20:55               ` Jonathan Nieder [this message]
2010-12-03 21:01                 ` Eugene Sajine
2010-12-03 21:02                 ` Junio C Hamano
2010-12-04  1:08                   ` Jonathan Nieder
2010-12-03 21:11           ` Jeff King
2010-12-03 21:52             ` Jeff King

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=20101203205534.GA15658@burratino \
    --to=jrnieder@gmail.com \
    --cc=euguess@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.