Calender
Sun Mon Tue Wed Thu Fri Sat
 123456
78910111213
14151617181920
21222324252627
28293031   
<< May 2017 >>
広告
SEARCH

SELECTED ENTRIES
RECENT COMMENTS
RECENT TRACKBACK
CATEGORIES
ARCHIVES
LINKS
PROFILE
OTHERS
SKYPE
PC: skype.jojo.jp
chat
iPad: iphone.jojo.jp
chat call
THANKS



本日:
昨日:
多言語
広告
 ▼▲ 作業日報 ▼△
    What's under the hood?
<< named: initializing DST: openssl failure | main | PostgreSQL interval型のcast方法 >>
git で特定ファイルのみを追加
.gitignore で一旦全ファイルを否定しその後追加したいファイルを否定で記述
*.*
!*.php
!*.xml

gitignore仕様
.gitignoreファイルはgitに追跡しないファイルを指定します。追跡対象に関する設定であって、既にcommitされたファイルに関しては作用しない。
gitignoreファイルの各行には無視するパターンを指定。gitは無視するファイルを以下の優先順位で決定する.
・コマンドラインによる除外ファイル指定
・.gitignoreがサブフォルダにある場合はオーバーライドされる
・ $GIT_DIR/info/exclude ファイル
・設定変数 core.excludesfile で設定されたファイル
・空白行はなにもマッチしない
・#で始まる行はコメント
・接頭辞!は否定(即ちファイルを含むようになる)
・/で終る場合はディクトリとして扱われる
・/を含まない場合はglobパターンとして扱われる
・それ以外の場合はワイルドカード形式でマッチング(fnmatch)が行われる
 例:/aaa/*.html は /aaa/git.html はマッチするが、 /aaa/bbb/git.htmlはマッチしない
・先頭スラッシュは先頭パス名を意味する、例:/*.c は aaa.cにはマッチするが bbb/aaa.cにはマッチしない



GITIGNORE

Section: Git Manual (5)
Updated: 09/22/2011
Index Return to Main Contents
 

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. Note that all the gitignore files really concern only files that are not already tracked by git; in order to ignore uncommitted changes in already tracked files, please refer to the git update-index --assume-unchanged documentation.

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):

• Patterns read from the command line for those commands that support them.

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

• Patterns read from $GIT_DIR/info/exclude.

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

Patterns have the following format:

• A blank line matches no files, so it can serve as a separator for readability.

• A line starting with # serves as a comment.

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

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

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

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

• A leading slash matches the beginning of the pathname. For example, "/*.c" matches "cat-file.c" but not "mozilla-sha1/sha1.c".

An example:

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

DOCUMENTATION

Documentation by David Greaves, Junio C Hamano, Josh Triplett, Frank Lichtenheld, and the git-list <m[blue]git@vger.kernel.orgm[][1]>.  

GIT

Part of the git(1) suite  

NOTES

1.
git@vger.kernel.org
mailto:git@vger.kernel.org


 

Index

NAME
SYNOPSIS
DESCRIPTION
DOCUMENTATION
GIT
NOTES

| 開発関連 | 09:45 | comments(2) | trackbacks(0) |
管理者の承認待ちコメントです。
| - | 2013/05/31 8:18 PM |
管理者の承認待ちコメントです。
| - | 2013/05/31 8:19 PM |









http://blog.jojo.jp/trackback/1424912