All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Ed Avis <eda@waniasset.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documentation/log: clarify what --raw means
Date: Fri, 15 May 2015 10:44:46 -0700	[thread overview]
Message-ID: <xmqqpp61hh0x.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <loom.20150515T174530-547@post.gmane.org> (Ed Avis's message of "Fri, 15 May 2015 15:47:24 +0000 (UTC)")

Ed Avis <eda@waniasset.com> writes:

> Thanks, I think that is a bit clearer.
>
> You might also need to clarify the part about --format=raw where it says
> 'SHA-1s are displayed in full, regardless of whether --abbrev or --no-abbrev'.

This part of the description being "--format" option, the "SHA-1s"
the description refers to are the ones that appear in the commit
object itself, something like:

    tree 2b5bfdf7798569e0b59b16eb9602d5fa572d6038
    author Linus Torvalds <torvalds@ppc970.osdl.org> 1112911993 -0700
    committer Linus Torvalds <torvalds@ppc970.osdl.org> 1112911993 -0700

    Initial revision of "git", the information manager from hell

And the commit object itself does not have any "diff", as you are
not comparing anything with any other thing.  It is about recording
one single state in time.

I think that is what the reader needs to be made aware of, and the
current documentation is not doing a good job at it.

  reply	other threads:[~2015-05-15 17:44 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
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 [this message]
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=xmqqpp61hh0x.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --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 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.