git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthieu Moy <matthieu.moy@grenoble-inp.fr>
To: Ed Avis <eda@waniasset.com>
Cc: git@vger.kernel.org
Subject: Re: git log --raw abbreviates SHA1s, despite what manual says
Date: Fri, 15 May 2015 17:42:51 +0200 (CEST)	[thread overview]
Message-ID: <297757279.1883703.1431704571028.JavaMail.zimbra@imag.fr> (raw)
In-Reply-To: <loom.20150515T171548-204@post.gmane.org>

----- Original Message -----
> Thanks for the explanation.  Plain 'git log' does not print any diffs.
> Does that mean that the --raw flag is a no-op in that case?

No, it displays the patch, in raw format. But you're right that the doc is unclear.

> Perhaps running 'git log --raw' should print a warning
> 
>     --raw given for raw-format diffs, but the output format you have chosen
>     does not include diffs.  Did you mean 'git log --format=raw'?

I'd rather fix the doc. Patch follows.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

  parent reply	other threads:[~2015-05-15 15:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15 14:46 git log --raw abbreviates SHA1s, despite what manual says Ed Avis
2015-05-15 15:08 ` Matthieu Moy
2015-05-15 15:22   ` Ed Avis
2015-05-15 15:33     ` Ed Avis
2015-05-15 15:42     ` Matthieu Moy [this message]
2015-05-15 15:44       ` [PATCH] Documentation/log: clarify what --raw means Matthieu Moy
2015-05-15 15:47         ` Ed Avis
2015-05-15 17:44           ` Junio C Hamano
2015-05-15 17:29         ` Eric Sunshine
2015-05-15 17:38         ` Junio C Hamano
2015-05-18 17:51           ` Matthieu Moy
2015-05-18 17:55           ` [PATCH v2 1/2] " Matthieu Moy
2015-05-18 17:55             ` [PATCH v2 2/2] Documentation/log: clarify sha1 non-abbreviation in log --raw Matthieu Moy
2015-05-18 20:52               ` Junio C Hamano
2015-05-18 21:28                 ` Matthieu Moy
2015-05-18 22:29                   ` Junio C Hamano

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=297757279.1883703.1431704571028.JavaMail.zimbra@imag.fr \
    --to=matthieu.moy@grenoble-inp.fr \
    --cc=eda@waniasset.com \
    --cc=git@vger.kernel.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).