From: "Eric S. Raymond" <esr@thyrsus.com>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Tag cleanup
Date: Thu, 9 Jan 2014 08:49:22 -0500 [thread overview]
Message-ID: <20140109134922.GB6290@thyrsus.com> (raw)
In-Reply-To: <21198.42266.904937.585396@a1i15.kph.uni-mainz.de>
Ulrich Mueller <ulm@gentoo.org>:
> In Gentoo, we have a "live" ebuild for Emacs that fetches from the
> upstream VCS repository. When fetching from git, we use shallow clones
> by default, because history is not interesting for this use case.
>
> Obtaining the raw SHA1 (with "git rev-parse HEAD" or similar) will
> still work for shallow clones, while "git describe" won't.
>
> There's a related downstream bug: https://bugs.gentoo.org/489100
> Quoting from there: "Is this really worth non-shallow fetches? We're
> talking about increasing overhead seriously for the sake of pretty
> version string." I'm passing this question on to you. ;-)
>
> Ulrich
Thank you. I consider that this resolves the describe-vs.-SHA1 question.
Not in a way that I like, mind you, but that's life.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
next prev parent reply other threads:[~2014-01-09 13:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 5:37 Tag cleanup Eric S. Raymond
2014-01-09 7:00 ` Eli Zaretskii
2014-01-09 8:13 ` Thien-Thi Nguyen
2014-01-09 11:24 ` Eric S. Raymond
2014-01-09 13:33 ` Ulrich Mueller
2014-01-09 13:49 ` Eric S. Raymond [this message]
2014-01-09 8:44 ` Yuri Khan
2014-01-09 11:26 ` Eric S. Raymond
2014-01-09 16:58 ` Glenn Morris
2014-01-09 17:00 ` Glenn Morris
-- strict thread matches above, loose matches on Subject: below --
2014-01-10 20:06 Eric S. Raymond
2014-01-10 20:23 ` Eli Zaretskii
2014-01-10 21:36 ` Andreas Schwab
2014-01-10 21:41 ` Eric S. Raymond
2014-01-10 22:09 ` Andreas Schwab
2014-01-11 19:40 ` Alan Mackenzie
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=20140109134922.GB6290@thyrsus.com \
--to=esr@thyrsus.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=ulm@gentoo.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.