tec
/
lexic
1
0
Fork 0
Code Issues 10 Pull Requests 1 Releases Activity

Update README #14

Open
BenedictHW wants to merge 4 commits from unknown repository into master
pull from: unknown repository
merge into: tec:master
Conversation 5 Commits 4 Files Changed 2 +156 -25
BenedictHW commented 2021-02-18 23:43:36 +00:00 (Migrated from github.com)
Copy Link

More context in #13.

More context in #13.
👍 1
tecosaur commented 2021-02-23 02:24:49 +00:00 (Migrated from github.com)
Copy Link

I'll take a look at this in a bit :)

I'll take a look at this in a bit :)
😆 1
tecosaur commented 2021-03-26 07:27:49 +00:00 (Migrated from github.com)
Copy Link

A bit ™️

A bit :tm:
BenedictHW commented 2021-03-27 02:38:47 +00:00 (Migrated from github.com)
Copy Link

Yes, the tone is more appropriate for personal notes or a blog post than a README. And some of the links might infringe copyright...TMI for sure.

Maybe you can consider cherry picking the package description commit? 04d1c2a2dd
Just to help package discoverability for people who head to MELPA.org and key in "dictionary".

Cheers,

Yes, the tone is more appropriate for personal notes or a blog post than a README. And some of the links might infringe copyright...TMI for sure. Maybe you can consider cherry picking the package description commit? https://github.com/tecosaur/lexic/pull/14/commits/04d1c2a2ddea38531afdc4cc62e47e2cd7ea357d Just to help package discoverability for people who head to MELPA.org and key in "dictionary". Cheers,
tecosaur commented 2021-03-27 02:45:28 +00:00 (Migrated from github.com)
Copy Link

Basically, the delay is because while there are bits I like, I'd like to merge a modified version, and I haven't got around to making the modifications I'd like to see.

Basically, the delay is because while there are bits I like, I'd like to merge a modified version, and I haven't got around to making the modifications I'd like to see.
BenedictHW commented 2021-03-27 02:48:23 +00:00 (Migrated from github.com)
Copy Link

Absolutely! Let me know if there's any way I can help.

Absolutely! Let me know if there's any way I can help.
This pull request is broken due to missing fork information.
You can also view command line instructions.

Step 1:

From your project repository, check out a new branch and test the changes.
git checkout -b unknown repository master
git pull origin unknown repository

Step 2:

Merge the changes and update on Forgejo.
git checkout master
git merge --no-ff unknown repository
git push origin master
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
bug

Something isn't working

  
documentation

Improvements or additions to documentation

  
duplicate

This issue or pull request already exists

  
enhancement

New feature or request

  
good first issue

Good for newcomers

  
help wanted

Extra attention is needed

  
invalid

This doesn't seem right

  
question

Further information is requested

  
wontfix

This will not be worked on

No Label
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
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: tec/lexic#14
No description provided.
Delete Branch "unknown repository"

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?