From: Miklos Vajna <vmiklos@frugalware.org>
To: "H.Merijn Brand" <h.m.brand@xs4all.nl>
Cc: Lars Noschinski <lars-2008-1@usenet.noschinski.de>, git@vger.kernel.org
Subject: Re: Feature suggestion: git-hist
Date: Wed, 30 Jul 2008 16:55:34 +0200 [thread overview]
Message-ID: <20080730145534.GD32057@genesis.frugalware.org> (raw)
In-Reply-To: <20080730155835.71289eee@pc09.procura.nl>
[-- Attachment #1: Type: text/plain, Size: 631 bytes --]
On Wed, Jul 30, 2008 at 03:58:35PM +0200, "H.Merijn Brand" <h.m.brand@xs4all.nl> wrote:
> We are not used to working with $SHA's, and IMHO from the end-user pov,
> a $SHA is less user friendly than a release number or a file version. I
> can remember a version, but I cannot remember a SHA.
But a version is never unique in a distributed environment. So a version
is useless without at least an abbreviated hash.
If pure hashes are not friendly enough, you can use something like:
git describe $(git rev-list -1 HEAD -- <file>)
to get the _hash_ of the _commit_ (ie. not the version of a file) that
touched the file last time.
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-07-30 14:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 11:38 Feature suggestion: git-hist H.Merijn Brand
2008-07-30 12:03 ` Pieter de Bie
2008-07-30 12:14 ` H.Merijn Brand
2008-07-30 13:33 ` Lars Noschinski
2008-07-30 13:58 ` H.Merijn Brand
2008-07-30 14:55 ` Miklos Vajna [this message]
2008-07-30 15:03 ` H.Merijn Brand
2008-07-30 15:23 ` Santi Béjar
2008-07-30 15:58 ` Avery Pennarun
2008-07-30 16:34 ` Lars Noschinski
2008-07-30 15:18 ` Santi Béjar
2008-07-30 15:29 ` H.Merijn Brand
[not found] ` <FA2D570A-B2B1-4994-AA6A-9C0C55E69900@silverinsanity.com>
2008-07-30 16:26 ` Merging submodules (was Re: Feature suggestion: git-hist) H.Merijn Brand
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=20080730145534.GD32057@genesis.frugalware.org \
--to=vmiklos@frugalware.org \
--cc=git@vger.kernel.org \
--cc=h.m.brand@xs4all.nl \
--cc=lars-2008-1@usenet.noschinski.de \
/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).