Man git -add

Operating Systems OS X (Apple) Man git -add

Prev Next

04-14-2014

Registered User

8, 0

Join Date: Apr 2014

Last Activity: 1 May 2014, 12:26 AM EDT

Posts: 8

Thanks Given: 1

Thanked 0 Times in 0 Posts

Man git -add

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 something?

Thanks

BuDop

View Public Profile for BuDop

Find all posts by BuDop

Previous Thread | Next Thread

5 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

Git or PKGutil

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 ...

2. UNIX for Beginners Questions & Answers

Install git on UNIX

How can I install git on unix using wget?

3. Red Hat

Git command

trying to add git link to my computer as root and getting error message git clone https://github.com/xxxxxxx/xxxxx.sh bash: git: command not found Please use CODE tags as required by forum rules!

4. Solaris

Git Solaris

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. ...

5. Solaris

man and ldm man

According to Sun documentation (Ldoms 1.1 Administration Guide), To access the ldm(1M) man page, add the directory path /opt/SUNWldm/man to the variable $MANPATH. When I add the lines: MANPATH=$MANPATH:/opt/SUNWldm/man export MANPATH to .profile, exit root and re-login, I would have "man ldm"...

LEARN ABOUT OSX

git-prune

GIT-PRUNE(1)							    Git Manual							      GIT-PRUNE(1)

NAME

       git-prune - Prune all unreachable objects from the object database

SYNOPSIS

       git prune [-n] [-v] [--progress] [--expire <time>] [--] [<head>...]

DESCRIPTION

	   Note
	   In most cases, users should run git gc, which calls git prune. See the section "NOTES", below.

       This runs git fsck --unreachable using all the refs available in refs/, optionally with additional set of objects specified on the command
       line, and prunes all unpacked objects unreachable from any of these head objects from the object database. In addition, it prunes the
       unpacked objects that are also found in packs by running git prune-packed. It also removes entries from .git/shallow that are not reachable
       by any ref.

       Note that unreachable, packed objects will remain. If this is not desired, see git-repack(1).

OPTIONS

       -n, --dry-run
	   Do not remove anything; just report what it would remove.

       -v, --verbose
	   Report all removed objects.

       --progress
	   Show progress.

       --expire <time>
	   Only expire loose objects older than <time>.

       --
	   Do not interpret any more arguments as options.

       <head>...
	   In addition to objects reachable from any of our references, keep objects reachable from listed <head>s.

EXAMPLE

       To prune objects not used by your repository or another that borrows from your repository via its .git/objects/info/alternates:

	   $ git prune $(cd ../another && git rev-parse --all)

NOTES

       In most cases, users will not need to call git prune directly, but should instead call git gc, which handles pruning along with many other
       housekeeping tasks.

       For a description of which objects are considered for pruning, see git fsck's --unreachable option.

SEE ALSO

       git-fsck(1), git-gc(1), git-reflog(1)

GIT

       Part of the git(1) suite

Git 2.17.1							    10/05/2018							      GIT-PRUNE(1)

OS X (Apple)