Re: Can we rename gitklient?
On Sat, Mar 4, 2023 at 3:14 PM Hamed Masafi wrote: > > > I think Kittie is too close to Kitty (a terminal application iirc) so I'd > > avoid that one at least. > OK > > > Yes, the name can be changed, we could change it even we you had released it > > already (would be a bit more annoying probably). > Thanks > > > I’d personally stay away from names involving the word “code” (or “kode”), > > as that makes it sound like it’s some sort of IDE. Kommit sounds like a > > pretty good option to me. > > I really like "Kommit". It starts with "K" and is just to the point. > > Kommit makes a lot of sense to me. > This is what it looks like, the name kommit has a lot of fans On the other hand, "gitklient" has quite good search results, all of the top hits I get are correct, whereas "kommit" has several hits that may be difficult to overcome.
Re: branch Tracking question
On Sat, Jul 27, 2013 at 8:39 PM, Lindsay Mathieson < lindsay.mathie...@gmail.com> wrote: > If I'm working on a kde private local branch that is intended to eventually > merge with master should I set it to track the remote master? > Only if the branch itself is intended to be available to others, and only when you're ready for it to be publicly available to avoid accidents with `git push --all` etc. Regards, Eli >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: moc isn't being called for the output of custom commands
Hi, On Sat, Apr 20, 2013 at 5:55 PM, Michael Spencer wrote: > Hello, > > I have a small script that helps to generate parts of a Qt class. I then > call it from a CMake file, using a couple custom commands in a function: > > Here is the part that doesn't work. Although the the custom commands are > called and work great, moc doesn't get called on the resulting files. > However, if I generate the files by hand, and than manually add the copied > source file to the list of sources, moc does get called. The list of source > files is identical regardless of whether I add the file by hand or it gets > added as a result of the custom commands. It's just the moc doesn't get > called if the file is produced as a result of a custom command. > > I am doing the custom commands wrong? How do I fix this so moc is called > on the output of my custom commands? > > I did this about a year ago, I've put it on techbase (in a temporary location) now due to the length of the lines: http://techbase.kde.org/User:Argonel/mocGenerated There may be a "more correct" method, but as it wasn't intended for permanent use I didn't put much effort into it beyond making it work. Regards, Eli >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
