Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!storethat.news.telefonica.de!telefonica.de!news-1.dfn.de!news.dfn.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "J.O. Aho" Newsgroups: comp.lang.php Subject: Re: Git (Was: can't get includes to load) Date: Sun, 31 Mar 2013 11:54:02 +0200 Lines: 118 Message-ID: References: <3bednVqnL5qAhc_MnZ2dnUVZ_q6dnZ2d@supernews.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net bVNkPCYS13eUU2ZSXV2bkwYDCZcXM5Yf0AgHy2/y3rBTKT4XrI Cancel-Lock: sha1:vvUJE+kvGhSRfBzu4IFjqvPipEY= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130326 Thunderbird/17.0.4 In-Reply-To: Xref: csiph.com comp.lang.php:8929 On 31/03/13 09:31, Cal Dershowitz wrote: > On 03/29/2013 05:14 AM, J.O. Aho wrote: > >> >> "ls -l" will not show it, as it's a hidden directory, you need to use >> "ls -la", where the "a" is all. >> > > Geez, thx JO, I think I'm in the clear on this now. This was a tough > thread for me in that the -a meant completely different things as a > modifcation to git as opposed to ls. I do kep my "learning experiences > journaled, tho. They show up as git1.txt. That's not a file that needs > to be committed to git because it's me pasting my litany of > mistakes/learning to it, and it isn't in any way executable. >> This shows you created the git repository, before you can commit >> something, you need to add the files you want to track. >> >> git add index.php includes readme.txt style.css >> >> and then you can make the commit. >> >> Remember I told earlier in this thread that the 'git commit -m >> "something" -a' only works on files you already are tracking of, in an >> empty git repository you ain't tracking anything, those you need to add >> files with "git add". >> >> >> Please read this page: >> http://refcardz.dzone.com/refcardz/getting-started-git >> >> If you want more in depth video: >> http://excess.org/article/2008/07/ogre-git-tutorial >> > $ ls -la > total 36 > drwxr-xr-x 4 fred automation 4096 Mar 29 00:09 . > drwxr-xr-x 3 fred automation 4096 Mar 28 00:18 .. > drwxr-xr-x 7 fred automation 4096 Mar 29 00:09 .git > -rw-r--r-- 1 fred automation 1947 Mar 29 00:08 git1.txt > -rw-r--r-- 1 fred automation 1902 Mar 29 00:07 git1.txt~ > drwxr-xr-x 2 fred automation 4096 Mar 27 23:44 includes > -rw-r--r-- 1 fred automation 2208 Mar 26 14:36 index.php > -rw-r--r-- 1 fred automation 4 Mar 28 00:23 readme.txt > -rw-r--r-- 1 fred automation 0 Mar 28 00:23 readme.txt~ > -rwxr-xr-x 1 fred automation 896 Mar 25 21:49 style.css > $ git add index.php > $ git status > # On branch master > # > # Initial commit > # > # Changes to be committed: > # (use "git rm --cached ..." to unstage) > # > # new file: index.php > # > # Untracked files: > # (use "git add ..." to include in what will be committed) > # > # git1.txt > # git1.txt~ > # includes/ > # readme.txt > # readme.txt~ > # style.css > $ git add includes > $ git status > # On branch master > # > # Initial commit > # > # Changes to be committed: > # (use "git rm --cached ..." to unstage) > # > # new file: includes/footer.php > # new file: includes/header.php > # new file: includes/nav.php > # new file: includes/sidebar.php > # new file: index.php > # > # Untracked files: > # (use "git add ..." to include in what will be committed) > # > # git1.txt > # git1.txt~ > # readme.txt > # readme.txt~ > # style.css > $ > > Outstanding! so boom, all the files in includes are "gotten." They are tracked, they are not stored in the repository, to store them in the repository you need to make a commit, for example: git commit -m "initial commit of website design" -a when you done that, a copy will be stored of the files and if you make changes to the files and you want to restore it for the changes was no good, then you can checkout them again. As long as they are just added, you don't have that feature. > Do I really want to have only one .css file for the whole site? The more files you divide things up in (from the point of view of the web browser), the slower the page will be, try to have everything that you use in all your pages in one single css and if you have styles which you use only a few times in a rarely used page, then you can split those out. I do recommend you install firebug and yslow and you will get good information how to improve the speed of your web page. -- //Aho