bout 30 days. If reflogs can't keep objects alive, your
> > repository would have started shrinking in about 2 weeks.
>
> Thanks, after following all of your tips it's now down to 44M instead of
> 64M - but that's still way too large. Having a look at the history again,
> I see that many of the recent unrelated commits vanished, but there are
> still bunch of commits from 2007 and pre-2007 that are completely
> unrelated.
doing a prune last makes me wonder if a repack at the end is not needed;
git repack -a -d -f
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
n any of the subrepos you
also commit and push the meta repo.
Thinking about this; maybe the sysadmins can research if they can make this
happen automatically...
disclaimer; I'm no submodules expert and my limited experience is from 2
versions ago. Als
cations that need them), libkdeedu and keedu/data.
There are some more problems, see
http://lists.kde.org/?l=kde-scm-interest&m=128394136707263&w=2
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
to link up git and reviewboard and some other parts
with minimal manual input but in the end the actual users will go like;
ehm, but, thats not how I want to work!
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
don't convert the old history and just start fresh. It would have
practically the same effect as you would never be able to get back to a state
where things compiled as they were before the conversion
> I think that's easier than writing svn2git rules for po
t; totally unconnected applications put together in a module.
If you have an interest in kdenetwork apps ending up in split repositories (and
I doubt a lot of people will fight you on that) you can make that so if you
take
the time to write the rulesets for that in the kde-rules reposit
ed on our already existing approuch.
As far as I can see the document doesn't give us any critical or even not very
critical concerns for our current approach.
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
dules since they should be be read-only for translations
anyway.
Did that idea not work out?
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
k those movements yourself in explicit rules.
The difference is that in-module moves are part of history and should be kept
as
moves. Whereas split modules require you to figure thouse out and you
essentially have to rewrite actual history.
--
Thomas Zander
__
n one module) it would be nice if you could write another email
that builds on top of our work and gives hints on small changes that may make
everyones life better.
At least that would avoid discouraging people that already put in a lot of
time and have gone though this discussion too many t
ragear will each have their own
repository. »
For people that want all the details; go here
http://www.gitorious.org/svn2git/kde-ruleset
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
effectively means 2 years of consensus
building and rule writing is thrown away. I don't think I can stumach this
restart of effort and still help out with the conversion.
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
ht
pain to do at the same time.
If you don't want some parts of kdebindings to be part of the big KDE software
collection, then the above strategy makes total sense to me.
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https:
reasons behind that; which I won't repeat here as this is a discussion that
should not be reopened again without really good reasons :-)
As Aaron wrote some time ago; "Its a discussion we had and closed, its decided"
The reasons you cite are not entirely convincing to me,
rn it into a social discussion and git is a great tool to publish
early without all the commitments.
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
downloads :)
My thinking before reading Eikes email was a tarball with a checkout every 2
months and I doubt interim tarballs will be needed as the user can just do a
git pull to fetch the rest till 'today'.
This has the advantage of being able
Could this request be handled by one of you?
--
Thomas Zander
--- Begin Message ---
Sir,
are you the appropriate person to whom I should bring
bugs/issues with svn2git? If not, please disregard the following,
but point me to the appropriate person?
I have a reasonably large (477MB) svn
On Thursday 8. July 2010 15.51.24 Jens-Michael Hoffmann wrote:
> Hi,
>
> I'd like to ask for review of my merge request:
> http://gitorious.org/svn2git/kde-ruleset/merge_requests/2
>
> Or can I just push?
You can just push new files, no prob.
Thanks for working on thi
o see a decision is clearly made is here;
http://gitorious.org/svn2git The sources :-)
The rulesets are the product of the work done by people that, well follow up on
the decision. And they are not splitting modules.
Its a made decision, many many manhours have been going in after that decision
On Sunday 27. June 2010 19.22.34 Tom Albers wrote:
> Ok, but some things have changed since we moved from gitorious to our own
> solution, which might be relevant.
Its not, as long as Git is used all the previous technical details are and stay
relevant.
--
Thomas
> >
> > The advantage is automatic sharing of objects in gc.
>
> Not quite true -- the other advantage is that, if we have the clone on
> the cgit/redmine server pulling all personal branches, it can show those
> personal branches in the code browsers.
Which is also no d
are stalled.
One word; Meritocracy
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
On Tuesday 11. May 2010 22.15.20 Eike Hein wrote:
> On 05/11/2010 10:03 PM, Thomas Zander wrote:
> > What about github?
> > If they can support a git.kde.org a transition to something better (i.e.
> > Free (as in, speech)) can be almost painless.
>
> Github is closed-s
repos to merge in someone elses patches into the
mainline.
But as Chani points out, thats just not practical, gitorious makes it
practical.
If github only does cherry-picking thats kind of a showstopper for me too, to
be honest.
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
opinion.
What about github?
If they can support a git.kde.org a transition to something better (i.e. Free
(as in, speech)) can be almost painless.
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/li
here's a script in the
> kde-ruleset repository in the bin subdir that downloads the repo from
> rsync.
Beware its big. Need some 60Gb free space.
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
On Sunday 28. March 2010 23.48.48 Cornelius Schumacher wrote:
> On Sunday 28 March 2010 Thomas Zander wrote:
> > $ git clone git://gitorious.org/svn2git/kde-ruleset.git
> > $ grep 'create repository' kde-ruleset/*
> >
> > Each of those lines wil
or will
> there be some projects to structure the KDE repositories?
$ git clone git://gitorious.org/svn2git/kde-ruleset.git
$ grep 'create repository' kde-ruleset/*
Each of those lines will be its own project with one or more repositories.
--
Thomas Zander
___
?
Since *all* history is in git, from day one till current day its not gone. Its
still available.
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
of automatic docbook regeneration might
> be a fix for that...only if i had the time to implement it :D
Move it to user base and let it be translated in the wiki :)
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://m
27;m not saying you can't do it, I have no illusions that I can yield that kind
of power. I'm saying its just not very KDE of you if you do.
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
should have plenty of diskspace (70Gb
free at minimum). Bandwidth is close to zero (just ssh) after the initial
clone. Putting up a serious firewall would keep the user from doing silly from
that shell...
Anyone (suse?) able to do something like t
hat might be true for the core modules and
> even extragear apps, this clearly doesn't apply to kdevelop-pg-qt.
I disagree. It does apply.
I suggest you read it all and read the discussion that followed in the
comments, that should make things clearer as I'd just repeat stuff that Aa
2010/02/keeping-it-our-source-code-together.html
In short, by moving this one thing you loose occasional contributors, testers
and essentially mind share. Not because its hard, but because its different
from the rest.
--
Thomas Zander
___
Kde-scm-inte
etting everyone
over, in a coordinated fashion. So the writing of your rules for this project
sounds great, please do so. And use that experience for the writing of the
rules of kdevelop as a bigger part.
The actual uploading of the git repo is something that I hope we can postpone
till the rest of KDE m
paration and coordination for this
move and it seems that got stalled a bit.
Boudewijn (the major backer for this effort) send an email to koffice-devel
yesterday saying we should postpone the KOffice migration pending the SLA
discussions. http://lists.kde.org/?l=koffice-devel&m=126747612
r by shifting the responsibility to
the sysadmins sounds shortsighted IMO.
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
agree on some level of
uptime, some level of support and that we don't get objections about the
amount of traffic we generate. (which could very well violate any fair-use
policies).
In other words; its the responsible thing to do.
I'm hoping that we can keep our schedule of mov
On Thursday 25. February 2010 22.45.40 Andreas Pakulat wrote:
> | match /trunk/KDE/kdevelop
>
All match rules should end with a slash IIRC.
If that works, I'd be very happy if someone made the tool not crash on it ;)
--
Thomas Zander
On Tuesday 23. February 2010 14.46.12 Ian Monroe wrote:
> On Tue, Feb 23, 2010 at 6:37 AM, Thomas Zander wrote:
> > On Monday 22. February 2010 23.37.24 Ian Monroe wrote:
> >> I'm getting
> >> $ svn log -v -r950717 file:///mnt/tera/kde-svn/kde/
> >>
04-07 18:08:25 +0200 (Tue, 07 Apr 2009) | 1 line
Changed paths:
M /trunk/www/sites/edu/marble/newstuff/maps/mars-marblemap.tar.gz
make mars package 0.8.0 proof (remove the MarblePlacemark tags)
On Monday 22. February 2010 04.14.57 Thomas Zander wrote:
> On Monday 22. February 2010 03.23.37 Ian Monroe wrote:
> > I've started a wiki page with the idea that people will post tips and
> > instructions on how to write svn2git import rules.
> > http://gitorious.
t similar to http://gitorious.org/svn2git/pages/Home ?
The gitorious page should be editable by all kde-developers, AFAIK. So feel
free to share content between those two.
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mai
eady existing functionality on gitorious.
Did you report a bug to them?
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
o
smooth.
But at this time its premature.
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
e Amarok people are in contact with the release team AFAIK. There are
example scripts in use from them already. Its just different.
> Get input from the distributions.
Asked several distro people (of various distros ;) on IRC and they were all
perfectly fine with the transfer and preferred n
existing rules to you.
There is zero reason to include him in the equation for hiring a dev. That you
do so anyway just makes you look like you are attacking him personally for
disagreeing with you.
--
Thomas Zander
___
Kde-scm-interest mailing list
Kd
converted history or not (initially) ideal workflows.
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
rying to distract us from actually moving forward.
At this point I frankly don't care anymore if KDE splits modules or not. What
I care about is that this effort is loosing people faster than a sieve loosing
water. If we ever want to get somewhere the bikeshedding has to stop.
--
Thomas Zander
ion not worth
the fringe benefits splitting may bring. C'est La Vie.
So I and many others in KOffice think that its time to move KOffice to git.
1) http://gitorious.org/svn2git
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-intere
go was pretty much spot on.
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
tely loose all atomicity
falls under the bell-curve argument.
It doesn't apply to the subject on the table.
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
ffice/kword
User B backports to the stable branch this fix by applying the change made on
koffice/kword but never notices that the change in koffice/libs is needed too
because that added some API.
He commits & stable branch doesn't compile anymore.
--
Thomas Zander
in your app will cause cmake to compile your
libs dir first, as it depends on that.
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
x27;its
modified in dir A, not in dir B' part. I'd rather avoid having submodules as
they really are a PITA to work with.
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
cmake variable ;)
This topic is closed for me, really, we closed it before, no new info has been
brought to the table.
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
me up before, we talked about it extensively and
while we have some people that like it, nobody wanted to put the work in and I
think the advantages are just not clear (to me at least).
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
nvolves fixing a lot of conflicts and also testing things a lot, and
> therefore can only be done sanely on individual commits, and not on a merge
> of dozens of commits.
Read the manpage of git merge; it allows you to do this trivially as you can
specify what you want to merge.
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
our new project on gitorious, but then wait for
the rest of KDE to migrate before getting the hooks and the translations etc.
Essentially, wait for KDE to move to git before your new project can be part
of the KDE community.
Cheers!
--
Thomas Zander
___
essentially
identical to the way people worked together in svn and before that in cvs.
This is, btw, one reason to have the same modules in git as we had in svn...
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
-devel or somesuch? I
think its entirely unfair to decide on such a fundamental change away from
what has been the KDE way for many years without a much broader consensus.
In fact, its just Ossi that has this view, isn't it?
--
Thomas Zander
On Saturday 12. December 2009 16.07.21 Oswald Buddenhagen wrote:
> On Sat, Dec 12, 2009 at 03:54:45PM +0100, Thomas Zander wrote:
> > On Saturday 12. December 2009 15.45.10 Oswald Buddenhagen wrote:
> > > yeah, and now back to reality. ;)
> >
> > I may be dreaming,
On Saturday 12. December 2009 15.45.10 Oswald Buddenhagen wrote:
> yeah, and now back to reality. ;)
I may be dreaming, but in the KDE I've worked in for the last 10 years this
worked out pretty well.
--
Thomas Zander
___
Kde-scm-interest mail
On Saturday 12. December 2009 12.07.53 Oswald Buddenhagen wrote:
> On Sat, Dec 12, 2009 at 11:19:20AM +0100, Thomas Zander wrote:
> > On Saturday 12. December 2009 11.07.58 Oswald Buddenhagen wrote:
> > > > likewise, we want all devs to be able to comment on and otherwise
&
hands of the maintainers of the respective
> subproject. it has never been different in kde
How is there a technical limitation in kde currently for the integration of
patches?
I only see the social one.
--
Thomas Zander
___
Kde-scm-interest ma
ive apps.
>
> * = The "amarok-developers" team originally had other
> uses, then got abandoned, and now repurposed, hence
> the "-developers" suffix. The intention is to rename
> it to "-reviewers" if possible or
ojects mainline or stable branch and do any sort of merging etc.
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
us within the group of people that really want it.
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
and naturally
the "gitorious is slow!" problems.
So I think that would be useful for us to investigate, indeed.
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
n gitorious (did you know its open source?) to help
*everyone* get there, then I'd argue they are indeed clearly part of the
community called KDE.
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
On Thursday 12. November 2009 19.41.21 Thomas Zander wrote:
> As some movement has been detected I want to point out that the work Thiago
> did for the svn-fast-export has been extended by me and moved to gitorious;
>
> http://gitorious.org/svn2git
>
> Be sure to also read the w
. In practice I don't think you'll have
to see this problem.
There is an open feature request on gitorious to fix this issue, btw. (with a
proposed solution) So, yes, the general problem is known and should be looked
at.
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
ldudtt
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
, it has a couple of usecases (the most
complicated ones, for sure) that I ask we verify work.
In essence, if 3 years from now I find a commit with your email address on it,
how will I figure out who actually pushed it. Thats all.
--
Thomas Zander
___
Kde
we can
compare on merit. Or, rather, "Show me the money!" [2].
The proposal for splitting has been on the table for the last 2 years. Please
produce a counter proposal if you think you can do better.
1) http://lists.kde.org/?l=kde-scm-interest&m=12019324153215
required, AFAICT. How its recorded and
backupped/shared is the topic I wanted to put on the agenda.
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
ou can get from a git clone...
This is similar to what the earlier proposal Thiago and me suggested, yes.
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
directories (and remember that even reverted accidental imports have an
> irreversible impact on every single clone).
We have done all the benchmarks and research, and we reached a quite
different conclusion from yours.
--
Thomas Zander
___
Kde-scm-i
On Friday 13. November 2009 11.51.04 Oswald Buddenhagen wrote:
> On Thu, Nov 12, 2009 at 08:23:54PM +0100, Thomas Zander wrote:
> > On Thursday 12. November 2009 20.02.44 Oswald Buddenhagen wrote:
> > > disadvantages of big repos:
> > > - huge clones for everyb
t want to ok to the opt-in?
I hate to bring up these pesky legal and accountability issues but I think
they should be fixed before we start working on this new platform at-large. I
hope you agree.
--
Thomas Zander
___
Kde-scm-interest mailing list
to do that?
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
ok-ed for inclusion in one of the big modules its entirely
possible to move it in there without loss of history.
But all this is not really an issue for the conversion, this is an issue to
discuss after we moved to Git and it likely not be decided on this list.
--
Thomas Zander
___
ad an svn account has his info publicly available
(see accounts files), whats different on gitorious that there is a privacy
issue?
--
Thomas Zander
signature.asc
Description: This is a digitally signed message part.
___
Kde-scm-interest mailing
only
once in many months. Combined with the fact that one push can contain a lot
of commits a quick glance at the commit logs show that this is at worst a
minor annoyance.
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
ore work which leads to
b) someone should do the work of splitting and of fixing a tool like 'repo'
to be useful for us.
point [b] is not trivial, but if you care for this issue you might want to
start now so we get a long way in the short time we have before the r
ld like to know more about and that may be in
the log already.
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
),
though I extended the KOffice export rules slightly. (which are on my machine
at work that I can't reach till monday)
The question on my mind is where to put those rules.
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
On Wednesday 30. September 2009 21.53.56 Jens-Michael Hoffmann wrote:
> Is this really necessary? If yes, why?
Because KWord doesn't have a wiki import/exporter? :)
Volunteers welcome!
--
Thomas Zander
Qt Developer Days 2009 | Save your seat - REGISTER NOW!
Munich, Germany: October 12t
nation.
Any assumptions about correctness-checks, logging being complete etc all go
out the window if you can't be certain that the http call will 100% if the
time be completed correctly.
If gitorious.org doesn't allow kde-written post-commit hooks, gitorious.org
is useless to
;private' clone and he pushes to it.
After a couple of weeks and maybe more committers on this little project we
merge it into mainline via a normal local git command and I personally can
push it to mainline in the master branch.
--
Thomas Zander
_
ffice/doc then?
* stuff like dirks dashboard would continue working without rewrite.
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
y a
requirement. More a "may be nice to have".
Though I could see how its actually more hassle than its worth to many.
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
really feel git has a
horrible UI for simple things.
--
Thomas Zander
signature.asc
Description: This is a digitally signed message part.
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
On Friday 29. May 2009 00.34.47 Albert Astals Cid wrote:
> Well, everyone keeps saying "We are loosing developers because of SVN",
> can't I extend that to "We are loosing developers because of
> CURRENT_VCS"?
only if CURENT_VCS equals svn. Wha
ou should just rebase to keep a clean and simple history.
--
Thomas Zander
signature.asc
Description: This is a digitally signed message part.
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
27;t checkout since it would
have to overwrite the file.
--
Thomas Zander
signature.asc
Description: This is a digitally signed message part.
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
seems a bit odd to me; an opt-out solution. Not solving the
problem but avoiding it with the side effect of having to keep an svn server
up and running :/
So, like Matt I was under the impression we wanted to port script to
basically do exactly what it did before, but now usi
On Thursday 21. May 2009 10.52.50 Oswald Buddenhagen wrote:
> actually, i am wondering whether we really want scripty to modify
> .desktop files.
Lets not try to change KDE policies and ways of working and keep this list
to its scope of introducing a new choice for KDE.
--
Thomas
server.
it still requires some research and writing of scripts; see this mail
http://lists.kde.org/?l=kde-scm-interest&m=121751052701010&w=2
--
Thomas Zander
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
ution for
switching to another scm we can propose that for wider adoption. To have a
good chance of getting acceptance the amount of changes should be minimal.
Therefor the topic you brought up just doesn't belong on this list.
--
Thomas Zander
__
1 - 100 of 113 matches
Mail list logo
