Add gitignore file #130

Merged
lkarsten merged 1 commits from add_gitignore into master 2013-04-23 21:57:22 +02:00
lkarsten commented 2013-04-20 14:27:33 +02:00 (Migrated from github.com)
No description provided.
Atheros1 commented 2013-04-23 21:08:25 +02:00 (Migrated from github.com)

Why not use a command like

git commit -am "comment"

to modify only files that have been added?

Why not use a command like > git commit -am "comment" to modify only files that have been added?
lkarsten commented 2013-04-23 21:21:15 +02:00 (Migrated from github.com)

I don't follow. This commit adds a single file.

5f28f56c81

I don't follow. This commit adds a single file. https://github.com/lkarsten/PyBitmessage/commit/5f28f56c814420e4b337894664aafa32e2e8196b
Atheros1 commented 2013-04-23 21:26:10 +02:00 (Migrated from github.com)

Yes it does. If I may ask, why are we adding it?

Yes it does. If I may ask, why are we adding it?
MaPePeR commented 2013-04-23 21:29:17 +02:00 (Migrated from github.com)

Obviously to not include *.pyc files in the repository. :)

Obviously to not include *.pyc files in the repository. :)
Atheros1 commented 2013-04-23 21:32:10 +02:00 (Migrated from github.com)

But there are other files that we won't want to add either: especially *.dat files if the user turns on portable mode. I also have a large variety of extraneous files that I have made over time that I wouldn't want to add either. Why should we specify files to ignore when we can instead specify files to add? It seems much less error prone.

But there are other files that we won't want to add either: especially *.dat files if the user turns on portable mode. I also have a large variety of extraneous files that I have made over time that I wouldn't want to add either. Why should we specify files to ignore when we can instead specify files to add? It seems much less error prone.
lkarsten commented 2013-04-23 21:45:01 +02:00 (Migrated from github.com)

Jonathan Warren:

But there are other files that we won't want to add either: especially *.dat files if the user turns on portable mode. I also have a large variety of extraneous files that I have made over time that I wouldn't want to add either. Why should we specify files to ignore when we can instead specify files to add? It seems much less error prone.

It makes the "git status" output show only the things you need to
care about.

It is easy to forget to add a new file to revision control when there
are a lot of extra files laying around.

Having a .gitignore file is a common practice.

Lasse Karstensen

Jonathan Warren: > But there are other files that we won't want to add either: especially *.dat files if the user turns on portable mode. I also have a large variety of extraneous files that I have made over time that I wouldn't want to add either. Why should we specify files to ignore when we can instead specify files to add? It seems much less error prone. It makes the "git status" output show only the things you need to care about. It is easy to forget to add a new file to revision control when there are a lot of extra files laying around. Having a .gitignore file is a common practice. ## Lasse Karstensen
Atheros1 commented 2013-04-23 22:00:22 +02:00 (Migrated from github.com)

Thank you Ikarsten

Thank you Ikarsten
lkarsten commented 2013-04-23 22:22:46 +02:00 (Migrated from github.com)

Thanks for merging :)

Thanks for merging :)
This repo is archived. You cannot comment on pull requests.
No description provided.