Skip to content

Commit

Permalink
Deprecate git-lost-found
Browse files Browse the repository at this point in the history
"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>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
  • Loading branch information
Johannes Schindelin authored and Junio C Hamano committed Nov 8, 2007
1 parent e7509ee commit fc8b5f0
Show file tree
Hide file tree
Showing 3 changed files with 9 additions and 0 deletions.
3 changes: 3 additions & 0 deletions Documentation/RelNotes-1.5.4.txt
Original file line number Diff line number Diff line change
Expand Up @@ -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
------------------

Expand Down
4 changes: 4 additions & 0 deletions Documentation/git-lost-found.txt
Original file line number Diff line number Diff line change
Expand Up @@ -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,
Expand Down
2 changes: 2 additions & 0 deletions git-lost-found.sh
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,8 @@ USAGE=''
SUBDIRECTORY_OK='Yes'
. git-sh-setup

echo "WARNING: '$0' is deprecated in favor of 'git fsck --lost-found'" >&2

if [ "$#" != "0" ]
then
usage
Expand Down

0 comments on commit fc8b5f0

Please sign in to comment.