Review Request 113957: Rename of "Recently Accessed" to "Recently Saved"
Emmanuel Pescosta
emmanuelpescosta099 at gmail.com
Sat Dec 14 13:35:29 GMT 2013
> Does this mean I have to compile things? Actually I don't know how to do
> this.
It's really easy ;)
The steps are:
1. Create a folder structure were you have your source code, your build
directory and your install directory.
For example:
mkdir $HOME/kde-devel
cd $HOME/kde-devel
mkdir src build install
2. Clone the repos into $HOME/kde-devel/src
For example:
cd $HOME/kde-devel/src
git clone kde:kde-baseapps
3. Open KDevelop and Open/Import this project
4. Use $HOME/kde-devel/install as intall directory and
$HOME/kde-devel/build as build directory.
5. Edit the source code/apply patches and build the project
6. Run -> Configure Launches and add Dolphin here
7. Start Dolphin via execute
8. Have fun! ;)
2013/12/14 Frank Reininghaus <frank78ac at googlemail.com>
> Hi,
>
> it's actually preferred to add additional comments to the review
> request directly. Splitting the conversation between the review
> request and regular mails makes the conversation hard to follow for
> anyone who might try to find out something about it in the future.
>
> 2013/12/11 Richard llom:
> > Frank Reininghaus wrote:
> >
> >> -----------------------------------------------------------
> >> This is an automatically generated e-mail. To reply, visit:
> >> http://git.reviewboard.kde.org/r/113957/#review45525
> >> -----------------------------------------------------------
> >>
> >> Ship it!
> >>
> >>
> >> Looks good, thanks! Do you have a git account?
> >>
> > I don't know, so far I accomplished everything with the identity.kde.org
> > account. Does this include a git account?
>
> No. We can push the patch for you then.
>
> >> If yes, feel free to push to master once you have tested that it still
> >> works as expected, i.e., that the change does not cause unexpected
> >> breakage at run time.
> >>
> > Does this mean I have to compile things? Actually I don't know how to do
> > this.
>
> Does that mean that you did not even check if the patched code still
> builds? I'm a bit surprised now - actually, I think that everyone
> assumes implicitly that at least this has been verified for *every*
> patch uploaded to ReviewBoard, unless explicitly stated otherwise.
>
> Actually, I think that I clearly stated in
>
> https://bugs.kde.org/show_bug.cgi?id=304854#c7
>
> that the reason why I would appreciate help with this change is that
> careful testing of the change is IMHO needed (it might seem unlikely
> that it breaks at runtime, but one should definitely test it in order
> not to cause unexptected trouble).
>
> But I hope that I misunderstood you ;-)
>
> Cheers,
> Frank
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.kde.org/mailman/private/kfm-devel/attachments/20131214/7a6be4cb/attachment.htm>
More information about the kfm-devel
mailing list