On Saturday 09 July 2011, Alexander Neundorf wrote:
> On Saturday 09 July 2011, Allen Winter wrote:
> ...
>
> > Done:
> > + MacroOptionalAddSubdirectory.cmake renamed to
> > ECMOptionalAddSubdirectory.cmake and moved up into modules. +
> > MacroOptionalFindPackage.cmake removed from attic
>
> Coo
On Saturday 09 July 2011, Allen Winter wrote:
...
> Done:
> + MacroOptionalAddSubdirectory.cmake renamed to
> ECMOptionalAddSubdirectory.cmake and moved up into modules. +
> MacroOptionalFindPackage.cmake removed from attic
Cool :-)
And how did you do that exactly ?
As Sune described or some othe
On Saturday 09 July 2011 7:03:15 AM you wrote:
> On Saturday 09 July 2011, Allen Winter wrote:
> > On Friday 08 July 2011 4:00:16 PM you wrote:
> > > On Friday 01 July 2011, Allen Winter wrote:
> > > > Done.
> > > > Except I screwed-up the history somewhat.
> > > > To see the history of a file you
On Saturday 09 July 2011 13:03:15 Alexander Neundorf wrote:
> A new top-level subdir modules/ sounds good.
> git doesn't have "mv" or "cp" commands, right ?
Git does have a mv command, but git is also smart enough:
$ mv group group2
$ git add group2
$ git add -p
[snip]
$ git commit -m"blah"
[mast
On Saturday 09 July 2011, Allen Winter wrote:
> On Friday 08 July 2011 4:00:16 PM you wrote:
> > On Friday 01 July 2011, Allen Winter wrote:
> > > Done.
> > > Except I screwed-up the history somewhat.
> > > To see the history of a file you need to use the --follow option.
> > >
> > > eg. git log -
On Friday 08 July 2011 4:00:16 PM you wrote:
> On Friday 01 July 2011, Allen Winter wrote:
> > Done.
> > Except I screwed-up the history somewhat.
> > To see the history of a file you need to use the --follow option.
> >
> > eg. git log --follow attic/modules/FindNepomuk.cmake
>
> Ok.
> Now I thi
On Friday 01 July 2011, Allen Winter wrote:
> Done.
> Except I screwed-up the history somewhat.
> To see the history of a file you need to use the --follow option.
>
> eg. git log --follow attic/modules/FindNepomuk.cmake
Ok.
Now I think MacroOptionalAddSubdirectory.cmake should be in e-c-m, but r
Done.
Except I screwed-up the history somewhat.
To see the history of a file you need to use the --follow option.
eg. git log --follow attic/modules/FindNepomuk.cmake
On Thursday, June 30, 2011 04:17:17 pm Alexander Neundorf wrote:
> On Thursday 30 June 2011, Allen Winter wrote:
> > On Wednesday
On Thursday 30 June 2011, Allen Winter wrote:
> On Wednesday 29 June 2011 3:10:56 PM Alexander Neundorf wrote:
...
> > Yes.
> > Is there a special "reset" or simply git rm all files ?
>
> Aww .. gee... I actually spent quite some time figuring out how to copy
> these over without losing history. H
On Wednesday 29 June 2011, Pavel Heimlich, a.k.a. hajma wrote:
> 2011/6/29 Allen Winter :
> > Howdy,
> >
> > I copied the current kdelibs/cmake into extra-cmake-modules.
> > History should be retained.
> >
> > So now we need to start hacking away.
>
> Hi,
> is there an easy way to mass-test all
On Wednesday 29 June 2011 3:10:56 PM Alexander Neundorf wrote:
> On Wednesday 29 June 2011, Michael Jansen wrote:
> > On Wednesday 29 June 2011 20:17:53 Alexander Neundorf wrote:
> > > Hi,
> > >
> > > I guess I should explain a bit more what's behind the idea of
> > > extra-cmake- modules.
> > >
2011/6/29 Allen Winter :
> Howdy,
>
> I copied the current kdelibs/cmake into extra-cmake-modules.
> History should be retained.
>
> So now we need to start hacking away.
Hi,
is there an easy way to mass-test all the modules?
I imagine I would run them all on my KDE build machine and I would
only
On Wednesday 29 June 2011, Alexander Neundorf wrote:
> Hi,
>
> I guess I should explain a bit more what's behind the idea of extra-cmake-
> modules.
...
> As plan I would
> - go through the list from Raphael again and insert some more details
Done for most files except all Find-modules (they can
On Wednesday 29 June 2011, Michael Jansen wrote:
> On Wednesday 29 June 2011 20:17:53 Alexander Neundorf wrote:
> > Hi,
> >
> > I guess I should explain a bit more what's behind the idea of
> > extra-cmake- modules.
> >
> > There were two big topics at the Platform sprint in Randa: Qt5, and how
>
On Wednesday 29 June 2011 20:17:53 Alexander Neundorf wrote:
> Hi,
>
> I guess I should explain a bit more what's behind the idea of extra-cmake-
> modules.
>
> There were two big topics at the Platform sprint in Randa: Qt5, and how to
> make KDE libraries better available for Qt-only software.
>
Hi,
I guess I should explain a bit more what's behind the idea of extra-cmake-
modules.
There were two big topics at the Platform sprint in Randa: Qt5, and how to
make KDE libraries better available for Qt-only software.
Qt5 will break binary compatibility, and will try to stay 100% source
com
On Wednesday 29 June 2011 09:28:35 Allen Winter wrote:
> Howdy,
>
> I copied the current kdelibs/cmake into extra-cmake-modules.
> History should be retained.
>
> So now we need to start hacking away.
>
> Raphael, would it be possible to put your tables into a plain-ordinary-text
> file in the r
Howdy,
I copied the current kdelibs/cmake into extra-cmake-modules.
History should be retained.
So now we need to start hacking away.
Raphael, would it be possible to put your tables into a plain-ordinary-text
file in the repo?
If not too much trouble.
-Allen
___
18 matches
Mail list logo
