| 1 |
On Tue, Mar 04, 2014 at 09:17:42PM -0800, Brian Dolbec wrote: |
| 2 |
> On Tue, 4 Mar 2014 20:50:38 -0800, W. Trevor King wrote: |
| 3 |
> > On Sun, Mar 02, 2014 at 03:01:00PM -0800, Brian Dolbec wrote: |
| 4 |
> > These all look like entries for a local $GIT_DIR/info/exclude, instead |
| 5 |
> > of the shared, in-tree .gitignore, since they're specific to your |
| 6 |
> > workflow and not catalyst or it's build process. |
| 7 |
> |
| 8 |
> Yes, they are. I've never professed to be a git "expert" |
| 9 |
> Please enlighten me on that. It's annoying trying to wade through |
| 10 |
> all those files making commits. |
| 11 |
|
| 12 |
The “DESCRIPTION” section of gitignore(5) goes through it pretty |
| 13 |
clearly [1]. $GIT_DIR/info/exclude (likely |
| 14 |
~/src/catalyst/.git/info/exclude or similar for you) has the same |
| 15 |
syntax as .gitignore, but it's not versioned. gitignore(5) recommends |
| 16 |
it for [1]: |
| 17 |
|
| 18 |
Patterns which are specific to a particular repository but which do |
| 19 |
not need to be shared with other related repositories (e.g., |
| 20 |
auxiliary files that live inside the repository but are specific to |
| 21 |
one user’s workflow) |
| 22 |
|
| 23 |
Cheers, |
| 24 |
Trevor |
| 25 |
|
| 26 |
[1]: https://www.kernel.org/pub/software/scm/git/docs/gitignore.html |
| 27 |
|
| 28 |
-- |
| 29 |
This email may be signed or encrypted with GnuPG (http://www.gnupg.org). |
| 30 |
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy |
Archives