[qos-ch/slf4j] e701a4: Updated broken links on mailinglists archives on N...

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: e701a43563b875c2491addcf6950aa7d1b9ea7aa https://github.com/qos-ch/slf4j/commit/e701a43563b875c2491addcf6950aa7d1b9ea... Author: Libor Jelinek <ljelinek@virtage.com> Date: 2012-09-21 (Fri, 21 Sep 2012) Changed paths: M slf4j-site/src/site/pages/mailing-lists.html Log Message: ----------- Updated broken links on mailinglists archives on Nabble (http://bugzilla.slf4j.org/show_bug.cgi?id=218) Commit: d6205bf3bd83b55c0cb1d6da0edaab093a4eb1f0 https://github.com/qos-ch/slf4j/commit/d6205bf3bd83b55c0cb1d6da0edaab093a4eb... Author: Libor Jelinek <ljelinek@virtage.com> Date: 2012-09-21 (Fri, 21 Sep 2012) Changed paths: M osgi-over-slf4j/pom.xml M osgi-over-slf4j/src/main/java/org/slf4j/osgi/logservice/impl/Activator.java M osgi-over-slf4j/src/main/java/org/slf4j/osgi/logservice/impl/LogServiceFactory.java M osgi-over-slf4j/src/main/java/org/slf4j/osgi/logservice/impl/LogServiceImpl.java M pom.xml Log Message: ----------- Merge remote-tracking branch 'upstream/master' Commit: 8888edb033f7f6c36efc84d522fcb84a17a0b863 https://github.com/qos-ch/slf4j/commit/8888edb033f7f6c36efc84d522fcb84a17a0b... Author: Ceki Gulcu <ceki@qos.ch> Date: 2012-09-22 (Sat, 22 Sep 2012) Changed paths: M slf4j-site/src/site/pages/mailing-lists.html Log Message: ----------- Merge pull request #23 from bircow/master Website: updated broken links on mailinglists archives for Nabble (http://bugzilla.slf4j.org/show_bug.cgi?id=218) Compare: https://github.com/qos-ch/slf4j/compare/3e121c2cac6a...8888edb033f7

Please, how (or when) the changes will be actually pushed to public slf4j.org website? It's not urgent, I just want to don't forget to mark related bug as fixed when updated links will be actually published on the official website mailing-lists.html page. Libor On Sat, Sep 22, 2012 at 10:08 AM, Ceki Gulcu <ceki@qos.ch> wrote:
Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: e701a43563b875c2491addcf6950aa7d1b9ea7aa https://github.com/qos-ch/slf4j/commit/e701a43563b875c2491addcf6950aa7d1b9ea... Author: Libor Jelinek <ljelinek@virtage.com> Date: 2012-09-21 (Fri, 21 Sep 2012)
Changed paths: M slf4j-site/src/site/pages/mailing-lists.html
Log Message: ----------- Updated broken links on mailinglists archives on Nabble (http://bugzilla.slf4j.org/show_bug.cgi?id=218)
Commit: d6205bf3bd83b55c0cb1d6da0edaab093a4eb1f0 https://github.com/qos-ch/slf4j/commit/d6205bf3bd83b55c0cb1d6da0edaab093a4eb... Author: Libor Jelinek <ljelinek@virtage.com> Date: 2012-09-21 (Fri, 21 Sep 2012)
Changed paths: M osgi-over-slf4j/pom.xml M osgi-over-slf4j/src/main/java/org/slf4j/osgi/logservice/impl/Activator.java M osgi-over-slf4j/src/main/java/org/slf4j/osgi/logservice/impl/LogServiceFactory.java M osgi-over-slf4j/src/main/java/org/slf4j/osgi/logservice/impl/LogServiceImpl.java M pom.xml
Log Message: ----------- Merge remote-tracking branch 'upstream/master'
Commit: 8888edb033f7f6c36efc84d522fcb84a17a0b863 https://github.com/qos-ch/slf4j/commit/8888edb033f7f6c36efc84d522fcb84a17a0b... Author: Ceki Gulcu <ceki@qos.ch> Date: 2012-09-22 (Sat, 22 Sep 2012)
Changed paths: M slf4j-site/src/site/pages/mailing-lists.html
Log Message: ----------- Merge pull request #23 from bircow/master
Website: updated broken links on mailinglists archives for Nabble (http://bugzilla.slf4j.org/show_bug.cgi?id=218)
Compare: https://github.com/qos-ch/slf4j/compare/3e121c2cac6a...8888edb033f7
_______________________________________________ slf4j-dev mailing list slf4j-dev@qos.ch http://mailman.qos.ch/mailman/listinfo/slf4j-dev

On 23.09.2012 16:46, Libor Jelinek wrote:
Please, how (or when) the changes will be actually pushed to public slf4j.org website? It's not urgent, I just want to don't forget to mark related bug as fixed when updated links will be actually published on the official website mailing-lists.html page.
Hi Libor, A bug is considered fixed when the relevant fix hits the git repo. There is no need to wait for the release in order to mark a bug as fixed. -- Ceki http://twitter.com/ceki

Hello Ceki! No no, I meant when content of git's slf4j/tree/master/slf4j-site/src/site/pages/mailing-lists.html will become identical to http://www.slf4j.org/mailing-lists.html. In that moment, a bug is actually fixed from reporter point of view. Libor On Sun, Sep 23, 2012 at 8:12 PM, ceki <ceki@qos.ch> wrote:
On 23.09.2012 16:46, Libor Jelinek wrote:
Please, how (or when) the changes will be actually pushed to public slf4j.org website? It's not urgent, I just want to don't forget to mark related bug as fixed when updated links will be actually published on the official website mailing-lists.html page.
Hi Libor,
A bug is considered fixed when the relevant fix hits the git repo. There is no need to wait for the release in order to mark a bug as fixed.
-- Ceki http://twitter.com/ceki
_______________________________________________ slf4j-dev mailing list slf4j-dev@qos.ch http://mailman.qos.ch/mailman/listinfo/slf4j-dev
participants (3)
-
ceki
-
Ceki Gulcu
-
Libor Jelinek