Am 15.04.2014 um 23:23 schrieb Junio C Hamano gits...@pobox.com:
Brandon McCaig bamcc...@gmail.com writes:
That is for your benefit, and for easily sharing that configuration
with collaborators. Git only cares that the file exists in your
working tree at run-time.
It is a lot more than
Frank Ammeter g...@ammeter.ch writes:
Am 15.04.2014 um 23:23 schrieb Junio C Hamano gits...@pobox.com:
Brandon McCaig bamcc...@gmail.com writes:
That is for your benefit, and for easily sharing that configuration
with collaborators. Git only cares that the file exists in your
working tree
Frank:
On Sat, Apr 12, 2014 at 7:29 AM, Frank Ammeter g...@ammeter.ch wrote:
I don’t see that argument.
I don’t know why at the time of a commit git should read unstaged files from
my working tree - that affect my commit.
.gitignore works the exact same way. If you modify .gitignore then git
Brandon McCaig bamcc...@gmail.com writes:
That is for your benefit, and for easily sharing that configuration
with collaborators. Git only cares that the file exists in your
working tree at run-time.
It is a lot more than for sharing. If you made .gitignore only
effective after it gets
Am 11.04.2014 um 22:38 schrieb Torsten Bögershausen tbo...@web.de:
On 2014-04-11 22.20, Frank Ammeter wrote:
I’m not a git expert and this might be the wrong place to ask this question,
so please send me somewhere else if I’m in the wrong place.
I asked the same question on stack overflow,
On 2014-04-11 22.20, Frank Ammeter wrote:
I’m not a git expert and this might be the wrong place to ask this question,
so please send me somewhere else if I’m in the wrong place.
I asked the same question on stack overflow, but didn’t get any response:
6 matches
Mail list logo
