[08:18] <Wiz_KeeD> hello guys
[08:19] <Wiz_KeeD> I have a directory that is owned by www-data and www-data group, how do I manage a bzr branch when new files are constantly being generated and I cannot be expected to chmod g+w ./* -R every time
[15:09] <Wiz_KeeD> guys, how does one update thew working tree?
[15:10] <jelmer> Wiz_KeeD: "bzr update"
[15:10] <Wiz_KeeD> I tried that it does not update the working tree, still empty
[15:10] <Wiz_KeeD> I moved everything out and did revert -r latest_revision
[15:10] <Wiz_KeeD> and it worked
[15:11] <jelmer> so it does depend on what you mean by "update"
[15:15] <Wiz_KeeD> update the working tree precisely to what the revision has
[15:17] <jelmer> just "bzr revert" should do that
[15:23] <Wiz_KeeD> with --no-backup so i don't have a lot of crap to deal with?
[15:26] <jelmer> it should only create backup files for files that have actually changed
[15:38] <Wiz_KeeD> yeah they would be a lot
[20:38] <jfcaron> Is there a way to set something in bazaar.conf (or elsewhere) that makes "bzr diff" automatically do the same thing as "bzr cdiff"?  cdiff isn't intuitive enough for me.
[20:38] <jfcaron> "bzr diff" is apparently not an allowed bash alias name because of the space.
[20:38] <jelmer> jfcaron: yes, add an alias for 'diff' to 'diff --color'
[20:38] <jelmer> jfcaron: a bzr alias, rather than a bash alias
[20:39] <jfcaron> What's the difference between diff --color and cdiff?
[20:40] <jelmer> they should be the same thing
[20:40] <jelmer> you can create an alias to cdiff too
[20:40] <jfcaron> Cool, thanks.
[20:41] <jfcaron> And it's a global setting in my bazaar.conf, as I wanted.