Hi.
Is there a way to avoid having these to file to always show up as non-staged?
$ git status # On branch cat # Changes not staged for commit: # (use "git add <file>..." to update what will be committed) # (use "git checkout -- <file>..." to discard changes in working directory) # # modified: externals/httplib2 (new commits) # modified: scripts/i18n (new commits)
I found this suggestion online (can't remember where): Some files in a repository, which are versioned (i.e. they can't be git-ignored), are often changed, but rarely committed. Usually these are various local configuration files that are edited, but should never be committed upstream.
Git lets you ignore those files by assuming they are unchanged. This is done by running the git update-index --assume-unchanged path/to/file.txt
but it is not a permanent solution.
Bye Mpaa
yes, there is a file named ".gitignore" or something like that, see it
Best
On Fri, Jan 31, 2014 at 12:26 PM, Mpaa mpaa.wiki@gmail.com wrote:
Hi.
Is there a way to avoid having these to file to always show up as non-staged?
$ git status # On branch cat # Changes not staged for commit: # (use "git add <file>..." to update what will be committed) # (use "git checkout -- <file>..." to discard changes in working directory) # # modified: externals/httplib2 (new commits) # modified: scripts/i18n (new commits)
I found this suggestion online (can't remember where): Some files in a repository, which are versioned (i.e. they can't be git-ignored), are often changed, but rarely committed. Usually these are various local configuration files that are edited, but should never be committed upstream.
Git lets you ignore those files by assuming they are unchanged. This is done by running the git update-index --assume-unchanged path/to/file.txt
but it is not a permanent solution.
Bye Mpaa
Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
"Some files in a repository, which are versioned (i.e. they can't be git-ignored), ..." I guess those two files are versioned, so can we git-ignore?
On Fri, Jan 31, 2014 at 11:22 AM, Amir Ladsgroup ladsgroup@gmail.comwrote:
yes, there is a file named ".gitignore" or something like that, see it
Best
On Fri, Jan 31, 2014 at 12:26 PM, Mpaa mpaa.wiki@gmail.com wrote:
Hi.
Is there a way to avoid having these to file to always show up as non-staged?
$ git status # On branch cat # Changes not staged for commit: # (use "git add <file>..." to update what will be committed) # (use "git checkout -- <file>..." to discard changes in working directory) # # modified: externals/httplib2 (new commits) # modified: scripts/i18n (new commits)
I found this suggestion online (can't remember where): Some files in a repository, which are versioned (i.e. they can't be git-ignored), are often changed, but rarely committed. Usually these are various local configuration files that are edited, but should never be committed upstream.
Git lets you ignore those files by assuming they are unchanged. This is done by running the git update-index --assume-unchanged path/to/file.txt
but it is not a permanent solution.
Bye Mpaa
Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
-- Amir
Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
their version are different compare to the upstream content (e.g. core or compat) for so I think it worth a try
On Fri, Jan 31, 2014 at 2:30 PM, Mpaa mpaa.wiki@gmail.com wrote:
"Some files in a repository, which are versioned (i.e. they can't be git-ignored), ..." I guess those two files are versioned, so can we git-ignore?
On Fri, Jan 31, 2014 at 11:22 AM, Amir Ladsgroup ladsgroup@gmail.comwrote:
yes, there is a file named ".gitignore" or something like that, see it
Best
On Fri, Jan 31, 2014 at 12:26 PM, Mpaa mpaa.wiki@gmail.com wrote:
Hi.
Is there a way to avoid having these to file to always show up as non-staged?
$ git status # On branch cat # Changes not staged for commit: # (use "git add <file>..." to update what will be committed) # (use "git checkout -- <file>..." to discard changes in working directory) # # modified: externals/httplib2 (new commits) # modified: scripts/i18n (new commits)
I found this suggestion online (can't remember where): Some files in a repository, which are versioned (i.e. they can't be git-ignored), are often changed, but rarely committed. Usually these are various local configuration files that are edited, but should never be committed upstream.
Git lets you ignore those files by assuming they are unchanged. This is done by running the git update-index --assume-unchanged path/to/file.txt
but it is not a permanent solution.
Bye Mpaa
Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
-- Amir
Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
https://stackoverflow.com/questions/3240881/git-can-i-suppress-listing-of-mo...
So the trick is to adapt .gitmodules, not .gitignore.
Merlijn
On 31 January 2014 09:56, Mpaa mpaa.wiki@gmail.com wrote:
Hi.
Is there a way to avoid having these to file to always show up as non-staged?
$ git status # On branch cat # Changes not staged for commit: # (use "git add <file>..." to update what will be committed) # (use "git checkout -- <file>..." to discard changes in working directory) # # modified: externals/httplib2 (new commits) # modified: scripts/i18n (new commits)
I found this suggestion online (can't remember where): Some files in a repository, which are versioned (i.e. they can't be git-ignored), are often changed, but rarely committed. Usually these are various local configuration files that are edited, but should never be committed upstream.
Git lets you ignore those files by assuming they are unchanged. This is done by running the git update-index --assume-unchanged path/to/file.txt
but it is not a permanent solution.
Bye Mpaa
Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
This is mine: 1 [submodule "i18n"] 2 path = scripts/i18n 3 url = https://gerrit.wikimedia.org/r/p/pywikibot/i18n.git 4 branch = . 5 ignore = dirty 6 7 [submodule "externals/httplib2"] 8 path = ex/httplib2ternals/httplib2 9 url = https://gerrit.wikimedia.org/r/p/pywikibot/externals/httplib2.git 10 branch = . 11 ignore = dirty
Looks like ignore = dirty is already there ...
On Fri, Jan 31, 2014 at 1:24 PM, Merlijn van Deen valhallasw@arctus.nlwrote:
https://stackoverflow.com/questions/3240881/git-can-i-suppress-listing-of-mo...
So the trick is to adapt .gitmodules, not .gitignore.
Merlijn
On 31 January 2014 09:56, Mpaa mpaa.wiki@gmail.com wrote:
Hi.
Is there a way to avoid having these to file to always show up as non-staged?
$ git status # On branch cat # Changes not staged for commit: # (use "git add <file>..." to update what will be committed) # (use "git checkout -- <file>..." to discard changes in working directory) # # modified: externals/httplib2 (new commits) # modified: scripts/i18n (new commits)
I found this suggestion online (can't remember where): Some files in a repository, which are versioned (i.e. they can't be git-ignored), are often changed, but rarely committed. Usually these are various local configuration files that are edited, but should never be committed upstream.
Git lets you ignore those files by assuming they are unchanged. This is done by running the git update-index --assume-unchanged path/to/file.txt
but it is not a permanent solution.
Bye Mpaa
Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
Does ignore=all work?
On 31 January 2014 13:32, Mpaa mpaa.wiki@gmail.com wrote:
This is mine: 1 [submodule "i18n"] 2 path = scripts/i18n 3 url = https://gerrit.wikimedia.org/r/p/pywikibot/i18n.git 4 branch = . 5 ignore = dirty 6 7 [submodule "externals/httplib2"] 8 path = ex/httplib2ternals/httplib2 9 url = https://gerrit.wikimedia.org/r/p/pywikibot/externals/httplib2.git 10 branch = . 11 ignore = dirty
Looks like ignore = dirty is already there ...
On Fri, Jan 31, 2014 at 1:24 PM, Merlijn van Deen valhallasw@arctus.nlwrote:
https://stackoverflow.com/questions/3240881/git-can-i-suppress-listing-of-mo...
So the trick is to adapt .gitmodules, not .gitignore.
Merlijn
On 31 January 2014 09:56, Mpaa mpaa.wiki@gmail.com wrote:
Hi.
Is there a way to avoid having these to file to always show up as non-staged?
$ git status # On branch cat # Changes not staged for commit: # (use "git add <file>..." to update what will be committed) # (use "git checkout -- <file>..." to discard changes in working directory) # # modified: externals/httplib2 (new commits) # modified: scripts/i18n (new commits)
I found this suggestion online (can't remember where): Some files in a repository, which are versioned (i.e. they can't be git-ignored), are often changed, but rarely committed. Usually these are various local configuration files that are edited, but should never be committed upstream.
Git lets you ignore those files by assuming they are unchanged. This is done by running the git update-index --assume-unchanged path/to/file.txt
but it is not a permanent solution.
Bye Mpaa
Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
it seems so
On Fri, Jan 31, 2014 at 3:12 PM, Merlijn van Deen valhallasw@arctus.nlwrote:
Does ignore=all work?
On 31 January 2014 13:32, Mpaa mpaa.wiki@gmail.com wrote:
This is mine: 1 [submodule "i18n"] 2 path = scripts/i18n 3 url = https://gerrit.wikimedia.org/r/p/pywikibot/i18n.git 4 branch = . 5 ignore = dirty 6 7 [submodule "externals/httplib2"] 8 path = ex/httplib2ternals/httplib2 9 url = https://gerrit.wikimedia.org/r/p/pywikibot/externals/httplib2.git 10 branch = . 11 ignore = dirty
Looks like ignore = dirty is already there ...
On Fri, Jan 31, 2014 at 1:24 PM, Merlijn van Deen valhallasw@arctus.nlwrote:
https://stackoverflow.com/questions/3240881/git-can-i-suppress-listing-of-mo...
So the trick is to adapt .gitmodules, not .gitignore.
Merlijn
On 31 January 2014 09:56, Mpaa mpaa.wiki@gmail.com wrote:
Hi.
Is there a way to avoid having these to file to always show up as non-staged?
$ git status # On branch cat # Changes not staged for commit: # (use "git add <file>..." to update what will be committed) # (use "git checkout -- <file>..." to discard changes in working directory) # # modified: externals/httplib2 (new commits) # modified: scripts/i18n (new commits)
I found this suggestion online (can't remember where): Some files in a repository, which are versioned (i.e. they can't be git-ignored), are often changed, but rarely committed. Usually these are various local configuration files that are edited, but should never be committed upstream.
Git lets you ignore those files by assuming they are unchanged. This is done by running the git update-index --assume-unchanged path/to/file.txt
but it is not a permanent solution.
Bye Mpaa
Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l