starred/librespot

Fork 0

mirror of https://github.com/librespot-org/librespot.git synced 2026-04-27 08:15:50 +03:00

librespot? #9

New issue

Closed

opened 2026-02-27 19:28:15 +03:00 by kerem · 5 comments

kerem commented

2026-02-27 19:28:15 +03:00

Owner

Originally created by @michaelherger on GitHub (Jan 29, 2018).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/18

I have a fork of plietar/librespot which I've modified. Now I'd like to base it off librespot-org/librespot. Anybody knows how I would do this? I would like to be able to post pull requests here (if there ever was one :-))

Originally created by @michaelherger on GitHub (Jan 29, 2018). Original GitHub issue: https://github.com/librespot-org/librespot/issues/18 I have a fork of plietar/librespot which I've modified. Now I'd like to base it off librespot-org/librespot. Anybody knows how I would do this? I would like to be able to post pull requests here (if there ever was one :-))

kerem

2026-02-27 19:28:15 +03:00

closed this issue
added the
help wanted
label

kerem commented

2026-02-27 19:28:16 +03:00

Author

Owner

@alin23 commented on GitHub (Jan 29, 2018):

You can make another fork and cherry-pick your commits to the new fork ¯_(ツ)_/¯

@alin23 commented on GitHub (Jan 29, 2018): You can make another fork and cherry-pick your commits to the new fork ¯\_(ツ)_/¯

kerem commented

2026-02-27 19:28:16 +03:00

Author

Owner

@ComlOnline commented on GitHub (Jan 29, 2018):

There's no easy way to do this as there could be conflicts etc. After you have forked a new repo from librespot-org you could create pull requests into it and do it that way. (Hey @alin23, you dropped this ;) \ )

@ComlOnline commented on GitHub (Jan 29, 2018): There's no easy way to do this as there could be conflicts etc. After you have forked a new repo from librespot-org you could create pull requests into it and do it that way. (Hey @alin23, you dropped this ;) \\ )

kerem commented

2026-02-27 19:28:16 +03:00

Author

Owner

@sashahilton00 commented on GitHub (Jan 29, 2018):

@michaelherger like @ComlOnline there's no easy way. I just had a look at a few of your branches, it looks like you created a few. If you explain a little about which ones you added and what they do, I'd be happy to start copy-pasting stuff if you want a hand migrating.

@sashahilton00 commented on GitHub (Jan 29, 2018): @michaelherger like @ComlOnline there's no easy way. I just had a look at a few of your branches, it looks like you created a few. If you explain a little about which ones you added and what they do, I'd be happy to start copy-pasting stuff if you want a hand migrating.

kerem commented

2026-02-27 19:28:16 +03:00

Author

Owner

@michaelherger commented on GitHub (Jan 29, 2018):

I don't think there's much of general interest in my branches as of today (there was one which got merged a while back). They mostly deal with my Spotty plugin for Logitech Media Server (LMS). I needed a way to talk from librespot/spotty to LMS. At least two branches deal with my more or less successful attempts for this feature. Another one (refactor-0817) tries to bring my changes up to speed with the re-factoring started by @plietar back in August of last year (and now continued here). I'll probably just live with the current situation until that latest branch is ready to be merged into my spotty branch. Then I'll create a new fork and try to push that fork only. Thanks for all your input!

@michaelherger commented on GitHub (Jan 29, 2018): I don't think there's much of general interest in my branches as of today (there was one which got merged a while back). They mostly deal with my Spotty plugin for [Logitech Media Server (LMS)](https://github.com/Logitech/slimserver). I needed a way to talk from librespot/spotty to LMS. At least two branches deal with my more or less successful attempts for this feature. Another one (refactor-0817) tries to bring my changes up to speed with the re-factoring started by @plietar back in August of last year (and now continued here). I'll probably just live with the current situation until that latest branch is ready to be merged into my spotty branch. Then I'll create a new fork and try to push that fork only. Thanks for all your input!

kerem commented

2026-02-27 19:28:16 +03:00

Author

Owner

@michaelherger commented on GitHub (Jan 31, 2018):

FWIW: I can submit pull requests even from my existing, old fork, without forking librespot-org/librespot again. I merged changes from the latter on top of my existing master, pushed to my origin. From where I was able to submit this pull request https://github.com/librespot-org/librespot/pull/111

@michaelherger commented on GitHub (Jan 31, 2018): FWIW: I can submit pull requests even from my existing, old fork, without forking librespot-org/librespot again. I merged changes from the latter on top of my existing master, pushed to my origin. From where I was able to submit this pull request https://github.com/librespot-org/librespot/pull/111

kerem referenced this issue

2026-02-27 19:29:32 +03:00

[GH-ISSUE #349] Librespot locks up when running out of diskspace #229

kerem referenced this issue

2026-02-27 19:59:55 +03:00

[PR #9] [MERGED] Update dependencies and fix the use of deprecated functionality #777

No milestone

No project

No assignees

1 participant

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

starred/librespot#9

No description provided.

Rows
Columns