On Wednesday, 2 de February de 2011 05:58:35 John Tapsell wrote:
> git rebase -i origin #Bring up a list of your changes.
>
> the top of the list, save>
>
>
>
> git pull --rebase #make sure we are up to date
>
> git log #copy the SHA of the commit you want to push up to
Hint:
On Wed, Feb 2, 2011 at 2:02 AM, Kevin Ottens wrote:
> On Wednesday 2 February 2011 07:21:44 Dawit A wrote:
>> On Wed, Feb 2, 2011 at 12:58 AM, John Tapsell wrote:
>> >> But how would a similar work flow except there are multiple fixes
>> >> present in the local repo ? How would you push only a si
On Wednesday 2 February 2011 07:21:44 Dawit A wrote:
> On Wed, Feb 2, 2011 at 12:58 AM, John Tapsell wrote:
> >> But how would a similar work flow except there are multiple fixes
> >> present in the local repo ? How would you push only a single fix in
> >> such case ?
> >
> > git rebase -i origin
On Tuesday 1 February 2011 23:06:47 Aaron J. Seigo wrote:
> On Tuesday, February 1, 2011, Stefan Majewsky wrote:
> > On Tue, Feb 1, 2011 at 10:22 PM, Aaron J. Seigo wrote:
> > > then i learned today to be extra vigilant about doing `git pull
> > > --rebase` and not just `git pull` so i don't accid
On Wed, Feb 2, 2011 at 12:58 AM, John Tapsell wrote:
>> But how would a similar work flow except there are multiple fixes
>> present in the local repo ? How would you push only a single fix in
>> such case ?
>
> git rebase -i origin #Bring up a list of your changes.
>
> the top of the list, sav
> But how would a similar work flow except there are multiple fixes
> present in the local repo ? How would you push only a single fix in
> such case ?
git rebase -i origin #Bring up a list of your changes.
git pull --rebase #make sure we are up to date
git log #copy the SHA of the
On Tue, Feb 1, 2011 at 4:22 PM, Aaron J. Seigo wrote:
> On Tuesday, February 1, 2011, Alexander Neundorf wrote:
>> On Monday 31 January 2011, Andreas Pakulat wrote:
>> > Hi,
>> >
>> > something that hasn't been written down as far as I can see (if I
>> > overlooked it, please point me to it) is wh
On Tuesday, February 01, 2011 19:14:34 Andreas Pakulat wrote:
> Once you know it puts that into the PATHS option the rest is a mere look
> at the cmake manual
As soon as you mentioned having to dive into the CMake manual to make
something work you have lost a fair amount of bleeding edge testers
On Tue, Feb 1, 2011 at 6:43 PM, Michael Jansen wrote:
>
>
>> I guess this is not really the point of your discussion, but a rather
>> a bad example you used...
>
> Really? I meant it as an example that without compiling kwebkitpart before
> kdebase you didn't get support for it in konqueror. Which
On 01.02.11 23:14:26, Michael Jansen wrote:
> > > > Do you need that for running ?
> > > > For building it's not necessary. Use CMAKE_PREFIX_PATH.
> > >
> > > I always thought that PATH controls which qt version is selected if you
> > > have more than one (First qmake found). It was that way some
On 01.02.11 14:06:47, Aaron J. Seigo wrote:
> On Tuesday, February 1, 2011, Stefan Majewsky wrote:
> > On Tue, Feb 1, 2011 at 10:22 PM, Aaron J. Seigo wrote:
> > > then i learned today to be extra vigilant about doing `git pull --rebase`
> > > and not just `git pull` so i don't accidentally throw
2011/2/1 Nicolás Alvarez :
> On 01/02/2011, George Goldberg wrote:
>> On 1 February 2011 12:01, Tom Albers wrote:
>>> The monthly overview
>>>
>>> - Forwarded Message -
342 decibel
>>
>> I think it's safe to kill this list. The project has been in the land
>> of the unmaintained
> I guess this is not really the point of your discussion, but a rather
> a bad example you used...
Really? I meant it as an example that without compiling kwebkitpart before
kdebase you didn't get support for it in konqueror. Which you acknowledge if i
read your mail correctly happened at a t
On Tue, Feb 1, 2011 at 4:14 PM, Michael Jansen wrote:
>
>> a. nope. kwebkitpart only depends on kdelibs! There are no
>> requirements besides that. The previous requirement that you must
>> build kwebkitpart before you compiled the konq-plugins, which have now
>> been moved to kdebase, is now
On Tuesday 01 February 2011 21:37:26 Aaron J. Seigo wrote:
> so i'd like to suggest that we gather on irc in the near future and hammer
> this stuff out. weekends tend to be better for many it seems, so i've put
> up a doodle here:
Fantastic :-) Just to point out that FOSDEM is this weekend, so m
On Tuesday 01 February 2011 13:45:27 George Goldberg wrote:
> >> 41 kdelibs-bugs
>
> This is a very useful list for bug triagers - I can volunteer to
> moderate it if no-one else is currently doing it.
ditto, if more than 1 or 2 mods are needed.
John.
On Tuesday 01 February 2011 17:14:05 Artur de Souza wrote:
> Quoting Tom Albers :
> >> 80 kmobiletools
> >> 20 kde-embedded
>
> We already have kde-mobile...maybe it's safe to remove these two
> mailing lists?
kmobiletools is actually an app for syncing your phone, not part of the
mobile/embedde
On Tuesday, February 1, 2011, Harri Porten wrote:
> On Tue, 1 Feb 2011, Aaron J. Seigo wrote:
> > we could end up with a "new kdelibs" module that contains just the core
> > stuff such as kdecore, kdeui, kio .. there could be requirements in
> > there about allowable dependencies between those libr
On Tue, 1 Feb 2011, Aaron J. Seigo wrote:
we could end up with a "new kdelibs" module that contains just the core stuff
such as kdecore, kdeui, kio .. there could be requirements in there about
allowable dependencies between those libraries.
[...]
the big change here would be that applications
> If you find the place let me know.
No ... only if i am unable to fix it myself :)) .
> > > Do you need that for running ?
> > > For building it's not necessary. Use CMAKE_PREFIX_PATH.
> >
> > I always thought that PATH controls which qt version is selected if you
> > have more than one (First
On Tuesday, February 1, 2011, Stefan Majewsky wrote:
> On Tue, Feb 1, 2011 at 10:22 PM, Aaron J. Seigo wrote:
> > then i learned today to be extra vigilant about doing `git pull --rebase`
> > and not just `git pull` so i don't accidentally throw merge commits in
> > there while preping for a push.
On Tuesday 01 February 2011, Michael Jansen wrote:
...
> > > kdesupport? anyone ... perhaps qt from trunk or qtsoftware to get
> > > problems as early as possible?
> >
> > I was asking specifically about "KDE" stuff, i.e. everything starting
> > with kdelibs, not stuff kdelibs depends on (which I a
On Tuesday, February 1, 2011, Alexander Neundorf wrote:
> I can remember that a point of criticism about gnome was that it is hard to
> get it built correctly with all the relatively small independent libs.
> I think we are moving in that direction...
> Are we aware of this and is this ok with us ?
On Tuesday, February 1, 2011, Maksim Orlovich wrote:
> On 2/1/11, Andreas Pakulat wrote:
> > On 01.02.11 19:49:10, Albert Astals Cid wrote:
> >
> > No, the natural fix is to make the dependency chain proper, i.e. KTE
> > depends on kdelibs, khtml depends on KTE+kdelibs. That means khtml
> > canno
hi everyone ...
with git having finally arrived more-or-less, we find ourselves without a well
defined work flow for kdelibs (and by extension other KDE repositories)
i don't think we can or should hope and pray that our sysadmins will perform
another magic trick and solve this for us, nor can
On Tue, Feb 1, 2011 at 10:22 PM, Aaron J. Seigo wrote:
> then i learned today to be extra vigilant about doing `git pull --rebase` and
> not just `git pull` so i don't accidentally throw merge commits in there while
> preping for a push.
Look in man git-config for "branch.autosetuprebase". I thin
> > So want Aaaron and me to miss out on kwebkit and scripting, and
> > policykit
> > and rekonq and ... konsole? How do you suppose to use your system
> > without
> > konsole.
>
> Yes, with git this has become more stuff.
build-tool is able to compile more than 100 Modules. And run the stuff.
On Tuesday, February 1, 2011, Alexander Neundorf wrote:
> On Monday 31 January 2011, Andreas Pakulat wrote:
> > Hi,
> >
> > something that hasn't been written down as far as I can see (if I
> > overlooked it, please point me to it) is what the policy on kdelibs is
> > to be now wrt. merging vs. ch
On 2/1/11, Andreas Pakulat wrote:
> On 01.02.11 19:49:10, Albert Astals Cid wrote:
> No, the natural fix is to make the dependency chain proper, i.e. KTE
> depends on kdelibs, khtml depends on KTE+kdelibs. That means khtml
> cannot be part of kdelibs anymore if KTE is not part of kdelibs anymore.
> a. nope. kwebkitpart only depends on kdelibs! There are no
> requirements besides that. The previous requirement that you must
> build kwebkitpart before you compiled the konq-plugins, which have now
> been moved to kdebase, is now longer valid because of the addition of
> several Extentsion
On Tue, Feb 1, 2011 at 1:55 PM, Friedrich W. H. Kossebau
wrote:
> Mardi, le 1 février 2011, à 19:39, Sune Vuorela a écrit:
>> On 2011-02-01, Friedrich W. H. Kossebau wrote:
>> >> And I'm not sure there should be
>> >> such a thing.
>> >
>> > Hm. You don't agree that a user experience like
>> >
>>
On Tue, Feb 1, 2011 at 2:58 PM, Michael Jansen wrote:
> On Tuesday 01 February 2011 20:35:27 Alexander Neundorf wrote:
>> On Tuesday 01 February 2011, Michael Jansen wrote:
>> > On Tuesday 01 February 2011 19:53:40 Alexander Neundorf wrote:
>> > > On Monday 31 January 2011, Aaron J. Seigo wrote:
>
On Tuesday 01 February 2011, Michael Jansen wrote:
> On Tuesday 01 February 2011 20:35:27 Alexander Neundorf wrote:
> > On Tuesday 01 February 2011, Michael Jansen wrote:
> > > On Tuesday 01 February 2011 19:53:40 Alexander Neundorf wrote:
> > > > On Monday 31 January 2011, Aaron J. Seigo wrote:
>
On Tuesday 01 February 2011, Andreas Pakulat wrote:
> On 01.02.11 19:49:10, Albert Astals Cid wrote:
> > A Dimarts, 1 de febrer de 2011, Ian Monroe va escriure:
> > > On Mon, Jan 31, 2011 at 21:19, Aaron J. Seigo wrote:
> > > >[snip]
> > > >
> > > > oh well, KTextEditor isn't an option,
> > >
> >
On Tuesday, February 1, 2011, Pino Toscano wrote:
> Alle venerdì 28 gennaio 2011, Nicolas Alvarez ha scritto:
> > What do you all think of removing wallpapers from these git
> > repositories? We could put them in a separate git repository, or
> > even keep them in SVN.
>
> Now that the workspace r
On 01.02.11 19:49:10, Albert Astals Cid wrote:
> A Dimarts, 1 de febrer de 2011, Ian Monroe va escriure:
> > On Mon, Jan 31, 2011 at 21:19, Aaron J. Seigo wrote:
> > >[snip]
> > >
> > > oh well, KTextEditor isn't an option,
> >
> > Should we give up so easily on this? The whole point of modulariz
On Tuesday 01 February 2011, Artur de Souza wrote:
> Hello!
>
> I would like to inform that the move of kdeplasma-addons to git and
> completed successfully.
> Now you can find the new repository in:
>
> git clone git://anongit.kde.org/kdeplasma-addons
>
> Thanks a lot to eean for the help and t
On Tuesday 01 February 2011 20:35:27 Alexander Neundorf wrote:
> On Tuesday 01 February 2011, Michael Jansen wrote:
> > On Tuesday 01 February 2011 19:53:40 Alexander Neundorf wrote:
> > > On Monday 31 January 2011, Aaron J. Seigo wrote:
> > > > On Sunday, January 30, 2011, Michael Pyne wrote:
> >
A Dimarts, 1 de febrer de 2011, Ian Monroe va escriure:
> On Mon, Jan 31, 2011 at 21:19, Aaron J. Seigo wrote:
> >[snip]
> >
> > oh well, KTextEditor isn't an option,
>
> Should we give up so easily on this? The whole point of modularization
> is to remove cross-module dependencies, just like KHT
On Tuesday 01 February 2011 13:01:32 Tom Albers wrote:
> 29 kde-java
I think we can safely delete that one. We don't have Java bindings anymore and
the main bindings ML is kde-bindings. A quick glance at those mails would
still be cool (can I somehow view them?).
--
Arno Rehn
a...@arnorehn.de
Hello!
I would like to inform that the move of kdeplasma-addons to git and
completed successfully.
Now you can find the new repository in:
git clone git://anongit.kde.org/kdeplasma-addons
Thanks a lot to eean for the help and to our awesome sysadmins.
Cheers,
Artur
--
Mardi, le 1 février 2011, à 20:14, Alexander Neundorf a écrit:
> On Tuesday 01 February 2011, Friedrich W. H. Kossebau wrote:
> > Mardi, le 1 février 2011, à 19:42, Alexander Neundorf a écrit:
> > > On Tuesday 01 February 2011, Friedrich W. H. Kossebau wrote:
> > > > Mardi, le 1 février 2011, à 18:
On Tuesday 01 February 2011, Michael Jansen wrote:
> On Tuesday 01 February 2011 19:53:40 Alexander Neundorf wrote:
> > On Monday 31 January 2011, Aaron J. Seigo wrote:
> > > On Sunday, January 30, 2011, Michael Pyne wrote:
> > > > Like I said, "xml-support" branch on kdesrc-build git. If you want
A stray thought on making plasma-netbook easier to use: have a shortcut to the
search field, and put it in the text, so it reads "F2 to search" instead of
"Search" (given F2 is the shortcut). That way it will be visible to the user
what to do.
--
Venlig hilsen,
Anders
On Tuesday 01 February 2011 19:53:40 Alexander Neundorf wrote:
> On Monday 31 January 2011, Aaron J. Seigo wrote:
> > On Sunday, January 30, 2011, Michael Pyne wrote:
> > > Like I said, "xml-support" branch on kdesrc-build git. If you want
> > > to
> > > give
> >
> > _very_ cool. will the good new
Mardi, le 1 février 2011, à 20:10, Sune Vuorela a écrit:
> On 2011-02-01, Friedrich W. H. Kossebau wrote:
> > We can't assume for all, but in many installations the user does. Like
> > the ususal private computer.
> > For administrated systems, there could be a substitute which instead of
> > allo
On Tuesday 01 February 2011, Friedrich W. H. Kossebau wrote:
> Mardi, le 1 février 2011, à 19:42, Alexander Neundorf a écrit:
> > On Tuesday 01 February 2011, Friedrich W. H. Kossebau wrote:
> > > Mardi, le 1 février 2011, à 18:53, Sune Vuorela a écrit:
> > > > On 2011-02-01, Friedrich W. H. Kosseb
On 2011-02-01, Friedrich W. H. Kossebau wrote:
> We can't assume for all, but in many installations the user does. Like the
> ususal private computer.
> For administrated systems, there could be a substitute which instead of
> allowing to install rather aids the user to file a request to the adm
Mardi, le 1 février 2011, à 19:42, Alexander Neundorf a écrit:
> On Tuesday 01 February 2011, Friedrich W. H. Kossebau wrote:
> > Mardi, le 1 février 2011, à 18:53, Sune Vuorela a écrit:
> > > On 2011-02-01, Friedrich W. H. Kossebau wrote:
> > > > Uh, that is old-fashioned. Should instead ask the
On Monday 31 January 2011, Andreas Pakulat wrote:
> Hi,
>
> something that hasn't been written down as far as I can see (if I
> overlooked it, please point me to it) is what the policy on kdelibs is
> to be now wrt. merging vs. cherry-picking of changes in branches and
> master?
>
> Andreas
Not r
On Tuesday 01 February 2011, Aaron J. Seigo wrote:
> On Monday, January 31, 2011, Andreas Pakulat wrote:
> > On 01.02.11 01:18:58, Pino Toscano wrote:
> > > Alle martedì 1 febbraio 2011, Aaron J. Seigo ha scritto:
> > > > > The concern that I have, on the other hand, is whether this can be
> > > >
On Monday 31 January 2011, Aaron J. Seigo wrote:
> On Sunday, January 30, 2011, Michael Pyne wrote:
> > Like I said, "xml-support" branch on kdesrc-build git. If you want to
> > give
>
> _very_ cool. will the good news today never end? ;)
>
> serious question: once this is stabilized, can we make t
Mardi, le 1 février 2011, à 19:39, Sune Vuorela a écrit:
> On 2011-02-01, Friedrich W. H. Kossebau wrote:
> >> And I'm not sure there should be
> >> such a thing.
> >
> > Hm. You don't agree that a user experience like
> >
> > "Sorry, missing X to do Y. Would you like to get X now for that?"
On Tuesday 01 February 2011, Kevin Krammer wrote:
> On Tuesday, 2011-02-01, Christoph Cullmann wrote:
...
> > Yeah, and because of this requirement, which I can agree on, I didn't
> > remove it from kdelibs, as its public API and I wanted to be SC + BC. And
> > no, runtime components moving to othe
On Tuesday 01 February 2011, Friedrich W. H. Kossebau wrote:
> Mardi, le 1 février 2011, à 18:53, Sune Vuorela a écrit:
> > On 2011-02-01, Friedrich W. H. Kossebau wrote:
> > > Uh, that is old-fashioned. Should instead ask the user whether she
> > > wants to install the proper text editor module.
On 2011-02-01, Friedrich W. H. Kossebau wrote:
>> And I'm not sure there should be
>> such a thing.
>
> Hm. You don't agree that a user experience like
> "Sorry, missing X to do Y. Would you like to get X now for that?"
> is better than one à la
> "Na, no way to do Y."?
Yes. since we
On 01/02/2011, George Goldberg wrote:
> On 1 February 2011 12:01, Tom Albers wrote:
>> The monthly overview
>>
>> - Forwarded Message -
>>> 342 decibel
>
> I think it's safe to kill this list. The project has been in the land
> of the unmaintained for at least a year now.
But it shou
Mardi, le 1 février 2011, à 18:53, Sune Vuorela a écrit:
> On 2011-02-01, Friedrich W. H. Kossebau wrote:
> > Uh, that is old-fashioned. Should instead ask the user whether she wants
> > to install the proper text editor module. Isn't there some simple
> > standard api for that these days?
>
> A
On Mon, Jan 31, 2011 at 21:19, Aaron J. Seigo wrote:
>[snip]
> oh well, KTextEditor isn't an option,
Should we give up so easily on this? The whole point of modularization
is to remove cross-module dependencies, just like KHTML depending on
KTextEditor. Ideally this sort of "sideways" dependency
On 2011-02-01, Aaron J. Seigo wrote:
> perhaps we should think about being more clear in our runtime definitions a=
> nd=20
> stricter with requiring apps to advertise their runtime expectations, so th=
> at=20
> we can go from having a huge pile of dependencies to just the requirements =
> for=20
On 2011-02-01, Friedrich W. H. Kossebau wrote:
> Uh, that is old-fashioned. Should instead ask the user whether she wants to
> install the proper text editor module. Isn't there some simple standard api
> for that these days?
A simple standard api for what? installations of scripts and wallpape
On Tuesday, February 1, 2011, George Goldberg wrote:
> >> 29 plasma-bugs
>
> Same as kdelibs-bugs for this one.
i'd appreciate the help with it :)
--
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43
KDE core developer sponsored by Qt Dev
On Tuesday, February 1, 2011, Sune Vuorela wrote:
> So far, we as packagers have been told that applications can expect all
> plugins (kio slaves, kparts, ...) located in kdelibs and kdebase-runtime
> to be available, and segfault is a acceptable way of handling missing
> things.
to boil it down t
Alle venerdì 28 gennaio 2011, Nicolas Alvarez ha scritto:
> What do you all think of removing wallpapers from these git
> repositories? We could put them in a separate git repository, or
> even keep them in SVN.
Now that the workspace repository was pushed without them (so breaking
history, past
Mardi, le 1 février 2011, à 16:43, Maksim Orlovich a écrit:
> > erf; two dependencies in kdelibs on KTextEditor. ok, that makes it a no
> > go then ... hm.. looking at it, only khtml has a build-time dependency
> > on it. if
> > the texteditor part isn't available (or the source of the crash even?
Quoting Tom Albers :
80 kmobiletools
20 kde-embedded
We already have kde-mobile...maybe it's safe to remove these two
mailing lists?
Cheers,
Artur
---
> erf; two dependencies in kdelibs on KTextEditor. ok, that makes it a no go
> then ... hm.. looking at it, only khtml has a build-time dependency on it.
> if
> the texteditor part isn't available (or the source of the crash even? :)
> what
> does the debugger do at that point?
Pop up an error mes
On 1 February 2011 12:01, Tom Albers wrote:
> The monthly overview
>
> - Forwarded Message -
>> 342 decibel
I think it's safe to kill this list. The project has been in the land
of the unmaintained for at least a year now.
>> 41 kdelibs-bugs
This is a very useful list for bug tria
On 2011-02-01, Christoph Cullmann wrote:
>> So far, we as packagers have been told that applications can expect all
>> plugins (kio slaves, kparts, ...) located in kdelibs and kdebase-runtime
>> to be available, and segfault is a acceptable way of handling missing
>> things.
> I agree that this wi
On 02/01/2011 01:21 PM, Andreas Pakulat wrote:
> On 01.02.11 13:05:49, Sebastian Trüg wrote:
>> On 02/01/2011 11:11 AM, Andreas Pakulat wrote:
>>> On 01.02.11 10:21:01, Sebastian Trüg wrote:
Hi list,
I have been working on an improvement for Nepomuk via git-svn for a
while now a
On 01.02.11 13:05:49, Sebastian Trüg wrote:
> On 02/01/2011 11:11 AM, Andreas Pakulat wrote:
> > On 01.02.11 10:21:01, Sebastian Trüg wrote:
> >> Hi list,
> >>
> >> I have been working on an improvement for Nepomuk via git-svn for a
> >> while now and would now like to push it to kde-runtime.
> >
On 02/01/2011 11:11 AM, Andreas Pakulat wrote:
> On 01.02.11 10:21:01, Sebastian Trüg wrote:
>> Hi list,
>>
>> I have been working on an improvement for Nepomuk via git-svn for a
>> while now and would now like to push it to kde-runtime.
>
> If the branch has been created via git-svn you cannot me
The monthly overview
- Forwarded Message -
> 342 decibel
> 80 kmobiletools
> 47 kde-contests
> 46 kde-i18n-pt
> 43 kgraphviewer-devel
> 41 kdelibs-bugs
> 32 kde-usability
> 31 dot-stories
> 29 plasma-bugs
> 29 kde-java
> 20 kde-embedded
> 19 kde-openserver
> 19 kde-news-de
> 19 kde-fra
On Tuesday, 2011-02-01, Christoph Cullmann wrote:
> On Tuesday, February 01, 2011 11:11:08 am Sune Vuorela wrote:
> > So far, we as packagers have been told that applications can expect all
> > plugins (kio slaves, kparts, ...) located in kdelibs and kdebase-runtime
> > to be available, and segfau
Am 2/1/2011 10:31, schrieb David Jarvie:
> On Mon, January 31, 2011 11:27 pm, Thiago Macieira wrote:
>> On Monday, 31 de January de 2011 23:34:39 Arno Rehn wrote:
>>> I guess that won't quite work when there are commits specific to 4.6 in
>>> the
>>> 4.6 branch that shouldn't end up in master. And
On Tuesday, February 01, 2011 11:11:08 am Sune Vuorela wrote:
> On 2011-02-01, Aaron J. Seigo wrote:
> > --nextPart3865859.bpjpIik9D5
> > Content-Type: Text/Plain;
> >
> > charset="us-ascii"
> >
> > Content-Transfer-Encoding: quoted-printable
> >
> > On Monday, January 31, 2011, Michael Pyne
On 01.02.11 10:21:01, Sebastian Trüg wrote:
> Hi list,
>
> I have been working on an improvement for Nepomuk via git-svn for a
> while now and would now like to push it to kde-runtime.
If the branch has been created via git-svn you cannot merge it properly.
You need to cherry-pick all commits.
>
On 2011-02-01, Aaron J. Seigo wrote:
> --nextPart3865859.bpjpIik9D5
> Content-Type: Text/Plain;
> charset="us-ascii"
> Content-Transfer-Encoding: quoted-printable
>
> On Monday, January 31, 2011, Michael Pyne wrote:
>> On Monday, January 31, 2011 17:42:56 Aaron J. Seigo wrote:
>> > potential cav
On Mon, January 31, 2011 11:27 pm, Thiago Macieira wrote:
> On Monday, 31 de January de 2011 23:34:39 Arno Rehn wrote:
>> I guess that won't quite work when there are commits specific to 4.6 in
>> the
>> 4.6 branch that shouldn't end up in master. And it clutters history with
>> tons of merges.
>
>
On 1 February 2011 09:21, Sebastian Trüg wrote:
> Hi list,
>
> I have been working on an improvement for Nepomuk via git-svn for a
> while now and would now like to push it to kde-runtime.
> However, I would prefer to keep the commit history and backport to 4.6.
> Thus, I thought of pushing my fea
Hi list,
I have been working on an improvement for Nepomuk via git-svn for a
while now and would now like to push it to kde-runtime.
However, I would prefer to keep the commit history and backport to 4.6.
Thus, I thought of pushing my feature branch into the kde-runtime
repository and then merge i
On Tue, Feb 01, 2011 at 01:43:17AM +0100, Andreas Pakulat wrote:
> I'm constantly doing the tag --contains and branch --contains thing to
> find out when a certain fix was done at work to double-check wether a
> reported bug is already contained in a released version. Or which
> branches are affect
On Tue, Feb 01, 2011 at 08:18:10AM +0100, Thiago Macieira wrote:
> On Tuesday, 1 de February de 2011 01:23:01 Oswald Buddenhagen wrote:
> > just face it, git's merging concept makes most sense for longer-lived
> > feature branches, but not so much for bugfix branches. not even linux
> > itself uses
Some text was lot in the paragraph below due to kmail freezing during editing
this mail.
My experince with SAL so far is that I start it, look at it and do not know
what to do except clicking in the entry field, which makes me immediately go
back to the normal desktop.
Missing text: Currently
A Segunda, 31 de Janeiro de 2011 23:58:54 Anders Lund você escreveu:
> Please do not make everything the desktop, as long as it is not keyboard
> accerssible! I avoid using plasma-notebook, since it is an interface for
> clickers. Such interfaces may make sense for tablets and phones, NOT for
> any
On Tirsdag den 1. februar 2011, Aaron J. Seigo wrote:
> On Monday, January 31, 2011, Anders Lund wrote:
> > Please do not make everything the desktop, as long as it is not keyboard
> > accerssible! I avoid using plasma-notebook, since it is an interface for
> > clickers.
>
> please do not make kne
86 matches
Mail list logo
