You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The odr-project-reorg branch can be removed, it was a temporary development branch which was used while adapting the spec to upstream's project reorganisation and got finally merged into master.
legacy-fdk-aac-dabplus reflects the state of the package before upstream's project reorg. I don't see any harm in keeping this branch around. It was already helpful in the past to see how the package and the software was organized before.
I was expecting such an explanation of the legacy-fdk-aac-dabplus branch. I hear there's a tool called git that supports tags.
If you want to add more context you could annotate the tag, the version I provided 1.2.0-0.fdk.2.3.2.odr.toolame.0.2l.odr is based on the state of things in the specfile atm. I think it is correct and reflects the contents of the package at that state.
I think c24761c is a leaf in a branch that does not have any relevant changes left to merge. Here's a merge: radiorabe:512cc4f...radiorabe:c24761c
Also, it looks like
legacy-fdk-aac-dabplus
is just there to point to 86a8e8c.Have a look at the network graph to see them.
Proposed Solution:
odr-project-reorg
ref to it1.2.0-0.fdk.2.3.2.odr.toolame.0.2l.odr
¯_(ツ)_/¯ and remove the ref.edit: what's wrong with link formatting 🙁 wtf,
/commit/
worky,/tree/
no-worky 😲The text was updated successfully, but these errors were encountered: