On Tuesday, March 11, 2014 2:01:49 AM UTC-3, rusi wrote:
>
> $HOME/.config/git/ignore, $GIT_DIR/info/exclude, .gitignore
>
+1 to *.git/info/exclude*
This was the better solution I've found to ignore thing that only I use.
--
You received this message because you are subscribed to the Google Gr
On Tue, Mar 11, 2014 at 2:50 AM, rhugga wrote:
>
> So .gitignore is used to hide certain file types which is great. But how do
> you have it ignore the file itself?
>
> I put .gitignore in the file itself and that works but seems more like a
> work around than as intended.
The reasons and explana
> From: Chuck
> Putting .gitignore inside the file itself doesn't negate it's behavior.
> Just seems like something that should be built in because a) no one wants
> to see this listed as an untracked file and b) no one wants this included
> in their actual project repository.
The primary purpos
from
the binaries into different vaults.
Philip
- Original Message -
From: Chuck
To: git-users@googlegroups.com
Sent: Monday, March 10, 2014 9:33 PM
Subject: Re: [git-users] Question about .gitignore
This is why:
# git status
On branch master
Initial commit
Cha
On 10/03/2014 21:33, Chuck wrote:
>
> Putting .gitignore inside the file itself doesn't negate it's behavior.
> Just seems like something that should be built in because a) no one
> wants to see this listed as an untracked file and b) no one wants this
> included in their actual project repositor
This is why:
# git status
On branch master
Initial commit
Changes to be committed:
(use "git rm --cached ..." to unstage)
new file: myscript.sh
Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git checkout -- ..." to discard changes in worki
On 10/03/2014 21:20, rhugga wrote:
>
> So .gitignore is used to hide certain file types which is great. But how
> do you have it ignore the file itself?
>
> I put .gitignore in the file itself and that works but seems more like a
> work around than as intended.
Why would you want to ignore .giti
