From: Pat Notz <patnotz@gmail.com>
To: "David Kågedal" <davidk@lysator.liu.se>
Cc: git@vger.kernel.org
Subject: Re: Output from git diff
Date: Wed, 29 Jul 2009 11:29:02 -0600 [thread overview]
Message-ID: <1cd1989b0907291029r2efd78br3506ded03dedf438@mail.gmail.com> (raw)
In-Reply-To: <873a8fflt2.fsf@krank.kagedal.org>
On Wed, Jul 29, 2009 at 11:20 AM, David Kågedal<davidk@lysator.liu.se> wrote:
> Here is another diff output question. The updated documentation in
> diff-format.txt still claims that the output from the diff commands
> has this format:
>
> :100644 100644 bcd1234... 0123456... M file0
>
> This is true for "git diff --raw", but diff-tree and friends print
> full 40-char hashes.
>
> I can get diff-tree to use abbreviated hashes with --abbrev, but how
> do I tell diff to stop abbreviating?
Probably not the answer you *really* want but 'git diff --raw
--abbrev=40' will give you the full sha1
>
> And what should the documentation really say?
>
> --
> David Kågedal
>
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2009-07-29 17:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 19:54 Output from git diff-tree (documentation) David Kågedal
2009-07-27 21:03 ` Junio C Hamano
[not found] ` <87vdld9694.fsf@krank.kagedal.org>
[not found] ` <87prbl8ay5.fsf_-_@krank.kagedal.org>
2009-07-28 20:34 ` [PATCH] Update the documentation of the raw diff output format Junio C Hamano
2009-07-29 6:11 ` David Kågedal
2009-07-29 17:20 ` Output from git diff David Kågedal
2009-07-29 17:29 ` Pat Notz [this message]
2009-07-29 18:26 ` Junio C Hamano
[not found] ` <87y6q6ehx8.fsf@krank.kagedal.org>
2009-07-30 8:06 ` 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=1cd1989b0907291029r2efd78br3506ded03dedf438@mail.gmail.com \
--to=patnotz@gmail.com \
--cc=davidk@lysator.liu.se \
--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).