According to [this](http://www.magentocommerce.com/magento-connect/thefind-feed-1.html) TheFind Feed module does not come with the latest versions of Magento( > 1.6).
Carl Suster [Tue, 6 May 2014 07:38:57 +0000 (17:38 +1000)]
Remove redundant Umbraco exceptions to VS rules
From the discussion on #1013:
Since the rule in VS is packages/*, the fact that it contains a slash means
that it is anchored to the top level. That is, is will only apply to
a directory called packages at the top level, and not to any at deeper
directories like App_Data. So these rules at the bottom of your changes
actually aren't necessary after all. I just confirmed this with a quick test.
Jacob Rigby [Wed, 23 Apr 2014 20:50:28 +0000 (15:50 -0500)]
Fix eol issues
Some files don't contain a line separator ('\n') at the end. Add the
missing eol.
In POSIX, all lines of text should end with a newline character by
definition. See
http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html
section 3.397 for more.
See https://gist.github.com/jacknagel/1020172 for a gist of the issue.
When working with multifile LaTeX-documents in AUCTeX in emacs, it creates the auto-folder to keep track of styles, macros etc. in the whole document. Unnecessary of versioning purposes.
Elvis Nuñez [Tue, 15 Apr 2014 16:59:29 +0000 (18:59 +0200)]
Ignore xcuserstate
xcuserstate files are generated from within Xcode and saved in your project bundle to remember your last opened file, the open state of any group folders, open tabs, and any other user setting your project might need to remember, this is something that shouldn't be tracked in version control
Elvis Nuñez [Tue, 15 Apr 2014 16:56:25 +0000 (18:56 +0200)]
Ignore xcuserstate
xcuserstate files are generated from within Xcode and saved in your project bundle to remember your last opened file, the open state of any group folders, open tabs, and any other user setting your project might need to remember
Carl Suster [Mon, 14 Apr 2014 03:41:01 +0000 (13:41 +1000)]
Merge pull request #1008 from maieul/master
Add rules for TeX packages (e)ledmac and (e)ledpar. References from manuals:
eledmac p. 46:
> Each section will read and write an associated "line-list file", containing information used to do the numbering; the file will be called `<jobname>.nn`, where `nn` is the section number. However, you may direct that an extra string be added before the `nn` in that filename, in order to distinguish these temporary files from others: that string is called `\extensionchars`. Initially it's empty, since different operating systems have greatly varying ideas about what characters are permitted in file names. So `\renewcommand{\extensionchars}{-}` gives temporary files called `<jobname>.-1`, `<jobname>.-2`, etc.
eledmac p. 112:
> Endnotes of all varieties are saved up in a file, typically named `<jobname>.end`.
eledpar p.8:
> The `\beginnumbering` macro resets the line number to zero, reads an auxiliary file called `<jobname>.nn` (where `<jobname>` is the name of the main input file for this job, and `nn` is 1 for the first numbered section, 2 for the second section, and so on), and then creates a new version of this auxiliary file to collect information during this run. Separate auxiliary files are maintained for right hand texts and these are named `<jobname>.nnR`, using the ‘R’ to distinguish them from the left hand and serial (non-parallel) texts.
Revert "Packages folder is ignored correctly".
Without the asterisk at the end of the directory's path, an exception for
a file within this directory does not work.
(ex. !packages/repositories.config)
Carl Suster [Sun, 6 Apr 2014 00:38:40 +0000 (10:38 +1000)]
Merge branch 'fix-1022'
Restore the Xcode rules to the Objective-C template as per the discussion
thread on 5bd4330. Although the rules correspond to an IDE and so are
global, most users of the Obj-C template expect to find the Xcode rules
in the template generated by github.com, since the IDE is so ubiquitous.
This could possibly be resolved by adding a template transclusion
mechanism in the future, but for now duplication is the way to go.
This is a PR to remove the opinionated lines from the Node.js .gitignore file.
I do not believe that Github's pre-baked .gitignore files should be promulgating opinions, especially in a community that is as fresh as the Node.js community. Questions of what should be checked in should be a decision made on an organization-by-organization basis, or left up to the individual. Github's inclusion of opinion in these files puts unnecessary authority behind that opinion, which can have the negative side-effect of people following without thinking.
projects / gitignore.git / log