Hello,
I recently installed GIT 1.8.1 on my AIX 6.1 machine referring to AIX Open Source Packages | Main / git website and am facing a few issues with it.
Now if I login as root and issue git commands like git --version I get the response as shown : git version 1.8.1And I have tried creating... (4 Replies)
Hi,
I'm fairly new to the git command and I'm trying to figure out how to check if your local clone is up to date with the master. I know you can do the same thing on packages with apt-get by using update and then upgrade. Is there something similar with git? (0 Replies)
I meant to type in:
man git-add //no space
but I typed this in instead:
man git -add // space between git and -add
There were all these spewing out; not quite sure what I did. I am new to unix and the terminal. Does anyone know what man git -add does and how do I undo... (2 Replies)
I need to be able to run git commands on a solaris 10 box, the git server is a Linux rh 6.9 , but I can not find much info out there on a git client for solaris 10.
Is it just a pkgadd, or and install tar? or is there even any support for Solaris 10 git? My reading so far had not turned much up. ... (1 Reply)
i am running solaris 10 and they want GIt on there.
The instructions that I found on line want me to use pkgutil which i don't have either.
Most packages that i have installed come from the cd and are labeled SUNW...
I see one instruction to add
pkgadd -d http://get.opencsw.org/now
... (4 Replies)
Discussion started by: goya
4 Replies
LEARN ABOUT SUSE
git-lost-found
GIT-LOST-FOUND(1) Git Manual 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 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.
.ft C
$ git lost-found
[1ef2b196d909eed523d4f3c9bf54b78cdd6843c6] GIT 0.99.9c
...
.ft
Also you can use gitk to browse how any tags found relate to each other.
.ft C
$ gitk $(cd .git/lost-found/commit && echo ??*)
.ft
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.
.ft C
$ 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
.ft
AUTHOR
Written by Junio C Hamano <gitster@pobox.com[1]>
DOCUMENTATION
Documentation by Junio C Hamano and the git-list <git@vger.kernel.org[2]>.
GIT
Part of the git(1) suite
NOTES
1. gitster@pobox.com
mailto:gitster@pobox.com
2. git@vger.kernel.org
mailto:git@vger.kernel.org
Git 1.7.1 07/05/2010 GIT-LOST-FOUND(1)