- Original Message -
Why didn't these objections surface before when we asked and not now
when we tell what will happen, or was they just forgotten/ignored?
They were not raised because the idea up to now was to keep 4.6.x from svn and
do 4.7 from git, which would make dec 22 an
Dirk,
We were discussing in #kde-sysadmin whether it made sense to move not
just trunk/4.7 development to Git next week, but 4.6 as well. No one
really likes the idea of having two SCMs active at the same time,
which was the current plan.
Do you consider putting together the release scripts in
- Original Message -
Dirk,
We were discussing in #kde-sysadmin whether it made sense to move not
just trunk/4.7 development to Git next week, but 4.6 as well. No one
really likes the idea of having two SCMs active at the same time,
which was the current plan.
Do you consider
Am Montag, 13. Dezember 2010, um 22:44:04 schrieb Albert Astals Cid:
A Dilluns, 13 de desembre de 2010, Ian Monroe va escriure:
Dirk,
We were discussing in #kde-sysadmin whether it made sense to move not
just trunk/4.7 development to Git next week, but 4.6 as well. No one
really likes the
On Monday, December 13, 2010 16:49:29 Tom Albers wrote:
- Original Message -
Dirk,
We were discussing in #kde-sysadmin whether it made sense to move not
just trunk/4.7 development to Git next week, but 4.6 as well. No one
really likes the idea of having two SCMs active at the
On Mon, 13 Dec 2010 22:53:50 -0500
Michael Pyne mp...@kde.org wrote:
On Monday, December 13, 2010 16:49:29 Tom Albers wrote:
- Original Message -
Dirk,
We were discussing in #kde-sysadmin whether it made sense to move not
just trunk/4.7 development to Git next week, but 4.6
