mirror of
https://github.com/git/git.git
synced 2024-06-03 00:36:12 +02:00
48bb914ed6
The point of these sections is generally to:
1. Give credit where it is due.
2. Give the reader an idea of where to ask questions or
file bug reports.
But they don't do a good job of either case. For (1), they
are out of date and incomplete. A much more accurate answer
can be gotten through shortlog or blame. For (2), the
correct contact point is generally git@vger, and even if you
wanted to cc the contact point, the out-of-date and
incomplete fields mean you're likely sending to somebody
useless.
So let's drop the fields entirely from all manpages except
git(1) itself. We already point people to the mailing list
for bug reports there, and we can update the Authors section
to give credit to the major contributors and point to
shortlog and blame for more information.
Each page has a "This is part of git" footer, so people can
follow that to the main git manpage.
73 lines
1.7 KiB
Plaintext
73 lines
1.7 KiB
Plaintext
git-lost-found(1)
|
|
=================
|
|
|
|
NAME
|
|
----
|
|
git-lost-found - Recover lost refs that luckily have not yet been pruned
|
|
|
|
SYNOPSIS
|
|
--------
|
|
'git lost-found'
|
|
|
|
DESCRIPTION
|
|
-----------
|
|
|
|
*NOTE*: this command is deprecated. Use linkgit: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,
|
|
and other objects are stored in .git/lost-found/other.
|
|
|
|
|
|
OUTPUT
|
|
------
|
|
Prints to standard output the object names and one-line descriptions
|
|
of any commits or tags found.
|
|
|
|
EXAMPLE
|
|
-------
|
|
|
|
Suppose you run 'git tag -f' and mistype the tag to overwrite.
|
|
The ref to your tag is overwritten, but until you run 'git
|
|
prune', the tag itself is still there.
|
|
|
|
------------
|
|
$ git lost-found
|
|
[1ef2b196d909eed523d4f3c9bf54b78cdd6843c6] GIT 0.99.9c
|
|
...
|
|
------------
|
|
|
|
Also you can use gitk to browse how any tags found relate to each
|
|
other.
|
|
|
|
------------
|
|
$ gitk $(cd .git/lost-found/commit && echo ??*)
|
|
------------
|
|
|
|
After making sure you know which the object is the tag you are looking
|
|
for, you can reconnect it to your regular .git/refs hierarchy.
|
|
|
|
------------
|
|
$ git cat-file -t 1ef2b196
|
|
tag
|
|
$ git cat-file tag 1ef2b196
|
|
object fa41bbce8e38c67a218415de6cfa510c7e50032a
|
|
type commit
|
|
tag v0.99.9c
|
|
tagger Junio C Hamano <junkio@cox.net> 1131059594 -0800
|
|
|
|
GIT 0.99.9c
|
|
|
|
This contains the following changes from the "master" branch, since
|
|
...
|
|
$ git update-ref refs/tags/not-lost-anymore 1ef2b196
|
|
$ git rev-parse not-lost-anymore
|
|
1ef2b196d909eed523d4f3c9bf54b78cdd6843c6
|
|
------------
|
|
|
|
GIT
|
|
---
|
|
Part of the linkgit:git[1] suite
|