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

Fix some typos #822

Closed
henrikolsson wants to merge 1 commits from typo_fixes into master
pull from: typo_fixes
merge into: Bitmessage:master
Conversation 4 Commits 1 Files Changed 5 +5 -5
henrikolsson commented 2015-11-08 21:49:36 +01:00 (Migrated from github.com)
Copy Link

Fixes a few typos :)

Fixes a few typos :)
PeterSurda commented 2015-11-08 21:51:19 +01:00 (Migrated from github.com)
Copy Link

Thank you,

I am developing on another fork, I'll merge it there and later it will make it into official PyBitmessage.

Thank you, I am developing on another fork, I'll merge it there and later it will make it into official PyBitmessage.
JoshuaMurphynz commented 2015-11-08 21:51:54 +01:00 (Migrated from github.com)
Copy Link

Damn you're fast ;)
On 9 Nov 2015 09:51, "Peter Šurda" notifications@github.com wrote:

Thank you,

I am developing on another fork, I'll merge it there and later it will
make it into official PyBitmessage.

—
Reply to this email directly or view it on GitHub
https://github.com/Bitmessage/PyBitmessage/pull/822#issuecomment-154869295
.

Damn you're fast ;) On 9 Nov 2015 09:51, "Peter Šurda" notifications@github.com wrote: > Thank you, > > I am developing on another fork, I'll merge it there and later it will > make it into official PyBitmessage. > > — > Reply to this email directly or view it on GitHub > https://github.com/Bitmessage/PyBitmessage/pull/822#issuecomment-154869295 > .
henrikolsson commented 2015-11-08 22:07:57 +01:00 (Migrated from github.com)
Copy Link

Cool, I saw your reference to https://github.com/mailchuck/PyBitmessage in another pull request. Is that the fork you're talking about? Will it replace this codebase?

Cool, I saw your reference to https://github.com/mailchuck/PyBitmessage in another pull request. Is that the fork you're talking about? Will it replace this codebase?
PeterSurda commented 2015-11-09 08:17:59 +01:00 (Migrated from github.com)
Copy Link

Is that the fork you're talking about?

Yes.

Will it replace this codebase?

Mostly, yes. Almost all commits to that fork will be merged here within the next month or two. With respect to this request, I don't see anything that would be incompatible. If you want, you can make a pull request against that one to speed up the workflow, however I would ask you to PGP sign your commit. Otherwise I have to pull it locally and sign myself.

> Is that the fork you're talking about? Yes. > Will it replace this codebase? Mostly, yes. Almost all commits to that fork will be merged here within the next month or two. With respect to this request, I don't see anything that would be incompatible. If you want, you can make a pull request against that one to speed up the workflow, however I would ask you to PGP sign your commit. Otherwise I have to pull it locally and sign myself.
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
bug
Milestone
No items
No Milestone v0.6.0
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-28#822
No description provided.
Delete Branch "typo_fixes"

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?