Bitmessage/PyBitmessage-2025-02-21
Archived
2
0
Fork 0
Code Issues 167 Pull Requests 54 Actions Packages Projects Releases 5 Wiki Activity

Add gitignore file #130

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

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)
Copy Link

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)
Copy Link

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)
Copy Link

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)
Copy Link

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)
Copy Link

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)
Copy Link

Thank you Ikarsten

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

Thanks for merging :)

Thanks for merging :)
This repo is archived. You cannot comment on pull requests.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something isn't working as it's supposed to
build
Related to building or build system
dependencies
Pull requests that update a dependency file
developers
The issue is relevant mainly for developers rather than users
documentation
duplicate
enhancement
New feature
formatting
Code or UI text formatting
invalid
legal
mobile
Frontend for mobile devices (kivy)
obsolete
packaging
performance
protocol
Protocol change
question
refactoring
regression
Some issue, fixed in the past, appears again
security
test
translation
usability
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
PeterSurda
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Bitmessage/PyBitmessage-2025-02-21#130
No description provided.
Delete Branch "add_gitignore"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?