| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
* version info changes cause break, fixed in next commit
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
* libs & version files under new branch names: current & develop
* previously under branch version numbers (v5|v6)
* version .yml files moved
* associated adjustments made as required, notably to:
bin/sisu se* qi* (file headers); breakage potential, testing
required
* [on dir names, want release to (alphabetically) precede
next/development, considered (cur|dev)
(current|(dev|development|progress|next)) (stable|unstable),
alpha sorting fail (release|(next|develop))]
|
| |
|
|
|
|
|
|
|
| |
* "UnFrozen" prior to original time intended (end of Debian Freeze
for Jessie), reason: the upstream bugfix 5.7.2 intended for
Jessie (packaged for Debian as 5.7.1-2) was not accepted; this
means even if another patch does get sent for Jessie, it will
not be from upstream branch)
* post Debian:Jessie development commits
|
| |
|
|
|
|
|
|
|
|
| |
* NOTE: sisu is in development freeze mirroring the Debian release cycle;
bugfix & documentation update only, pending the release of Debian Jessie
* (as sisu upstream) the cleanest git workflow solution to the Debian freeze
appears to be to follow the Debian freeze with respect to upstream alterations
of sisu (bugfix & documentation only), incrementing upstream version number
as usual, whilst building package as required for Debian freeze version of
sisu 5.7.1-*
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
