From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: [PATCH v2] Deprecate git-lost-found
Date: Thu, 8 Nov 2007 00:41:22 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0711080041120.4362@racer.site> (raw)
In-Reply-To: <7vlk998u6r.fsf@gitster.siamese.dyndns.org>
"git fsck" learnt the option "--lost-found" in v1.5.3-rc0~5, to make
"git lost-found" obsolete. It is time to deprecate "git lost-found".
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
---
Documentation/RelNotes-1.5.4.txt | 3 +++
Documentation/git-lost-found.txt | 4 ++++
git-lost-found.sh | 2 ++
3 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/Documentation/RelNotes-1.5.4.txt b/Documentation/RelNotes-1.5.4.txt
index 133fa64..65dd1b0 100644
--- a/Documentation/RelNotes-1.5.4.txt
+++ b/Documentation/RelNotes-1.5.4.txt
@@ -46,6 +46,9 @@ Updates since v1.5.3
* Various Perforce importer updates.
+ * git-lost-found was deprecated in favor of git-fsck's --lost-found
+ option.
+
Fixes since v1.5.3
------------------
diff --git a/Documentation/git-lost-found.txt b/Documentation/git-lost-found.txt
index bc73911..7f808fc 100644
--- a/Documentation/git-lost-found.txt
+++ b/Documentation/git-lost-found.txt
@@ -11,6 +11,10 @@ SYNOPSIS
DESCRIPTION
-----------
+
+*NOTE*: this command is deprecated. Use gitlink:git-fsck[1] with
+the option '--lost-found' instead.
+
Finds dangling commits and tags from the object database, and
creates refs to them in the .git/lost-found/ directory. Commits and
tags that dereference to commits are stored in .git/lost-found/commit,
diff --git a/git-lost-found.sh b/git-lost-found.sh
index a5a32e7..9cedaf8 100755
--- a/git-lost-found.sh
+++ b/git-lost-found.sh
@@ -5,6 +5,8 @@ SUBDIRECTORY_OK='Yes'
OPTIONS_SPEC=
. git-sh-setup
+echo "WARNING: '$0' is deprecated in favor of 'git fsck --lost-found'" >&2
+
if [ "$#" != "0" ]
then
usage
--
1.5.3.5.1597.g7191
next prev parent reply other threads:[~2007-11-08 0:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 22:54 [PATCH] Deprecate git-lost-found Johannes Schindelin
2007-11-08 0:19 ` Junio C Hamano
2007-11-08 0:37 ` Johannes Schindelin
2007-11-08 0:41 ` Johannes Schindelin [this message]
2007-11-08 14:54 ` [PATCH] Remove deprecated commands from command list and update manpages Jonas Fonseca
2007-11-08 15:00 ` Andreas Ericsson
2007-11-08 16:01 ` [PATCH] Drop deprecated commands from git(7) and update deprecation notices Jonas Fonseca
2007-11-08 21:01 ` Junio C Hamano
2007-11-09 0:20 ` [PATCH] Remove non-existing commands from git(7) and delete their manpages Jonas Fonseca
2007-11-09 1:21 ` [PATCH 1/3] Documentation: lost-found is now deprecated Junio C Hamano
2007-11-09 1:27 ` Jonas Fonseca
2007-11-09 1:34 ` Junio C Hamano
2007-11-09 1:22 ` [PATCH 3/3] Documentation: remove documentation for removed tools Junio C Hamano
2007-11-12 0:24 ` [PATCH] Documentation: Fix references to deprecated commands Jonas Fonseca
2007-11-12 0:32 ` Jonas Fonseca
2007-11-12 8:22 ` Junio C Hamano
2007-11-12 9:37 ` Jonas Fonseca
2007-11-19 1:54 ` J. Bruce Fields
2007-11-19 7:44 ` Jonas Fonseca
2007-11-09 2:38 ` [PATCH 2/3] Make check-docs target detect removed commands Junio C Hamano
2007-11-08 15:18 ` [PATCH] Remove deprecated commands from command list and update manpages Johannes Schindelin
2007-11-08 15:19 ` Johannes Schindelin
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=Pine.LNX.4.64.0711080041120.4362@racer.site \
--to=johannes.schindelin@gmx.de \
--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.
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).