=== Yannig [n=Kokoyaya@AToulouse-254-1-89-52.w86-207.abo.wanadoo.fr] has joined #launchpad === Who_ [n=jonny@194-247-228-106.dynamic.dsl.as9105.com] has joined #launchpad [12:31] Merge to devel/launchpad/: [r=jamesh] Fix https://launchpad.net/products/malone/+bug/34105 (Strip leading and trailing whitespace before storing a bug watch's remotebug in the db) and https://launchpad.net/products/launchpad/+bug/41325 (Need to strip whitespaces from the beginning and end of people's displaynames) (r3558: Diogo Matsubara) [12:31] Malone bug 34105 in malone "Strip leading and trailing whitespace before storing a bug watch's remotebug in the db" [Major,In progress] [12:58] Hello, I'm from the art team (ubuntu-art) - Mark wants us to get a poll up but no-one who is currently available/responding has administrative rights- We need to get things going as fast as possible so as to have our voting for Themes done in time for them to be packaged for Dapper. Can anyone help? - we spoke to Salgado and he said that dropping in here was our best chance... Refernces: https://lists.ubuntu.com/archives/ubuntu-art [12:58] /2006-May/001355.html, https://lists.ubuntu.com/archives/ubuntu-art/2006-May/001480.html [01:03] Who_: AFAICT, only the team owner or a team admin are able to setup polls for the team [01:08] Salgado thought that it may be possible for some kind of uber admin to do it (my words, not his!) [01:09] From his mail to the list (not yet in the archives) "I myself can't do it, but I can explain what's going on to one of the Launchpad administrators and they'll be able to set up the poll for you. It'd [01:09] be good if you could join #launchpad on freenode.net so we can sort out the poll details and ask one of the global admins to create it for you." [01:09] so I am here obediently :) [01:10] Who_: indeed it's possible for a Launchpad Admin to setup this poll. the best time to find a LP admin here, is between 12:00 UTC and 21:00 UTC [01:10] I can help tomorrow, Who_ [01:10] I need to skip out tonight though "or else" [01:11] Who_: salgado also works at this time, so it'll be better if you can talk directly with him [01:12] I have to go too. See you guys tomorrow. [01:13] kiko-zzz, that would be great - can I email you more details if we haven't already sorted it out by then? [01:13] sure [01:13] gone! === ..[topic/#launchpad:lifeless] : Conversion to knits occuring 1030AEST PQM is down. https://launchpad.net/ | developer meeting: Thu 18 May, 1200UTC (wiki:MeetingAgenda) | launchpad-users@lists.canonical.com (wiki:MailingLists) | Channel logs: http://tinyurl.com/72w39 [01:16] ('thanks' seemed to escape that message) [01:16] spiv: we'll still start our run at 0930 [01:21] lifeless: ok. === sobersabre [n=bilbo@l192-117-118-8.broadband.actcom.net.il] has joined #launchpad [01:24] hi guys. [01:24] I wonder if I can access my launchpad calendar from evolution ? [01:24] and also to post events etc. via evo. === Adri2000 [n=Adri2000@lns-bzn-45-82-65-146-216.adsl.proxad.net] has joined #launchpad [01:35] lifeless: I'm copying down the branch from rocketfuel.knits now, looks about 15% done. [01:41] k [01:44] elmo: are you around ? [01:44] lifeless, he's on vacation [01:44] you will need to call znarl [01:44] oh right. [01:44] I'll rt it, its not urgent [01:45] ok cool [01:45] its also trivial, which is why I was going to ask direct :) [01:48] lifeless, pqm is telling me it I'm submitting a request for a non-managed branch. any clue what I did wrong? [01:49] I wonder if bzr-submit needs to be updated [01:49] or if something else is wrong [01:50] kiko-zzz: i recommend you start using the bzr pqm-submit plugin [01:50] its more flexible. [01:50] if pqm is telling you that, then the branch url its being given is wrong. [01:50] let me check your request [01:50] my branch URL, right, not the RF one? [01:50] this is what you sent in [01:51] star-merge sftp://chinstrap.ubuntu.com/home/warthogs/archives/kiko/launchpad/trivialities-xx/ sftp://chinstrap.ubuntu.com/home/warthogs/archives/rocketfuel/lib/canonical/launchpad/pagetests/foaf/30-mergepeople.txt [01:51] it should have been [01:51] that's not so good. [01:51] star-merge sftp://chinstrap.ubuntu.com/home/warthogs/archives/kiko/launchpad/trivialities-xx/ sftp://chinstrap.ubuntu.com/home/warthogs/archives/rocketfuel/launchpad/devel [01:51] I now see why [01:51] I am daft [01:54] spiv: this is a small python fragment I call repo-adsorb [01:55] from bzrlib.ui.text import TextUIFactory [01:55] import bzrlib [01:55] bzrlib.ui.ui_factory = TextUIFactory() [01:55] import bzrlib.repository [01:55] target=bzrlib.repository.Repository.open('.') [01:55] source=bzrlib.repository.Repository.open('devel') [01:55] target.fetch(source) === mpt [n=mpt@203.109.220.214] has joined #launchpad [01:55] followed by 'mv devel/.bzr/repository{,.old}' [01:55] it will suck a branch in metaweave format into a repo [01:56] Yay, I have Internet again [01:56] kiko-zzz: your merge request looks good. Its in the disabled queue now [01:57] thanks. [01:57] lifeless, is rocketfuel still pullable? [01:57] lifeless: Oh btw, I have a green Ps driving test at 11:30, so I'll have to disappear for a while around then. [01:57] I am now going to bed and will dream of fast merges [01:57] mpt: yes, we wont touch the rocketfuel-built for another 30 minutes [01:57] spiv: ok. [01:57] ta [02:00] mpt: andrew or I will guide you through the upgrade [02:00] as validation of our instructions [02:00] is that ok ? [02:04] lifeless, sure, you want to do that now? [02:05] mpt: in about 1 hour [02:05] ok [02:21] BjornT, ping [02:22] BjornT, unping === rpedro_ [n=rpedro@87-196-7-207.net.novis.pt] has joined #launchpad === tambaqui [n=tambaqui@201.160.20.136.cableonline.com.mx] has joined #launchpad === sladen [i=paul@starsky.19inch.net] has joined #launchpad === sivang [i=sivan@muse.19inch.net] has joined #launchpad === Burgundavia [n=corey@ubuntu/member/burgundavia] has joined #launchpad [02:52] spiv: ok, we're ready for a test merge [02:53] lifeless: I've got about 20MB left to download. [02:57] production is currently converting [03:01] Finally downloaded. [03:02] Gooooooooooooooooooooood afternoon Launchpadders! [03:10] "-4 revision(s) pulled." Heh. [03:10] ;) [03:12] lifeless: I need to head off to the driving test now, I should be back soon. [03:12] ok [03:12] lifeless: But I have just successfully converted a branch, following the instructions on the page. [03:12] good luck [03:13] "bzr log" and things seems to be giving sane output. [03:13] cool [03:13] lifeless: not sure where your repo-absorb thing fits in, but we can talk about that when I get back :) [03:13] ok [03:13] mpool: thanks [03:13] I'm propogating converted production branches to chinstraph now === tambaqui [n=tambaqui@201.160.20.136.cableonline.com.mx] has left #launchpad [] [03:44] lifeless, spiv, you wanted to walk me through the migration process? === stub [n=stub@ppp-58.8.3.253.revip2.asianet.co.th] has joined #launchpad [03:45] yup [03:45] stub: please let me know before doing anything on balleny just now [03:45] ok [03:46] Will I need Internet access on my development machine for this? [03:46] yes [03:46] ok, bbiab [03:47] lifeless: to convert a repository, I suppose the best way is to create a new repo and branch into it? [03:48] (having branched the knit rocketfuel branch into it first) [03:48] jamesh: hi [03:48] if you have a repository and need to convert it.. [03:48] bzr init-repo new-repo [03:48] python === mpt [n=mpt@203.109.220.214] has joined #launchpad [03:49] from bzrlib.ui.text import TextUIFactory [03:49] import bzrlib [03:49] bzrlib.ui.ui_factory = TextUIFactory() [03:49] import bzrlib.repository [03:49] target=bzrlib.repository.Repository.open('new-repo') [03:49] source=bzrlib.repository.Repository.open('old-repo-root') [03:49] target.fetch(source) [03:49] when that completes [03:49] mv old-repo/.bzr/repository{,.weaves} [03:50] mv new-repo/.bzr/repository old-repo/.bzr/repository [03:50] shouldn't I be importing the knits branch into the repo first? [03:50] and yes, pull the knit rocketfuel branch in first [03:50] otherwise that's equivalent to a bzr upgrade [03:54] main point is to use python to fetch the repo data [03:54] rather than pulling X branches across one at a time [03:54] yeah. [03:55] converting a bunch of branches into a repo is essentially a 'for path in os.listdir('.'): source = Repository.open(path); target.fetch(source)' loop [03:57] dell are doing 1000 dollar laptops now [03:57] thats quite impressive === mpt waits for the rsync [03:58] stub: production branches are now in knit format [03:58] stub: there is a diff in production/launchpad thats not committed [03:59] mebbe just the cruft from tests? [03:59] nah [03:59] cd ~/production/launchpad && diff to see [04:00] lifeless: so we can use the versions under .../archives/rocketfuel/ for the conversion rather than rocketfuel.knits now? [04:00] not yet, the rsync is still running [04:01] pqm@balleny:~/archives/rocketfuel/launchpad$ rsync -a --delete-after . chinstrap:/home/warthogs/archives/rocketfuel/launchpad [04:01] when that finishes :) [04:01] ahh yes. need to apply that change to production/1.62 [04:02] stub: ok. dont do it yet. will let you know when its clear [04:02] yup === stub is slow today due to one fscked wrist [04:03] ouch [04:03] too much 'testing' ? [04:03] swimmingi think [04:03] maybe dislocated a bit - things have been clicking back occasionally [04:04] so one handed for time being [04:04] mebbe take it into the hospital if not getting better in a few hours [04:05] lifeless: gah, the downside is bizarre dell phone support [04:06] www.dell.com.au/tv [04:06] I think Dell is still selling $350 Pentium D 2.8GHz machines too [04:06] in fairly nice tower boxes [04:08] although if you want to put a replacement graphics card in, you need to modify the card with a hacksaw [04:08] :) [04:08] to cut an extra notch [04:08] have you done this ? [04:08] yeah [04:08] you cut the maximum bandwidth of the card down from 16x PCIe to 8x [04:08] but it works [04:09] its a half-length socket ? [04:09] !! === salgado [n=salgado@201-1-130-8.dsl.telesp.net.br] has joined #launchpad [04:09] it is an 8x size socket which only has pins for a 4x connection (the machine is designed to be a server) [04:10] there is an 8x socket, but it doesn't seem to like graphics cards [04:11] lifeless: around? [04:11] yup [04:12] I think I need new batteries :{ [04:12] runtime seems to be shrinking [04:12] I've checked and they are only rated for 300 charge cycles ! [04:12] mpool: send that merge in asap please [04:12] lifeless: do I need to do something in order to land my shipit branch once the converion to knits is finished? [04:12] salgado: send in a merge request as normal [04:13] salgado: I can in fact have your branch come in first if you like [04:13] This is where I wish Ubuntu had labels like OS X [04:13] so I could color-code the branches I've converted [04:13] lifeless: that'd be great [04:13] lifeless, ok [04:13] mpt: emblems [04:13] salgado: will you be around if there are glitches ? [04:13] lifeless: at what time? [04:13] (first up is most risk :)) [04:14] salgado: we can do it as soon as this rsync finishes [04:14] shouldn't be long now [04:14] lifeless: I don't understand "bzr pull --overwrite into the rocketfuel-built matching branch" [04:14] its between balleny and chinstrap [04:14] The branch matching what? [04:14] okay. I'm going to have a shower then, be right back === salgado is now known as salgado-brb [04:14] mpt: this is where we need to walk you though ;) [04:14] mpt: tell me what you have done so far [04:14] lifeless: back [04:14] lifeless: (and I passed) [04:14] spiv: congrats! [04:15] spiv: now, just sms me when you are driving [04:15] lifeless: I don't use a repository; all my branches are in separate directories [04:15] lifeless: I've rsynced rocketfuel-built [04:15] lifeless: I'm in the middle of "bzr upgrade --format=metaweave trivial" [04:15] mpt: rocketfuel-built isn't yet in knit format [04:15] where trivial is the first branch I'm converting [04:15] mpt: right, get those upgrade --format=metaweave done for all your branches [04:15] mpt: as thats a necessary first step [04:16] oh [04:16] each one of those will chew up about 400MB of disk [04:16] Why isn't it step 1, then? :-) [04:16] lifeless, sent [04:16] mpt: because this is not as automated as the baz->bzr one, but should be easier all the same [04:16] when you do upgrade --format=metaweave, there is a '.bzr.backup' directory created [04:17] as long as the upgrade worked you can remove that directory, it has about 400Mb of old data in it [04:18] How do I tell whether it worked? [04:18] it will say 'conversion complete' [04:18] it says "finished" [04:18] and 'you can remove the .bzr.backup directory' [04:18] nope, doesn't say that either [04:18] if conversion fails, you can move this directory back to .bzr [04:18] if it succeeds, you can remove this directory if you wish [04:18] starting upgrade from format 6 to metadir [04:18] finished [04:18] mpt: there should be a "repository" directory under the .bzr/ directory [04:19] mpt: thats a successful conversion [04:19] yes [04:19] ok [04:20] bzr log still works [04:23] garh [04:23] man ext3 is SO SLOW AT RM [04:23] I hear that riserfs is much quicker at losing your files [04:25] its when one wants them lost its frustrating === salgado-brb is now known as salgado [04:44] lifeless: so, how's the conversion going? [04:45] rsyncing still [04:49] its on 1.49 oout of 1.62 [04:49] 1.5 [04:50] 1.50 [04:50] 1.51 [04:50] 11 branches to go, say 10 minutes [04:50] I'm going to grab lunch [04:51] Me too. [04:55] mpool: did that merge work for you ? [05:04] 1.61, nearly there === BjornT [n=bjorn@clt-84-32-240-183.dtiltas.lt] has joined #launchpad === mpt_ [n=mpt@203.109.220.214] has joined #launchpad [05:14] ok [05:14] launchpad branch is fully converted [05:14] salgado: did you have a merge request for this in the queue already ? [05:18] lifeless: it was in the queue [05:18] I can send it again right now, if you want [05:18] no need, I can retrieve it from the disabled queue [05:20] lifeless: Does that mean I should pull rocketfuel-built again? [05:21] mpt_: not quite yet [05:21] rf built is rebuilding at the moment [05:21] but anyone usin the archive directly can do so [05:21] stub: you can do new branches now etc [05:23] "But if we try to change it to a existing upstream bugtask, our validator enters in action." [05:23] Enters in action? [05:23] EWTF [05:25] ta === siretart [i=siretart@ubuntu/member/siretart] has joined #launchpad [05:45] lifeless: How long will rocketfuel-built take to rebuild? [05:46] shouldn't be much longer, its in sourcecode at the moment [06:01] salgado: you need to sleep. can you send another request in, and I'll shepard it through [06:20] spiv: can you send in a request please [06:20] lifeless: Hmm, ok. [06:21] just a trivial change [06:21] I think I've fixed the thing that glitched salgados branch [06:21] lifeless: finished? [06:21] nope, same thing glitched it [06:21] mpt_: so just work as normal [06:21] ok === mpt [n=mpt@203.109.220.214] has joined #launchpad === frodon_ido [n=patrick@ip-213-49-219-236.dsl.scarlet.be] has joined #launchpad [06:39] lifeless: still merging to the same location, right? [06:41] lifeless: sent [06:42] yes [06:44] was nice to see that the working repository for pending-reviws was about half the size when moved to knits [06:45] hopefully we'll see better performance once everyone else's branches are half the size [06:45] how do you merge, local disk paths or sftp ? [06:45] lifeless: I see no action on the pqm status page yet... I hope it won't still take four hours ;) [06:45] the pending-reviews script does local disk paths [06:46] spiv: building the config [06:52] spiv: so, how are you going converting your branches ? [06:52] spiv: fairly painless ? any ideas for the doco ? [06:55] lifeless: Main issue for me is disk space -- I'm very tempted to figure out how to share a repository for my branches. [06:55] spiv: the python fragment I posted is the key [06:55] spiv: jamesh also wrote a script [06:55] which, with knits I'm happy for people to use. === tambaqu1 [n=tambaqui@201.160.20.136.cableonline.com.mx] has joined #launchpad [06:55] Your python fragment assumes some weird directory structure I don't have. [06:56] spiv: tell me about your structure [06:56] Essentially, I have a "launchpad" directory somewhere in my home directory with all my (weave) branches. [06:56] so you have launchpad/foo [06:56] and launchpad/bar [06:57] Right. [06:57] spiv: http://people.ubuntu.com/~jamesh/make-bzr-repo.sh <- change FORMAT=metadir to FORMAT=knit and it will be happy [06:57] do they have nested branches ? [06:57] that is is there launchpad/foo/sourcecode/* ? [06:57] lifeless: Yes, mostly. [06:57] Mostly they start as copies (often hardlinked) of rocketfuel-built. [07:00] spiv: the way I work now is with my branches under ~/repo/canonical/$product/$branchname where each of ~/repo/canonical/$product is a shared repository [07:00] spiv: note that it is merging now [07:00] I think we have fixed the performance headache [07:00] spiv: I then do a "bzr checkout --lightweight" of the branch I want to work on to create a working tree (somewhere other than ~/repo [07:01] spiv, jamesh we now need *good* doco to help people switch to knits themselves [07:01] lifeless: Down to 20 minutes for build-config + merge, yeah. [07:01] lifeless: I'm still curious about why it took so long before, even when merging to e.g. sqlobject, but it doesn't really matter now. [07:01] lifeless: I suppose for small products I may as well just do "bzr upgrade" on my repos? [07:02] yup [07:02] since a full conversion is fairly cheap [07:02] "small" would be basically anything other than "launchpad" for us? [07:02] yeah [07:03] The next closest in number of revisions in rocketfuel is probably sqlobject, and that's only about 50 or 60. [07:03] Oh, cscvs I guess. [07:03] But nothing else in the thousands... [07:04] lifeless: Note that this merge will compensate for knits by making check_merge slower ;) [07:04] spiv: ahhha. bastard :) [07:06] jamesh: do you think that a repo and lightweight checkout is as simple as we can get it ? [07:07] lifeless: it is a little more complicated than "cp -al rocketfuel-built my-new-tree", because you need to fix up sourcecode/ [07:07] spiv: so to use a repository, you can just do what that script does, or use an repository with working trees where you work *within* the repository. [07:07] lifeless: I wish the pqm-submit plugin was packaged. [07:07] lifeless: I've been playing around with doing lightweight checkouts of the sourcecode/ dirs from rocketfuel-built too [07:08] yah [07:08] lifeless: I don't have a strong feeling for or against either of those options. [07:08] spiv: bzr itself is big and you should use the version I'm converting now [07:08] (sourcecode/bzr) [07:09] I guess this means I can't simply "cp -al" from rocketfuel-built to make a new branch + checkout anymore... [07:09] lifeless: I suppose a script for setting up/updating sourcecode/ would make lightweight checkouts simple to use. I don't know whether config-manager fits that bill or not though [07:09] jamesh: thats what rocketfuel-built is done with [07:09] lifeless: Oh heh, I forgot about that one, I converted my bzr.dev checkout ages ago :) [07:10] lifeless: but that's not a lightweight checkout [07:10] jamesh: just needs a command line option to the URLMapper to make it look at local disk [07:10] "cp -al $rf-built/sourcecode/* sourcecode/" isn't much harder, though... [07:10] jamesh: oh true. a couple of lines of python [07:11] more importantly though, I think the idiom of rsyncing rf-built down and using it is nice [07:11] if you do this: [07:11] rsync it down [07:11] hack hack hack [07:11] bzr push /local-repo/branch === dsas [n=dean@host81-129-228-205.range81-129.btcentralplus.com] has joined #launchpad [07:11] then that push will be fast [07:11] and if you have a shared repo on chinstrap [07:11] bzr push sftp://chinstrap/h/w/a/user/launchpad/branch [07:12] should be fast enough to [07:12] it will need to pull about 2Mb of data to push, which sucks [07:12] lifeless: I was about to ask that -- "bzr push /local-repo/new-branch" is the obvious piece I think I was missing. [07:13] lifeless: one thing I like about lightweight checkouts is that I can put the checkouts anywhere, and they use the ~/.bazaar/branches.conf settings for the repo directory [07:13] Is there a way to in-place convert a branch from standalone to a lightweight checkout? [07:13] spiv: not so much [07:13] spiv: can be written though [07:13] means I only needed to configure "bzr pqm-submit" once and it works wherever my checkouts are [07:13] lifeless: I think I'd find that very useful at the moment. [07:14] jamesh: cool. can you document that on our developer documentation today ? [07:14] SteveA has allowed me to ask you to help out with the conversion, as I knew you'd been working on this workflow somewhat [07:14] lifeless: My upgrade procedure would then be to start a repo seeded with the converted rocketfuel, then as I want to work on existing branches I have, push them into that repo and switch them to being checkouts of that repo. [07:14] lifeless: okay. I think I included a description in an email to the list earlier but I'd be happy to add it to the wiki [07:15] so we need two things today [07:15] 1) conversion HOWTO for sabdfdl, mpt etc [07:15] covering upgrade on chisntrap [07:15] Then there'd be no disruption to my existing nested working trees and finger-memory of paths :) [07:15] upgrade on local machine [07:15] spiv: so we can write a command using bzr to so it [07:15] spiv: I was suggesting you turn ~/launchpad in to a repo - bzr init-repo ~/launchpad [07:16] lifeless: I'm still using the "rsync local repo to chinstrap". Is there a way to do that with the bzr sftp transport yet? [07:16] i.e. not individual branches [07:16] spiv: then upgrade each branch to metaweave - for d in *; do bzr upgrade --format=metaweave $d; done [07:16] spiv: then run that python fragment to ensure you hav all the revisions from these branches - after pushing a rocketfuel-knit into the repo [07:17] After adjusting the paths in the python fragment... [07:18] spiv: you would have ~/launchpad/branch just as you do today [07:20] Right. The "." and "./devel" paths in the existing fragment confused me -- for some reason I find the "branch is here, but the repo is there, and a is parent dir of the branch" arrangement unexpected and thus disorientating until I realise what's going on. [07:21] for instance, heres how I am converting the rf branches [07:21] from bzrlib.ui.text import TextUIFactory [07:21] import bzrlib [07:21] import os [07:21] bzrlib.ui.ui_factory = TextUIFactory() [07:21] import bzrlib.repository [07:21] target=bzrlib.repository.Repository.open('.') [07:21] for branch in os.listdir('.'): [07:21] if branch == '.bzr': [07:21] continue [07:21] source=bzrlib.repository.Repository.open(branch) [07:21] target.fetch(source) [07:21] (on a related note, I find the fact that there are four seperate things that have formats confusing sometimes) [07:22] yes [07:22] its a compromise [07:22] there are four concepts - the control dir, the tree, branch and repo [07:22] we could have said there is one lockstep format [07:22] and that all change at once [07:22] It provides wonderful flexibility, but I have to concentrate sometimes to keep track of what's what in test cases and the like :) [07:22] yup [07:23] I'm not disagreeing with the design, just providing a datapoint you may find interesting. [07:23] spiv: the alternative is one format identifier with (#working tree formats)*(# of repository formats)*(#branch formats) values [07:23] jamesh: Or to simply disallow most combinations. [07:24] well [07:24] spiv: with shared repos it is useful [07:24] the nice thing is a plugin can install a new format of just the element it cares about [07:24] spiv: the format identifiers are attached to the directories where the data is stored [07:25] i.e. a faster tree format can be introduced by one plugin, and a better branch representation by another plugin [07:25] this is impossible with a single identifier [07:25] spiv: I can upgrade the repository to knits without having to touch the branches in the repo [07:25] jamesh: I agree. I like the capabilities this design offers. I'm just mentioning that I've sometimes been confused by it. [07:25] spiv: so, what would be really good is a suggestion to retain the capabilities - which are in use - but reduce the confusion factor [07:25] i.e. branch._branch_format, tree._tree_format perhaps ? [07:26] lifeless: that implies heirarchy [07:26] bah [07:26] I misread what you typed [07:26] :) [07:26] lifeless: that might help. I think calling "bzrdir" something like "controldir" would be clearer to my brain, too. [07:27] spiv: on disk, it is the '.bzr' dir :):):) [07:28] "bzrdir" has too many possible meanings for the casual coder -- e.g. "that's the dir with my bzr checkout" or "bzr branch"... [07:28] we considered controldir [07:28] but felt bzrdir was really on the money as an exact description [07:28] its possible that was wrong [07:28] Fair enough. [07:30] are readonly bound branches planned for bzr? [07:30] jamesh: I'm concerned about rsync usage [07:30] jamesh: because there is dataloss potential [07:31] standalone branches its clear that what you copy is what you gt [07:31] lifeless: sure. That's why I was asking if there was an equivalent way to push all my branches using sftp [07:31] shared repos you have to know to rsync the entire repo, and you have to never rsync from a different repo [07:32] Ah, crap. The hct/sourcerer part of the check_merge is bust. [07:32]