Alexander Neundorf wrote:
> Maybe something has to be done in git ?
> (basically all tools which get introduced to KDE have a fixing/feature
> addition phase initially ;-)
>
> Alex
Yes, this issue comes up on the git mailing list from time to time.
http://thread.gmane.org/gmane.comp.version-con
Tom Albers wrote:
- Original Message -
On Saturday, February 12, 2011 19:12:41 Tom Albers wrote:
- Original Message -
Hi,
Our default wallpapers used to be part of kdebase/workspace, but
during
the git migration they've been removed from workspace due the size
of
that directo
On Saturday 12 February 2011, Tom Albers wrote:
> - Original Message -
>
> > On Saturday, February 12, 2011 19:12:41 Tom Albers wrote:
> > > - Original Message -
> > >
> > > > Hi,
> > > >
> > > > Our default wallpapers used to be part of kdebase/workspace,
> > > > but during
> >
Hi,
On 02/12/11 20:12, Tom Albers wrote:
> Maybe just a tarball somewhere? SVN won't stay around, so we need another
> solution i think.
>
So probably we have to move it to a wallpapers git repository, anyway
until SVN is active we can continue to use it.
Bye,
Davide Bettio.
signature.asc
De
On Saturday 12 February 2011, Tom Albers wrote:
> - Original Message -
>
> > On Saturday, February 12, 2011 19:12:41 Tom Albers wrote:
> > > - Original Message -
> > >
> > > > Hi,
> > > >
> > > > Our default wallpapers used to be part of kdebase/workspace, but
> > > > during
> > > >
- Original Message -
> On Saturday, February 12, 2011 19:12:41 Tom Albers wrote:
> > - Original Message -
> >
> > > Hi,
> > >
> > > Our default wallpapers used to be part of kdebase/workspace, but
> > > during
> > > the git migration they've been removed from workspace due the size
On Saturday, February 12, 2011 19:12:41 Tom Albers wrote:
> - Original Message -
>
> > Hi,
> >
> > Our default wallpapers used to be part of kdebase/workspace, but
> > during
> > the git migration they've been removed from workspace due the size of
> > that directory.
> > Wallpapers can't
- Original Message -
> Hi,
>
> Our default wallpapers used to be part of kdebase/workspace, but
> during
> the git migration they've been removed from workspace due the size of
> that directory.
> Wallpapers can't be kept in a git repository because every time a git
> repository is cloned
Hi,
On 02/11/11 22:44, Ingo Klöcker wrote:
>> Since that location in SVN is now a bit obscure, perhaps we should
>> create a new SVN module called trunk/KDE/kdebase-wallpapers.
> kde-wallpapers? Because ...
>
>> The context here is that: SVN is just better then Git at storing
>> stuff like wallpap
2011/2/11 Ingo Klöcker :
> On Friday 11 February 2011, Ian Monroe wrote:
>> On Fri, Feb 11, 2011 at 14:06, Davide Bettio wrote:
>> > Hi,
>> >
>> > Our default wallpapers used to be part of kdebase/workspace, but
>> > during the git migration they've been removed from workspace due
>> > the size of
On Friday 11 February 2011, Ian Monroe wrote:
> On Fri, Feb 11, 2011 at 14:06, Davide Bettio wrote:
> > Hi,
> >
> > Our default wallpapers used to be part of kdebase/workspace, but
> > during the git migration they've been removed from workspace due
> > the size of that directory.
> > Wallpapers
On Fri, Feb 11, 2011 at 14:06, Davide Bettio wrote:
> Hi,
>
> Our default wallpapers used to be part of kdebase/workspace, but during
> the git migration they've been removed from workspace due the size of
> that directory.
> Wallpapers can't be kept in a git repository because every time a git
>
Hi,
Our default wallpapers used to be part of kdebase/workspace, but during
the git migration they've been removed from workspace due the size of
that directory.
Wallpapers can't be kept in a git repository because every time a git
repository is cloned all the history (including old wallpapers) is
On Sunday, January 23, 2011, Allen Winter wrote:
> On Tuesday 18 January 2011 6:15:04 pm Aaron J. Seigo wrote:
> > On Tuesday, January 18, 2011, Allen Winter wrote:
> > > On Tuesday 18 January 2011 4:34:21 pm Aaron J. Seigo wrote:
> > > > hi all ...
> > > >
> > > > when looking at migrating kdebas
On Tuesday 18 January 2011 6:15:04 pm Aaron J. Seigo wrote:
> On Tuesday, January 18, 2011, Allen Winter wrote:
> > On Tuesday 18 January 2011 4:34:21 pm Aaron J. Seigo wrote:
> > > hi all ...
> > >
> > > when looking at migrating kdebase to git (thanks to Ian Monroe for his
> > > efforts there an
On Friday, January 21, 2011, Torgny Nyblom wrote:
> On Friday 21 January 2011 22.44.49 Ben Cooksley wrote:
> > This is completely unpalatable in terms of security and technical on
> > KDE servers in my opinion as a sysadmin. Not sure what the others
> > think of it however.
>
> We use it at work
On Friday 21 January 2011 22.44.49 Ben Cooksley wrote:
> On Fri, Jan 21, 2011 at 11:17 AM, Aaron J. Seigo wrote:
> > On Thursday, January 20, 2011, Ben Cooksley wrote:
> >> Correct, it is Gerrit which is a more git based alternative to
> >> Reviewboard. http://code.google.com/p/gerrit/
> >
> > do
On Fri, Jan 21, 2011 at 11:17 AM, Aaron J. Seigo wrote:
> On Thursday, January 20, 2011, Ben Cooksley wrote:
>> Correct, it is Gerrit which is a more git based alternative to Reviewboard.
>> http://code.google.com/p/gerrit/
>
> does it have benefits over reviewboard? having just toyed with a bit a
On Thursday, January 20, 2011, Ben Cooksley wrote:
> Correct, it is Gerrit which is a more git based alternative to Reviewboard.
> http://code.google.com/p/gerrit/
does it have benefits over reviewboard? having just toyed with a bit after
lunch today, it seems like it's useful to drive the entire
2011/1/21 Alexander Neundorf :
> On Thursday 20 January 2011, Aaron J. Seigo wrote:
>> On Wednesday, January 19, 2011, Alexander Neundorf wrote:
>> > http://community.kde.org/Sysadmin/GitKdeOrgManual looks quite ok for
>> > somebody who knows how to use git for KDE, but not for me.
>> > Can somebod
On 20.01.11 19:47:22, Alexander Neundorf wrote:
> On Thursday 20 January 2011, Tom Albers wrote:
> > - Original Message -
> >
> > > On Wed, Jan 19, 2011 at 03:33:30PM -0600, Ian Monroe wrote:
> > > > There is no push/merge/branching policy for KDE. Different projects
> > > > will likely do
2011/1/20 Alexander Neundorf:
> As long as there is no policy defined, I simply try to push/merge to the
> respective master ?
> I also think that really most/all new KDE git repositories should use a common
> workflow.
I think this is a reasonable expectation for all repositories that are
part of
On Thursday 20 January 2011, Aaron J. Seigo wrote:
> On Wednesday, January 19, 2011, Alexander Neundorf wrote:
> > http://community.kde.org/Sysadmin/GitKdeOrgManual looks quite ok for
> > somebody who knows how to use git for KDE, but not for me.
> > Can somebody please add a simple step-by-step ho
On Thursday 20 January 2011, Tom Albers wrote:
> - Original Message -
>
> > On Wed, Jan 19, 2011 at 03:33:30PM -0600, Ian Monroe wrote:
> > > There is no push/merge/branching policy for KDE. Different projects
> > > will likely do their own thing. For the time being its just the
> > > SVN-s
On Thursday, January 20, 2011, Aaron J. Seigo wrote:
> On Wednesday, January 19, 2011, Alexander Neundorf wrote:
> > http://community.kde.org/Sysadmin/GitKdeOrgManual looks quite ok for
> > somebody who knows how to use git for KDE, but not for me.
> > Can somebody please add a simple step-by-step
On Wednesday, January 19, 2011, Alexander Neundorf wrote:
> http://community.kde.org/Sysadmin/GitKdeOrgManual looks quite ok for
> somebody who knows how to use git for KDE, but not for me.
> Can somebody please add a simple step-by-step howto, what I have to do with
> identity.kde.org, projects.kd
On Thursday, January 20, 2011, Oswald Buddenhagen wrote:
> On Wed, Jan 19, 2011 at 03:33:30PM -0600, Ian Monroe wrote:
> > There is no push/merge/branching policy for KDE. Different projects
> > will likely do their own thing. For the time being its just the
> > SVN-style development translated to
- Original Message -
> On Wed, Jan 19, 2011 at 03:33:30PM -0600, Ian Monroe wrote:
> > There is no push/merge/branching policy for KDE. Different projects
> > will likely do their own thing. For the time being its just the
> > SVN-style development translated to Git.
> >
> words like "unwis
On Wed, Jan 19, 2011 at 03:33:30PM -0600, Ian Monroe wrote:
> There is no push/merge/branching policy for KDE. Different projects
> will likely do their own thing. For the time being its just the
> SVN-style development translated to Git.
>
words like "unwise", "stupid" and "utterly braindead" com
2011/1/19 Alexander Neundorf :
> Hi,
>
> now that it's getting serious, can somebody who is working on the git
> migration, *please* take care and write proper documentation on
> techbase.kde.org for git dummies ?
>
> http://techbase.kde.org/Development/Tutorials/Git , which is the first google
> r
Hi,
now that it's getting serious, can somebody who is working on the git
migration, *please* take care and write proper documentation on
techbase.kde.org for git dummies ?
http://techbase.kde.org/Development/Tutorials/Git , which is the first google
result, and looks like a gateway page, has
On 18 January 2011 23:55, Aaron J. Seigo wrote:
>> Oh, what happened to the idea of making kde-workspace-libs a
>> standalone repo? Wouldn't that make sense?
>
> it could be done, but there was no use case for that. keeping the repos
> together lets us not worry so much about binary compat, too
On Tuesday, January 18, 2011, John Tapsell wrote:
> On 18 January 2011 23:13, Aaron J. Seigo wrote:
> > the complication there is that krunner also relies on libksyguard, which
> > lives in kdebase/workspace/libs/ksysguard. so we'd either end up with a
> > really odd dependency in ksysguard on kde
On 18 January 2011 23:13, Aaron J. Seigo wrote:
> the complication there is that krunner also relies on libksyguard, which lives
> in kdebase/workspace/libs/ksysguard. so we'd either end up with a really odd
> dependency in ksysguard on kde-workspace, or kde-workspace would end up
> depending on t
On Tuesday, January 18, 2011, Allen Winter wrote:
> On Tuesday 18 January 2011 4:34:21 pm Aaron J. Seigo wrote:
> > hi all ...
> >
> > when looking at migrating kdebase to git (thanks to Ian Monroe for his
> > efforts there and for the support of KO Gmbh that helped make that
> > happen), it was d
On Tuesday, January 18, 2011, John Tapsell wrote:
> On 18 January 2011 21:34, Aaron J. Seigo wrote:
> > konsole, however, is a significant application in its own right that
> > doesn't actually share code with the rest of the apps in there (besides
> > Qt, kdelibs and runtime, of course ;). so it
On 18 January 2011 22:05, Allen Winter wrote:
> Having konsole, ksysguard, etc in their own git repo is fine.
> But they still will reside logically inside kdebase-apps
>
> For example on api.kde.org the EBN and LXR.
That's sounds great.
John
On Tuesday 18 January 2011 4:34:21 pm Aaron J. Seigo wrote:
> hi all ...
>
> when looking at migrating kdebase to git (thanks to Ian Monroe for his
> efforts
> there and for the support of KO Gmbh that helped make that happen), it was
> decided to split it up into chunks which are:
>
> * kdeba
On 18 January 2011 21:34, Aaron J. Seigo wrote:
> konsole, however, is a significant application in its own right that doesn't
> actually share code with the rest of the apps in there (besides Qt, kdelibs
> and runtime, of course ;). so it is getting its own repo.
>
> if there are any questions /
hi all ...
when looking at migrating kdebase to git (thanks to Ian Monroe for his efforts
there and for the support of KO Gmbh that helped make that happen), it was
decided to split it up into chunks which are:
* kdebase runtime (git -> kderuntime)
* kdebase workspace (git -> kdeworkspace)
* kd
40 matches
Mail list logo
