Bitmessage/PyBitmessage-2024-12-15
Archived
2
0
Fork 0
Code Issues 168 Pull Requests 53 Actions Packages Projects Releases 5 Wiki Activity

unicode() date strings. #75

New Issue
Closed
opened 2013-03-26 23:44:34 +01:00 by m0Ray · 4 comments
m0Ray commented 2013-03-26 23:44:34 +01:00 (Migrated from github.com)
Copy Link

Date/time stamps on non-english locales are crappy. Add unicode() around strftime().

I made a patch by myself. Tried to create pull request, but maybe I have no permission to do it.

Date/time stamps on non-english locales are crappy. Add unicode() around strftime(). I made a patch by myself. Tried to create pull request, but maybe I have no permission to do it.
Atheros1 commented 2013-03-28 00:09:51 +01:00 (Migrated from github.com)
Copy Link

You shouldn't need special permission to create a pull request. When I receive it I'll accept it.

You shouldn't need special permission to create a pull request. When I receive it I'll accept it.
m0Ray commented 2013-03-28 01:50:35 +01:00 (Migrated from github.com)
Copy Link

Maybe I'm a newbie to git, but I couldn't fire up neither a proper button on "Pull Requests" page, nor keyboard shortcut.
BTW, should I create a branch and modify it in order to create a pull request?

That git is too... strange for oldschooler.

Maybe I'm a newbie to git, but I couldn't fire up neither a proper button on "Pull Requests" page, nor keyboard shortcut. BTW, should I create a branch and modify it in order to create a pull request? That git is too... strange for oldschooler.
Atheros1 commented 2013-03-28 02:11:46 +01:00 (Migrated from github.com)
Copy Link

The "pull request" button is at the top of Github.
First fork PyBitmessage. Then clone to your computer. Then make changes. Then push committed changes back to your fork on Github then you can hit the pull request button.

The "pull request" button is at the top of Github. First fork PyBitmessage. Then clone to your computer. Then make changes. Then push committed changes back to your fork on Github then you can hit the pull request button.
m0Ray commented 2013-03-28 02:25:42 +01:00 (Migrated from github.com)
Copy Link

That's it! I must fork it, then clone, then push... Thanks for instructions, but it's much more complex than simply attaching the output of "diff". Anyway, thanks.

That's it! I must fork it, then clone, then push... Thanks for instructions, but it's much more complex than simply attaching the output of "diff". Anyway, thanks.
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Branches Tags
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
build
dependencies
developers
documentation
duplicate
enhancement
formatting
invalid
legal
mobile
obsolete
packaging
performance
protocol
question
refactoring
regression
security
test
translation
usability
wontfix
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Bitmessage/PyBitmessage-2024-12-15#75
No description provided.
Delete Branch "%!s()"

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?