From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: commands like "du", "df", and "btrfs fs sync" hang
Date: Mon, 2 May 2016 00:23:02 +0000 (UTC) [thread overview]
Message-ID: <pan$39a32$2b46fbc1$6cec1$390d6a91@cox.net> (raw)
In-Reply-To: 20160501185418.5a148cdd@jupiter.sol.kaishome.de
Kai Krakow posted on Sun, 01 May 2016 18:54:18 +0200 as excerpted:
> I didn't now about smart-live-rebuild. Interesting. ;-)
Yeah. I didn't know about it until a few years ago, either, including
when I first setup kde4-live, tho at that point I was doing the stable-
branch live, not master live, so there were fewer changes. But I was
relying only on ccache to speed things up and rebuilding all my live
packages at every update, at the time.
Once I saw mention of smart-live-rebuild, however, and tried it, I soon
switched to live-master, and ran it in the kde4 era for a couple years
until development on kde4 nearly stopped as they focused on the
frameworks5-based versions. Then I waited until an actual frameworks5-
based plasma in /release/ versions would install and work for me, before
working on eliminating the deps for features I wasn't going to use
anyway, and then finally switching again to now frameworks5-based live-
git versions, only recently. Only this time I skipped the beta release
step and the stable-branch step and went directly from working release to
live-git-master.
But smart-live-rebuild *definitely* makes it easier, as do my helper
scripts that let me easily follow git logs for every package, and even do
git bisects when necessary, without having to manually switch into the
package's git dir first. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2016-05-02 0:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-01 7:00 commands like "du", "df", and "btrfs fs sync" hang Kai Krakow
2016-05-01 12:47 ` Duncan
2016-05-01 13:54 ` Mike Fleetwood
2016-05-01 23:16 ` Duncan
2016-05-01 16:54 ` Kai Krakow
2016-05-01 23:22 ` Duncan
2016-05-01 23:49 ` Duncan
2016-05-02 13:19 ` Austin S. Hemmelgarn
2016-05-03 6:44 ` Kai Krakow
2016-05-02 0:23 ` Duncan [this message]
2016-05-02 13:13 ` Austin S. Hemmelgarn
2016-05-03 15:09 ` Duncan
2016-05-02 0:39 ` Nicholas D Steeves
2016-05-03 6:48 ` Kai Krakow
2016-05-05 6:35 ` Kai Krakow
2016-05-07 11:40 ` Kai Krakow
2016-05-09 17:13 ` Nicholas D Steeves
2016-05-09 18:20 ` Kai Krakow
-- strict thread matches above, loose matches on Subject: below --
2016-05-01 10:22 Kai Krakow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='pan$39a32$2b46fbc1$6cec1$390d6a91@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).