10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello.
For a given folder, I want to select any files find $PATH1 -f \( -name "*" but omit any files like pattern name ! -iname "*.jpg" ! -iname "*.xsession*" ..... \) and also omit any subfolder like pattern name -type d \( -name "/etc/gconf/gconf.*" -o -name "*cache*" -o -name "*Cache*" -o... (2 Replies)
Discussion started by: jcdole
2 Replies
2. Shell Programming and Scripting
Hi,
I am trying to extract some patterns from a line. The input file is space delimited and i could not use column to get value after "IN" or "OUT" patterns as there could be multiple white spaces before the next digits that i need to print in the output file . I need to print 3 patterns in a... (3 Replies)
Discussion started by: redse171
3 Replies
3. UNIX for Dummies Questions & Answers
Hi I'm trying to get all files from a directory with a script. So i'm gone paste my script here:
cd /var/www/match_demos/speedgaming/
lftp -u Gudfaren,xxxxx ftp.speedgaming.pro -e cd 89.221.243.11_27500 -e mget *.dem
exit
when i run that i get:
"File name missed. Try `help mget' for more... (2 Replies)
Discussion started by: vYN
2 Replies
4. AIX
Hi,
below are the commands I use to get many gif files from /usr/local/images directory, the command just getting stuck at mget, nothing is moving
cd /usr/local/images
binary
mget *.gif:wall:
close
quit (3 Replies)
Discussion started by: dateez
3 Replies
5. Shell Programming and Scripting
Hi guys...Wow I just composed a huge post and it got erased as I was logged out automatically
Anyways I hope someone can help me out here.
So the task I'm working on is like this
I have a bunch of files that I care about sitting in a directory say $HOME/files
Now my job is to go and loop... (6 Replies)
Discussion started by: rukasetsuna
6 Replies
6. UNIX for Dummies Questions & Answers
This should be somewhat simple, but I need some help with this one.
I have a bunch of files with tags on the end like so...
Filename {tag1}.ext
Filename2 {tag1} {tag2}.ext
I want to hold in a variable just the filename with all the " {tag}" removed. The tag can be anything so I'm looking... (4 Replies)
Discussion started by: kerppz
4 Replies
7. Shell Programming and Scripting
Hi Gurus,
I have a file say for ex. file1 which has 3500 lines in it which are different account numbers and another file (file2) which has 230000 lines in it. I want to read all the lines in file1 and delete all those lines from file2 which has that same pattern as in file1. I am not quite... (4 Replies)
Discussion started by: toms
4 Replies
8. Shell Programming and Scripting
Hi All,
I am using mget (mget server.*) through ftp... ... i dont want to overwrite the files in my localmachine if it is already exists... is it possible through ftp ?? any other optios also mos t welcome
Thnks in advance (4 Replies)
Discussion started by: scorpio
4 Replies
9. UNIX for Dummies Questions & Answers
hello,
i was interested in knowing if you can mget or mput a sequence of files:
example- say i have a dir with 1000 files with the same extension e.g. *.sgi,
is there a way to mget only the last 200 files?
i would assume that there is a flag i would use, or something like:
mget... (14 Replies)
Discussion started by: yoyomamma
14 Replies
10. UNIX for Dummies Questions & Answers
hi, i want to mget a directory.
how to specify the flag that i dont want the system to prompt me?
thanks (2 Replies)
Discussion started by: yls177
2 Replies
GITIGNORE(5) Git Manual GITIGNORE(5)
NAME
gitignore - Specifies intentionally untracked files to ignore
SYNOPSIS
$GIT_DIR/info/exclude, .gitignore
DESCRIPTION
A gitignore file specifies intentionally untracked files that git should ignore. Files already tracked by git are not affected; see the
NOTES below for details.
Each line in a gitignore file specifies a pattern. When deciding whether to ignore a path, git normally checks gitignore patterns from
multiple sources, with the following order of precedence, from highest to lowest (within one level of precedence, the last matching pattern
decides the outcome):
o Patterns read from the command line for those commands that support them.
o Patterns read from a .gitignore file in the same directory as the path, or in any parent directory, with patterns in the higher level
files (up to the toplevel of the work tree) being overridden by those in lower level files down to the directory containing the file.
These patterns match relative to the location of the .gitignore file. A project normally includes such .gitignore files in its
repository, containing patterns for files generated as part of the project build.
o Patterns read from $GIT_DIR/info/exclude.
o Patterns read from the file specified by the configuration variable core.excludesfile.
Which file to place a pattern in depends on how the pattern is meant to be used. Patterns which should be version-controlled and
distributed to other repositories via clone (i.e., files that all developers will want to ignore) should go into a .gitignore file.
Patterns which are specific to a particular repository but which do not need to be shared with other related repositories (e.g., auxiliary
files that live inside the repository but are specific to one user's workflow) should go into the $GIT_DIR/info/exclude file. Patterns
which a user wants git to ignore in all situations (e.g., backup or temporary files generated by the user's editor of choice) generally go
into a file specified by core.excludesfile in the user's ~/.gitconfig.
The underlying git plumbing tools, such as git ls-files and git read-tree, read gitignore patterns specified by command-line options, or
from files specified by command-line options. Higher-level git tools, such as git status and git add, use patterns from the sources
specified above.
PATTERN FORMAT
o A blank line matches no files, so it can serve as a separator for readability.
o A line starting with # serves as a comment.
o An optional prefix ! which negates the pattern; any matching file excluded by a previous pattern will become included again. If a
negated pattern matches, this will override lower precedence patterns sources.
o If the pattern ends with a slash, it is removed for the purpose of the following description, but it would only find a match with a
directory. In other words, foo/ will match a directory foo and paths underneath it, but will not match a regular file or a symbolic
link foo (this is consistent with the way how pathspec works in general in git).
o If the pattern does not contain a slash /, git treats it as a shell glob pattern and checks for a match against the pathname relative
to the location of the .gitignore file (relative to the toplevel of the work tree if not from a .gitignore file).
o Otherwise, git treats the pattern as a shell glob suitable for consumption by fnmatch(3) with the FNM_PATHNAME flag: wildcards in the
pattern will not match a / in the pathname. For example, "Documentation/*.html" matches "Documentation/git.html" but not
"Documentation/ppc/ppc.html" or "tools/perf/Documentation/perf.html".
o A leading slash matches the beginning of the pathname. For example, "/*.c" matches "cat-file.c" but not "mozilla-sha1/sha1.c".
NOTES
The purpose of gitignore files is to ensure that certain files not tracked by git remain untracked.
To ignore uncommitted changes in a file that is already tracked, use git update-index --assume-unchanged.
To stop tracking a file that is currently tracked, use git rm --cached.
EXAMPLES
$ git status
[...]
# Untracked files:
[...]
# Documentation/foo.html
# Documentation/gitignore.html
# file.o
# lib.a
# src/internal.o
[...]
$ cat .git/info/exclude
# ignore objects and archives, anywhere in the tree.
*.[oa]
$ cat Documentation/.gitignore
# ignore generated html files,
*.html
# except foo.html which is maintained by hand
!foo.html
$ git status
[...]
# Untracked files:
[...]
# Documentation/foo.html
[...]
Another example:
$ cat .gitignore
vmlinux*
$ ls arch/foo/kernel/vm*
arch/foo/kernel/vmlinux.lds.S
$ echo '!/vmlinux*' >arch/foo/kernel/.gitignore
The second .gitignore prevents git from ignoring arch/foo/kernel/vmlinux.lds.S.
SEE ALSO
git-rm(1), git-update-index(1), gitrepository-layout(5)
GIT
Part of the git(1) suite
Git 1.7.10.4 11/24/2012 GITIGNORE(5)