Sponsored Content
Full Discussion: Extended man pages
Contact Us Post Here to Contact Site Administrators and Moderators Extended man pages Post 302402397 by Corona688 on Tuesday 9th of March 2010 06:35:26 PM
Old 03-09-2010
I think I get it -- he wants to be able to 'reply' to the manpages with howtos and tips.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Man pages

Hello , I just installed openssh in my system . I actually tried to man sshd but it says no entry , though there is a man directory in the installation which have the man pages for sshd . Can anyone tell me how should i install these man pages . DP (2 Replies)
Discussion started by: DPAI
2 Replies

2. UNIX for Dummies Questions & Answers

man pages

Hi, I've written now a man pages, but I don't knwo how to get 'man' to view them. Where have I to put this files, which directories are allowed?? THX Bensky (3 Replies)
Discussion started by: bensky
3 Replies

3. UNIX for Dummies Questions & Answers

man pages

Hi folks, I want to know all the commands for which man pages are available. How do i get it? Cheers, Nisha (4 Replies)
Discussion started by: Nisha
4 Replies

4. UNIX for Dummies Questions & Answers

man pages

When reading man pages, I notice that sometimes commands are follwed by a number enclosed in parenthesis. such as: mkdir calls the mkdir(2) system call. What exactly does this mean? (4 Replies)
Discussion started by: dangral
4 Replies

5. UNIX for Advanced & Expert Users

Openssl Man pages

I have found a few of the openssl commands but there are loads missing and I can't find them anywhere. Eg -inkey -in -A what do all these do?????? Does anyone know where there is a definitive list of Openssl commands?? If so please let me know.. Thanks. (1 Reply)
Discussion started by: gwoodhouse
1 Replies

6. UNIX for Dummies Questions & Answers

how to read man pages

can anybody explain me how to read unix man pages? for example when i want to get information about ps command man ps gives me this output: *********************************** Reformatting page. Please wait... completed ps(1) ... (2 Replies)
Discussion started by: gfhgfnhhn
2 Replies

7. Solaris

MAN PAGES

Hi everyone, I have a small query, in solaris the man pages get displayed on half of the terminal , can i get a full terminal or full screen display ?:) (2 Replies)
Discussion started by: M.Choudhury
2 Replies

8. HP-UX

Looking for some man pages.

Can anyone supply me with the man pages for: omnidatalist omnibarlist omnisap.exe I prefer the source man pages in nroff format. A clue about the software bundles which supply these man pages is fine as well. OS: HP-UX TIA (11 Replies)
Discussion started by: sb008
11 Replies

9. Shell Programming and Scripting

Man pages for Pthreads

"how to see the man pages related to pthreads". while executing the command man pthread_t . im getting the following error!!!!! No manual entry for pthread. (3 Replies)
Discussion started by: Muthukumar U
3 Replies

10. UNIX for Beginners Questions & Answers

Listing certain man pages

How would I go about making a list of all man pages beginning with the letter "a"? I have tried: man a* man * man man {a}* man {a*} man "a*" man 'a'* man 'a*' (5 Replies)
Discussion started by: Xubuntu56
5 Replies
GIT-PACK-REFS(1)						    Git Manual							  GIT-PACK-REFS(1)

NAME
git-pack-refs - Pack heads and tags for efficient repository access SYNOPSIS
git pack-refs [--all] [--no-prune] DESCRIPTION
Traditionally, tips of branches and tags (collectively known as refs) were stored one file per ref under $GIT_DIR/refs directory. While many branch tips tend to be updated often, most tags and some branch tips are never updated. When a repository has hundreds or thousands of tags, this one-file-per-ref format both wastes storage and hurts performance. This command is used to solve the storage and performance problem by stashing the refs in a single file, $GIT_DIR/packed-refs. When a ref is missing from the traditional $GIT_DIR/refs hierarchy, it is looked up in this file and used if found. Subsequent updates to branches always create new files under $GIT_DIR/refs hierarchy. A recommended practice to deal with a repository with too many refs is to pack its refs with --all --prune once, and occasionally run git pack-refs --prune. Tags are by definition stationary and are not expected to change. Branch heads will be packed with the initial pack-refs --all, but only the currently active branch heads will become unpacked, and the next pack-refs (without --all) will leave them unpacked. OPTIONS
--all The command by default packs all tags and refs that are already packed, and leaves other refs alone. This is because branches are expected to be actively developed and packing their tips does not help performance. This option causes branch tips to be packed as well. Useful for a repository with many branches of historical interests. --no-prune The command usually removes loose refs under $GIT_DIR/refs hierarchy after packing them. This option tells it not to. AUTHOR
Written by Linus Torvalds <torvalds@osdl.org[1]> GIT
Part of the git(1) suite NOTES
1. torvalds@osdl.org mailto:torvalds@osdl.org Git 1.7.1 07/05/2010 GIT-PACK-REFS(1)
All times are GMT -4. The time now is 04:41 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy