From: mkoegler@auto.tuwien.ac.at (Martin Koegler)
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: new GIT-VERSION-GEN with old GIT
Date: Sat, 23 Feb 2008 18:34:01 +0100 [thread overview]
Message-ID: <20080223173401.GA7808@auto.tuwien.ac.at> (raw)
On Debian, git 1.4.4 is still shipped in the stable distribution.
Since e5fc9a0aea2c3c49829b5cdf499339e5c759706b, simply running make in
a git checkout yields to an error message.
The error is in GIT-VERSION-GEN:
| + git diff-index --quiet HEAD
| usage: git-diff-index [-m] [--cached] [<common diff options>] <tree-ish> [<path>...]
| common diff options:
| -z output diff-raw with lines terminated with NUL.
| -p output patch format.
| -u synonym for -p.
| --patch-with-raw
| output both a patch and the diff-raw format.
| --stat show diffstat instead of patch.
| --numstat show numeric diffstat instead of patch.
| --patch-with-stat
| output a patch and prepend its diffstat.
| --name-only show only names of changed files.
| --name-status show names and status of changed files.
| --full-index show full object name on index lines.
| --abbrev=<n> abbreviate object names in diff-tree header and diff-raw.
| -R swap input file pairs.
| -B detect complete rewrites.
| -M detect renames.
| -C detect copies.
| --find-copies-harder
| try unchanged files as candidate for copy detection.
| -l<n> limit rename attempts up to <n> paths.
| -O<file> reorder diffs according to the <file>.
| -S<string> find filepair whose only one side contains the string.
| --pickaxe-all
| show all files diff when -S is used and hit is found.
| -a --text treat all files as text.
The problem is not critical, as the build process continues with wrong
version information.
mfg Martin Kögler
next reply other threads:[~2008-02-23 17:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-23 17:34 Martin Koegler [this message]
2008-02-23 18:46 ` new GIT-VERSION-GEN with old GIT 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080223173401.GA7808@auto.tuwien.ac.at \
--to=mkoegler@auto.tuwien.ac.at \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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 public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).