07-10-2008
You could do something like
find . ! -path . -prune -a -type f -newer etc...
Do you know of a more elegant way to prune the search? I find this one a little sloppy.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I need to move a bunch of files into folders that have the same name. I wanted to either do this with some filter command or some type of batch file that I could save that would already include all of the mv commands since I will have to do this process often. Whatever method you think is easier.
... (7 Replies)
Discussion started by: italia5
7 Replies
2. UNIX for Dummies Questions & Answers
I have a directory which has crores of files since from 2003. I want to move only the 2003 files to another directory. Please help in doing this.
Thanks (1 Reply)
Discussion started by: IHK
1 Replies
3. Shell Programming and Scripting
Hi All,
I have a directory which has crores of files since from 2003 till now. I want to move only the 2003 files to another directory. Please help.
Thanks (2 Replies)
Discussion started by: IHK
2 Replies
4. Red Hat
Hi all,
I have a massive amount of recording files in .WAV format stored in a directory, files dating back to 2006.
It is a huge amount of files as Linux cannot even do a listing of it all, it states: "argument list too long"
What I would like to do is the following:
Find all the files of... (6 Replies)
Discussion started by: codenjanod
6 Replies
5. Shell Programming and Scripting
I know this gets covered quite a bit in the forum and I think there is enough there for me to figure out how to do what I am trying to do, I just don't think I would do it very efficiently so I am going to ask the question...
I have database log files with date and time stamps in the file like
... (7 Replies)
Discussion started by: slatoms
7 Replies
6. Shell Programming and Scripting
Hi folks,
I'm new here and appreciate greatly any help.
I have a bunch of files that need be moved and renamed. Fortunately, they are all in sequence...
Present filename and path: /.catalog1/t76038_842-01
Move to: /.catalog1/76038-01
So, we need to drop the... (8 Replies)
Discussion started by: axslinger
8 Replies
7. Shell Programming and Scripting
Hi Folks,
I have different type of file in my current directory. From my current directory i need to move the file which is start with csp_rules and if the file is having the string payg , then I need to move all this files to another directory /output/record. Please help me how to do this?
... (3 Replies)
Discussion started by: suresh01_apk
3 Replies
8. Shell Programming and Scripting
Hi All,
I have 2 LINUX scripts (Lets say ScriptA & ScriptB) which copies files (lets say 'date_abc.txt , it goes to a while loop & checks for the files between 2 date varialbles) to directory X. (as Shown Below)
These 2 scripts are called from 2 different Autosys schedules & runs at the... (3 Replies)
Discussion started by: dsfreddie
3 Replies
9. Shell Programming and Scripting
Hi UNIX Experts,
Kindly help me in this requirement where i want to move files based on its status.
For Eg:
I have 3 dir's
--FileBox Dir
this directory will have all the files which i need to process (in informatica ETL Tool)
--Succeeded Dir
this directory will have files which... (4 Replies)
Discussion started by: kumarinfa
4 Replies
10. Shell Programming and Scripting
Hello,
First time poster. I am looking for a way to script or program the process of moving files from one folder to another, automatically, based on the count of files in the destination folder.
I was thinking a shell script would work, but am open to the suggestions of the experts... (6 Replies)
Discussion started by: comtech
6 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)