Hello everyone, I'm a newbie.
I've got a problem while using find.
I know there is a way to do it in man find which is something like
find . -wholename './src/emacs' -prune -o -print
it works but i also want to use -daystart, -mtime, -type on it and i dont know whats the sequence of these... (0 Replies)
Hello,
I know find can be prevented from recursing into directories with something like the following...
find . -name .svn -prune -a type d
But how can I completely prevent directories of a certain name (.svn) from being displayed at all, the top level and the children?
I really... (2 Replies)
Hi,
I have to find specific files only in the current directory...not in the sub directories.
But when I use Find command ... it searches all the files in the current directory as well as in the subdirectories. I am using AIX-UNIX machine.Please help..
I am using the below command. And i am... (2 Replies)
Dear All,
I am using find command
find /my_rep/*/RKYPROOF/*/*/WDM/HOME_INT/PWD_DATA -name rk*myguidelines*.pdf -print
The problem i am facing here is find /my_rep/*/
the directory after my_rep could be mice001, mice002 and mice001_PO, mice002_PO
i want to ignore mice***_PO directory... (3 Replies)
i am trying to recursively save a remote FTP server but exclude the files immediately under a directory directory1
wget -r -N ftp://user:pass@hostname/directory1
I want to keep these which may have more files under them
directory1/dir1/file.jpg
directory1/dir2/file.jpg... (16 Replies)
In COBOL, a hyphen can be used in a field name and in a specific program some field names would be identical to others except a suffix was added--sometimes a suffix to a suffix was used. For example, assume I am looking for AAA, AAA-BBB, and AAA-BBB-CCC and don't want to look at AAA-BBB-CCC... (7 Replies)
Hi,
I am using following command to find a specific file.
find . -name "find*.txt" -type f -print
I am issuing that command at root directory since I don't know in which sub folder that file is getting created from some other process.
As I am not having access to all directories, my... (3 Replies)
Hi
i am really new to linux scripting and i need a little bit help.
i have the following script:
find "/usr/share/nextcloud/data/__groupfolders" -type f -mtime +14 -exec rm {} \;
but i don't want to delete everything. I want to ignore .txt files. How can i do this? (3 Replies)
Hello,
I have some code that works more or less. This is called by a make file to adjust some hard-coded definitions in the src code. The script generated some values by looking at some of the src files and then writes those values to specific locations in other files. The awk code is used to... (3 Replies)
I am running AIX 7.1 and currently we have samba 3.6.25 installed on the server. As it stands some AIX folders are shared that can be accessed by certain Windows users.
The problem is that since Windows 10 the guest feature no longer works so users have to manually type in their Windows login/pwd... (14 Replies)
Discussion started by: linuxsnake
14 Replies
LEARN ABOUT SUSE
git-pack-refs
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)