multiple .gitignore and friends in same workdir possible?
A message that is not in the archive (sent off-list or not yet received): 4526533254752708319@unknownmsgid
Heya,
Quoted 2 lines · Konrad Karl
Is this currently possible or am I missing something? It would ease my task a lot.
I assume that each repo has it's own gitdir, in which case it has it's own config file, so you could just use "git config core.excludesfile .gitignore.one"?
Signature · 3 lines
Cheers, Sverre Rabbelier
Hi
Quoted 9 lines · Sverre Rabbelier
Heya,
Quoted 2 lines · Konrad Karl
Is this currently possible or am I missing something? It would ease my task a lot.
I assume that each repo has it's own gitdir, in which case it has it's own config file, so you could just use "git config core.excludesfile .gitignore.one"?
yes I could (i confess I was not aware of this config var) but the fine manual says:
In _addition_ to .gitignore (per-directory) and .git/info/exclude, git looks into this file for patterns of files which are not meant to be tracked.
so if there was some way to _not_ consider the standard .gitignore &friends I would be happy to live with.
Greetings,
Konrad
Quoted 5 lines
Signature · 4 lines
-- Cheers, Sverre Rabbelier
Konrad Karl venit, vidit, dixit 23.04.2010 16:32:
Quoted 16 lines
Hi
Quoted 9 lines · Sverre Rabbelier
Heya,
Quoted 2 lines · Konrad Karl
Is this currently possible or am I missing something? It would ease my task a lot.
I assume that each repo has it's own gitdir, in which case it has it's own config file, so you could just use "git config core.excludesfile .gitignore.one"?
yes I could (i confess I was not aware of this config var) but the fine manual says:
Quoted 6 lines
In _addition_ to .gitignore (per-directory) and .git/info/exclude, git looks into this file for patterns of files which are not meant to be tracked.
so if there was some way to _not_ consider the standard .gitignore &friends I would be happy to live with.
If you control the creation of the repos, why don't you simply leave the standard .gitignore empty and use the config as suggested by Sverre?
Michael
Quoted 6 lines · Michael J Gruber
Konrad Karl venit, vidit, dixit 23.04.2010 16:32:
Quoted 5 lines
Hi
Quoted 2 lines · Sverre Rabbelier
Heya,
[ ...... ]
Quoted 5 lines
Quoted 2 lines
so if there was some way to _not_ consider the standard .gitignore &friends I would be happy to live with.
If you control the creation of the repos, why don't you simply leave the standard .gitignore empty and use the config as suggested by Sverre?
Because this information does not getting transfered with git clone.
People have the chance to forget to set this variable after cloning the source repo and they will.
Konrad
Quoted 6 lines
Michael
--
To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Konrad Karl venit, vidit, dixit 23.04.2010 17:03:
Quoted 11 lines · Michael J Gruber
Quoted 6 lines
Konrad Karl venit, vidit, dixit 23.04.2010 16:32:
Quoted 5 lines
Hi
Quoted 2 lines · Sverre Rabbelier
Heya,
[ ...... ]
Quoted 3 lines
Quoted 2 lines
so if there was some way to _not_ consider the standard .gitignore &friends I would be happy to live with.
Quoted 7 lines
Quoted 2 lines
If you control the creation of the repos, why don't you simply leave the standard .gitignore empty and use the config as suggested by Sverre?
Because this information does not getting transfered with git clone.
People have the chance to forget to set this variable after cloning the source repo and they will.
...and the same is true for setting GIT_DIR appropriately for each repo
- people will commit to the wrong repo, which is even worse. That's why it's a fragile approach to begin with. Is there no chance you could put those libs in subdirs and use git modules?
Michael
Quoted 9 lines · Michael J Gruber
Konrad Karl venit, vidit, dixit 23.04.2010 17:03:
Quoted 5 lines · Michael J Gruber
Quoted 4 lines
Konrad Karl venit, vidit, dixit 23.04.2010 16:32:
Quoted 3 lines
Hi
On Fri, Apr 23, 2010 at 03:01:42PM +0200, Sverre Rabbelier wrote:
.........
Quoted 2 lines
Because this information does not getting transfered with git clone.
Quoted 7 lines
Quoted 2 lines
People have the chance to forget to set this variable after cloning the source repo and they will.
...and the same is true for setting
GIT_DIRappropriately for each repo
- people will commit to the wrong repo, which is even worse. That's why it's a fragile approach to begin with. Is there no chance you could put those libs in subdirs and use git modules?
the chance exists for the future but the existing build system does not support it (especially for older releases which I would like to be able to rebuild as is).
I think a script with a prominent name in the workdir which will set the git variable will be the next convenient solution which we can live with.
thanks for your input,
Konrad
Quoted 2 lines
Michael
Quoted 9 lines · Michael J Gruber
Konrad Karl venit, vidit, dixit 23.04.2010 17:03:
Quoted 5 lines · Michael J Gruber
Quoted 4 lines
Konrad Karl venit, vidit, dixit 23.04.2010 16:32:
Quoted 3 lines
Hi
On Fri, Apr 23, 2010 at 03:01:42PM +0200, Sverre Rabbelier wrote:
.........
Quoted 2 lines
Because this information does not getting transfered with git clone.
Quoted 7 lines
Quoted 2 lines
People have the chance to forget to set this variable after cloning the source repo and they will.
...and the same is true for setting
GIT_DIRappropriately for each repo
- people will commit to the wrong repo, which is even worse. That's why it's a fragile approach to begin with. Is there no chance you could put those libs in subdirs and use git modules?
the chance exists for the future but the existing build system does not support it (especially for older releases which I would like to be able to rebuild as is).
I think a script with a prominent name in the workdir which will set the git variable will be the next convenient solution which we can live with.
thanks for your input,
Konrad
Quoted 2 lines
Michael
Quoted 6 lines · Michael J Gruber
Konrad Karl venit, vidit, dixit 23.04.2010 16:32:
Quoted 5 lines
Hi
Quoted 2 lines · Sverre Rabbelier
Heya,
[ ...... ]
Quoted 5 lines
Quoted 2 lines
so if there was some way to _not_ consider the standard .gitignore &friends I would be happy to live with.
If you control the creation of the repos, why don't you simply leave the standard .gitignore empty and use the config as suggested by Sverre?
Because this information does not getting transfered with git clone.
People have the chance to forget to set this variable after cloning the source repo and they will.
Konrad
Quoted 6 lines
Michael
--
To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi
Quoted 9 lines · Sverre Rabbelier
Heya,
Quoted 2 lines · Konrad Karl
Is this currently possible or am I missing something? It would ease my task a lot.
I assume that each repo has it's own gitdir, in which case it has it's own config file, so you could just use "git config core.excludesfile .gitignore.one"?
yes I could (i confess I was not aware of this config var) but the fine manual says:
In _addition_ to .gitignore (per-directory) and .git/info/exclude, git looks into this file for patterns of files which are not meant to be tracked.
so if there was some way to _not_ consider the standard .gitignore &friends I would be happy to live with.
Greetings,
Konrad
Quoted 5 lines
Signature · 4 lines
-- Cheers, Sverre Rabbelier