/srv/irclogs.ubuntu.com/2008/04/13/#bzr.txt

awmcclainDone.00:07
jelmerawmcclain: thanks :-)00:12
ubotuNew bug: #216542 in bzr "unable to do merge on windows" [Undecided,New] https://launchpad.net/bugs/21654200:15
ubotuNew bug: #216541 in bzr "bzr mv dies when using a checkout over http://" [Undecided,New] https://launchpad.net/bugs/21654100:16
LinnkHey guys, I'm using Bazaar on Ubuntu 7.10. I'm trying to use the gui (Olive) to view a diff of a file, but the diff window simply shows up blank00:29
jelmerLinnk: how are you using it exactly?00:29
LinnkI click the file I want to see a diff for and click the Diff button in the toolbar00:30
LinnkI figured that I would then be asked which versions to diff, but apparently not00:31
jelmerLinnk: I think that just checks what changes there are in the working tree00:36
jelmerso on a fresh checkout it's correct the window is empty00:36
Linnkah yeah, that explains why it suddenly works now that I've changed some files00:37
Linnkso I'll have to use the terminal for diff's between revisions?00:38
jelmerLinnk: You can use "bzr viz" to find a revision to show the diff for00:47
Linnkjelmer: Ok, thanks a lot :)00:48
antoranzGuys! How do I change the "remembered location" of a branch so I don't have to specify it on every "bzr merge" call?01:28
jelmerawmcclain: use --remember01:30
jelmers/awmcclain/antoranz/01:30
jelmerantoranz: or edit .bzr/branch/branch.conf01:31
antoranzwhat does bzr bind do?01:31
antoranzjelmer: what you said worked. Thanks01:32
bob2binds a local branch to a remote one01:33
bob2making it a checkout (ie commits go to both immediately)01:33
antoranzok01:36
ubotuNew bug: #216586 in bzr "annotate removed-revision feature" [Undecided,New] https://launchpad.net/bugs/21658602:06
awmcclainI'm really at a loss here... I cannot get the bzr-email plugin to work for the life of me. No log entries, nothing. I'm flummoxed.02:10
jelmerawmcclain: What did you do to set it up?02:19
awmcclainjelmer: I've installed the plugin into my site packages. I've verified that it shows up until the bzr commands02:27
awmcclain...02:27
awmcclainand02:27
awmcclainI've set the post_commit_to config variable in the branch.conf, and in ~/.bazaar/.bazaar.conf02:28
jelmerawmcclain: it shows up in "bzr plugins" you mean?02:30
awmcclaincorrect02:30
awmcclaini can also do bzr help email02:31
jelmerwhat os are you on?02:31
awmcclainubuntu gutsy02:31
awmcclainit iddn't work in 1.2, and still doesn't work on 1.4r102:31
awmcclainwhat should my config file look like, do you know?02:32
awmcclaini have02:32
awmcclain[DEFAULT]02:32
awmcclainpost_commit_to          = admin@fluther.com02:32
jelmeryeah, that should be sufficient I think02:34
jelmerrunning bzr commit doesn't trigger it?02:34
ubotuNew bug: #181534 in bzr-svn "Discards credentials specified in URL" [Medium,Fix committed] https://launchpad.net/bugs/18153402:46
schmichaelif i have bzr 1.3 installed what repo format should i use?03:54
schmichaelit seems to default to pack03:54
bob2the default, unless you have some special requirement (e.g. working with branches from svn)03:54
schmichaelbob2: thanks!03:54
ubotuNew bug: #216614 in bzr "should not immediately abort of .bzr/format can't be opened" [Undecided,New] https://launchpad.net/bugs/21661403:55
AfCthere is an annotation cache, right?03:59
AfCdoes it get corrupted? if so, how do you force it to be regenerated?03:59
spivAfC: not (yet) for pack formats.04:00
=== BasicMac is now known as BasicOSX
matidjelmer: Hi there. Any news on the issue with svn+https and bzr?05:51
awmcclainjelmer: No, running bzr commit doesn't trigger it. At all.06:30
awmcclainAre there any hidden log files I should check?06:30
spivawmcclain: ~/.bzr.log, maybe try "bzr -Dhooks commit ..." too.06:32
awmcclainhrm06:35
awmcclainthe -D switch is complaining06:35
awmcclainoh oh,never mind06:36
awmcclainA ha! Ok. It seems like the email only works if I commit ON the machine, not through SSH06:38
awmcclainWhy would it not work over bzr+ssh://? Is there a different way to configure the post_commit_to?06:43
=== mwhudson_ is now known as mwhudson
pygimorning10:24
wildfireis their a bzr equivalent of 'git add -i' (it allows you to select particular hunks of a file to add)12:45
oleavrwildfire: check out the interactive plugin at http://bazaar-vcs.org/BzrPlugins12:47
asabilwildfire: git add is different from bzr add12:47
asabilthe interactive plugin adds a -i to commit12:47
asabilthanks for the advertisement oleavr :D12:48
oleavrasabil: "uncle software, coming to a store near you" ;D12:49
asabillol12:49
bob2shelve kinda does the opposite12:51
* asabil needs to implement bzr revert -i when he gets free time and motivation12:53
wildfireoleavr, and I just copy the *.py into ~/.bazaar/plugins/ and it'll work?12:54
oleavrwildfire: copy the directory in there, yes12:55
asabilwildfire: cd ~/.bazaar/plugins12:55
asabilbzr branch lp:bzr-interactive interactive12:56
asabilwildfire: you will need to have a subfolder inside plugins12:56
wildfireasabil, thanks - that branch command seemed to do the trick12:58
asabilgreat13:00
asabillet me know if there is any problem with it13:02
wildfireasabil, *** Bazaar has encountered an internal error.13:11
wildfirewildfire@muspell:/etc/bind$ sudo bzr record-patch13:12
wildfirebzr: ERROR: bzrlib.patches.MalformedHunkHeader: Malformed hunk header.  Does not match format.13:12
wildfire'Binary files postfix/virtual.db\t2008-04-04 01:58:00 +0000 and postfix/virtual.db\t2008-04-10 09:06:09 +0000 differ\n'13:12
asabilcan you paste the traceback somewhere please13:12
wildfireasabil, http://pastebin.com/m15c6399a13:14
wildfirehmm, when recording the changes I have to give it a patch-name13:14
asabilnever tried with bzr 1.0.0 actually13:15
asabiland record-patch is a different thing than commit -i13:15
asabilboth bzr commit -i and record-patch are working here13:16
asabilusing bzr 1.3.113:16
asabilthey also worked with 1.1 and 1.2 iirc13:17
matthewlmccluredoes bazaar support  perforce foreign branches?13:17
bob2as in actual perforce branches, or something like them?13:17
asabilmatthewlmcclure: you can try bzr-fastimport, but never tested it myself13:18
=== mario_ is now known as pygi
matthewlmcclurean actual perforce branch13:18
asabilwildfire: ?? can you upgrade bzr ?13:18
matthewlmcclureasabil: i saw that, but i'm unclear how to provide input to bzr-fastimport13:19
asabilmatthewlmcclure: http://bazaar-vcs.org/BzrFastImport/FrontEnds13:20
matthewlmcclureone of the wiki pages recommends git-p4, but it looks like that tool is hardcoded to git13:20
datoif git-p4 outputs in git-fast-import format, bzr-fastimport should do (or attempt to) do something useful with it13:21
asabilright13:21
datobut I think that'll be for importing only, not to work with them as foreign branches (like bzr-svn does with subversion's)13:21
asabildato: seems like git-p4 runs git commands13:21
datoaha13:21
asabilproc = subprocess.Popen(["git", "rev-parse", branch], ...13:21
asabilmatthewlmcclure: git-p4 can be a good starting point for hacking a bzr-p413:22
matthewlmcclureasabil: that's what i thought; thanks for confirming13:22
asabilmatthewlmcclure: but as dato said, fastimport is only about importing13:23
asabilI don't know if that's enough for you13:23
matthewlmcclureright, i'd really prefer two-way foreign branch support13:23
asabilsomeone needs to step up and implement it then13:23
matthewlmcclurei'm looking for an interesting project to hack on, so i may give it a shot13:24
asabilgreat :)13:24
wildfireasabil, I'm not sure what version of ubuntu this machine is running13:24
wildfireasabil, and this is a server13:25
asabil:/13:25
wildfireasabil, so an upgrade needs to be co-ordinated amongst a larger set of people than just me13:25
asabilI understand13:25
asabilbut isn't it for your own usage ?13:26
asabilI mean, why would you need to install bzr on the server ?13:26
asabilwildfire: you don't really need bzr on the server13:28
wildfirewe do if we manage /etc with it13:29
asabilwait wait13:30
asabilyou seem to have called record patch on a binary file13:30
asabilthat's a bug in bzr-interactive I guess13:31
asabillet me try to fix13:31
matidHi there.13:37
matidA quick question - what does bzr up do on an unbound branch?13:37
asabilupdates the working tree13:40
asabilthis is useful when you push to a server13:41
asabilyou can run update on the server to update the working tree13:41
matidSo it's only useful if someone pushes code to my branch, right?13:41
asabilyep13:42
asabilfor unbound branches of course13:42
matidYeah, I know.13:42
matidAnd would bzr pull on an unbound branch be any different from bzr up on a checkout or a bound branch?13:43
matid(svn convert here, still failing to grasp all the differences ;))13:43
asabilit may be different if you pull from a different url13:46
asabiland a pull may not work if the branches have diverged13:46
asabil(in which case you need to merge)13:47
matidYou may need to merge with bzr up too, right?13:47
asabildidn't use bzr up extensively, but I think it will merge automatically13:48
asabilit would work as in svn13:48
asabilif you see what I mean13:48
matidOK, thanks.13:48
matidI kinda get it now ;)13:48
asabilwhereas bzr pull fails even when there are no conflicts13:48
asabilit fails simply because the code has diverged and requires a merge13:49
matidAhh... So up would be like pull + merge in case pull fails.13:49
asabilsomething like that13:49
asabil*I think*13:49
matidasabil: Thanks a lot.13:50
asabilyou're welcome13:50
dwtGuys, can somebody help me with this? I'm trying to update a repository to a specific tag, but I don't get how to do this. What seems obvious to me (bzr up -r tagname) doesn't seem to be the way to do this15:21
dwtAnd I'm lost finding this in the docs - though it has to be something easy. :/15:23
asabildwt: can you give more details ?15:27
asabilis it a checkout or a branch ?15:28
dwtI'm a bit new, I think its a branch, i.e. it has full history15:28
dwtIf thats what you meant.15:28
asabiland what do you mean to update to a specific tag ?15:28
asabilyes that's what I meant :)15:28
dwt:-)15:29
asabilso you branched from somewhere15:29
dwtJes.15:29
asabiland you want to rollback to a specific tag ?15:29
dwtWell, I am playing around with bzr-svn and have a checkout of the 0.4 branch15:29
dwtyes!15:29
asabilbzr help revert15:30
asabil:)15:30
dwtahhhh15:30
asabilor you can crate a new branch from that one15:30
asabil(that's generally better)15:30
dwtSo the best way would be to move this directory aside15:30
asabilbzr branch -r tag:mytag . ../branch-mytag15:30
dwtbranch from it, and only get revision up to the tag from the revision15:31
asabilyep15:31
dwtWhy exactly is that better? I mean, I don't want to start developing on this checkout just yet15:31
dwt(and probably never)15:31
asabilso that you don't need to checkout again too many revisions15:32
asabilif you want to go ahead15:32
asabilif you see what I mean15:32
dwtSo revert really removes the revisions from the repository?15:32
dwtuh, thats nastsy.15:32
asabilfrom your local branch15:32
dwtIs there not a simpler way to just go back in the history to a specific time?15:32
dwtWhile still retaining all the revisions in the repository?15:33
asabilactually I am not sure if revisions are removed from the branch15:35
* dwt is currently reading the revert docs15:35
dwtI'l look this up a bit and come back to tell what I found.15:36
asabiloki15:36
dwtThansk anyway for the help so far. :)15:36
dwtasabil: Well, the documentation in in bzr help revert is not completely clear on this, but <http://doc.bazaar-vcs.org/bzr.dev/en/user-guide/index.html#undoing-mistakes> says that it only throws away local commits.16:30
dwtI'm not sure what I should make of this16:31
dwtanyway for my usecase revert seems like the right thing for me16:31
asabilk16:31
radixrevert only modifies your working tree16:35
radixso it won't delete revisions16:35
dwtso also local commits are not deleted?16:35
dwtthanks for the clarification radix!16:36
radixsure thing16:36
dwtok, thanks and cu!17:37
rockyanyone know if there is an equivalent to tag_svn_revision for bzr in setup.cfg (ala python setuptools) ?18:25
cr3if I have a remote machine from which I need code updated from a bzr repository, but the machine only has incoming traffic and no outgoing traffic, can I update the remote machine from my local machine using push or somesuch?19:22
cr3when I actually did try push, I get the error that the remote machine does not have a .bzr directory, which kinda makes sense because it's not a repository19:22
cr3I wonder if I need the bzr-push-and-update plugin, but I think there's a way to make this work somehow19:25
matidjelmer: Hi there!20:27
matidjelmer: I've got a question regarding bzr-svn, got a minute?20:27
jelmermatid: sure20:28
jelmermatid: I posted a patch to the subversion development list that fixes the https issue, btw20:28
matidjelmer: Oh, cool.20:29
matidjelmer: Thanks a lot.20:29
matidjelmer: The question is - what is a preferred way of dealing with diverged branches in svn?20:29
jelmermatid: There is no preferred way; it's up to you, what do you like best?20:30
jelmermatid: You can merge and push, but that may potentially change your existing revision history in svn20:30
jelmermatid: Some people prefer rebasing before pushing20:30
matidjelmer: Let's say, I branch some code, work with it, but in the meantime someone updates svn. I did bzr pull but I asked me to merge. And so did I, but after a push a strange commit appeared in svn.20:30
matidjelmer: It was a duplicate of the commit that was done in between my branch and the push.20:31
matidjelmer: And to be honest with you I don't even know how subversion will cope with it. If it's diff based then it should simply ignore it.20:32
matidjelmer: So I was supposed to rebase, right?20:32
matidjelmer: Oh, in fact it reverted the changes, it's not the same.20:34
matidjelmer: Eh, it's the same after all. I don't get it...20:40
jelmermatid: "bzr push" will push the current mainline in your bzr branch20:54
matidjelmer: Let's say with got a situation like this:20:55
ubotuNew bug: #216924 in bzr "Push failed using (bzr push lp:). On windows machine" [Undecided,New] https://launchpad.net/bugs/21692420:55
jelmermatid: That may involve changing the current mainline in Subversion20:55
matidjelmer: I branch the svn code at revision 154. Now another person submits revision 155 and 156 to svn, whereas I make one commit in my bzr branch.20:56
matidjelmer: Now what I did was a bzr merge followed by bzr commit and bzr push.20:57
matidjelmer: Which resulted in a new svn revision containing duplicated 155, 156 and my bzr changes.20:57
matidjelmer: Is this expected behaviour?20:57
jelmermatid: Yes, because that's what's in your local bzr mainline20:59
jelmermatid: If you want to push something on top of what's in svn, use rebase20:59
matidjelmer: Is there a change what I just did (bzr merge and push) broke something?21:00
matidjelmer: Or is it just an innocent duplication?21:01
jelmermatid: It still contains the same data as is in your local bzr branch21:01
matidjelmer: But well, if I did a merge before I pushed it should also contain all the changes that were made in svn in the meantime, right?21:02
jelmermatid: yes21:02
matidjelmer: Which means that bzr pushed a some diffs which applied to svn trunk simply didn't do a thing, am I right?21:02
matidjelmer: I'm not really used to this kind of behaviour :)21:03
jelmeryou'll notice the same revisions are in the svn branch as are output by "bzr log --line"21:03
jelmermatid: Not sure I understand what you mean by "Which means that bzr pushed a some diffs which applied to svn trunk simply didn't do a thing, am I right?"21:04
matidHmm...21:05
matidjelmer: It seems like bzr log --line shows some differences between svn and bzr.21:05
jelmercan you be more specific?21:05
matidjelmer: I mean, there's one extra commit in svn between the moment I branched the code and the moment I pushed it.21:06
matidjelmer: This is a commit that I merged in bzr by using `bzr merge`21:06
jelmermatid: and it's still there if you use "svn log" on the full branch url?21:06
matidjelmer: Eee... It disappeared... How come?21:07
jelmermatid: it's not part of the mainline21:07
matidjelmer: You can't delete changesets in plain svn, or can you?21:08
jelmermatid: it's part of the right hand side history. You'll see if you run "bzr log" on the remote svn branch it'll show up indented21:08
jelmermatid: Nope, it's still part of the repository, just not part of the mainline history of that branch21:08
matidjelmer: Guess I've never stumbled upon this kind of thing in svn...21:10
matidjelmer: Which means that both solutions (rebase and merge&push) are going to result in the same code state in svn.21:11
matidjelmer: Yet push will rearrange the revision history.21:11
jelmermatid: After rebase, you still have to push21:12
matidjelmer: Yeah, it's not going to change anything in svn though. Just append new changesets, right?21:12
jelmermatid: yep21:12
matidjelmer: I guess I'll use rebase then.21:12
matidjelmer: I mean for me it makes no difference, but other people are not going to frown upon some strange things going on in svn :)21:13
jelmermatid: :-)21:15
matidjelmer: It's kinda strange since it looks like I committed changes someone else made earlier.21:15
jelmermatid: It matches the behaviour of merge, commit and push for native bzr branches21:16
jelmerand that's what bzr-svn tries to do21:16
matidjelmer: To me it looks like I'm trying to make others' changesets look like mine :D21:17
jelmermatid: the same thing will happen if you use svn merge with a subversion branch21:18
matidjelmer: Hm... It's just that in svn I used to do it the other way round.21:18
matidjelmer: Work on a branch, then merge changes into trunk and commit there.21:19
matidjelmer: I think this would also be possible if I simply kept one clean checkout of svn trunk and merge other bzr branches into it, right?21:19
lifelessabentley: ping21:23
lifelessmorning y'all21:23
abentleylifeless: pong21:23
lifelessI'm trying to get BB up and running again on squid-cache.org21:24
lifelessI'm a little confused by your response to the bug I filed21:24
jelmermatid: yes - but if you do that, each merged bzr branch will only show up as a single commit in svn21:24
jelmermatid: (since a bzr merge puts only one revision on mainline)21:24
abentleyI understood you were running TG 1.02 and SQLAlchemy 0.4.4.  Is that right?21:24
lifelessdid you mean that if I downgrade sqlalchemy somehow, it will fix the error, or that 1.0.4.3 is a hard dependency now21:25
matidjelmer: That's what I'd do in svn, but it seems like using rebase is a better solution.21:25
jelmermatid: yeah, rebase makes snese in this case21:25
lifelessabentley: yes, thats what freebsd ships21:26
matidjelmer: Cool. Is there any case in which bzr-like merge and push will prove superior to rebase?21:26
abentleylifeless: for revno 249 and later, 1.0.4.x is a hard dependency.21:27
jelmermatid: It will probably give better results combining two branches21:27
jelmermatid: Rebase simply does diff + patch for each of the revisions you have that aren't in upstream21:27
lifelessabentley: you wouldn't happen to know if loggerhead is compatible with 1.0.4.x  ?21:27
abentleyAt least, in my experience, TG 1.0.2 did not work properly with SQLAlchemy 0.421:28
matidjelmer: OK. Which means that in case of not-so-complicated merges it should work the same.21:28
abentleylifeless: Sorry, I don't know that.21:28
lifelessthats ok, wishful thinking :P21:29
lifelessI find myself thinking unpleasant thoughts towards the turbogears maintainers21:29
lifelessthe dependency tree seems unpleasant21:30
abentleyI'm quite disheartened about the whole thing.21:30
abentleyEspecially that SQLAlchemy managed to ship two releases which had blatent bugs that my measly test suite caught.21:30
lifelesstests FTW21:30
lifelessmwhudson: ping21:31
mwhudsonlifeless: hi21:31
abentleyThis was stupid stuff where they failed to import a symbol they used.21:31
lifeless!!!21:32
lifelessthats apalling21:32
abentleyyou've got that right.21:32
lifelessI do want to talk about the tension that bubbled out on thursday; however sunday morning I woke up with a head cold21:36
jelmermatid: yeah21:36
lifelessI'd rather be at my best when debugging important things21:37
lifelessabentley: welcome back21:43
abentleythanks.  Last thing I saw was "I'd rather be at my best when debugging important things"21:43
lifelessabentley: that was the last thing I wrote21:43
abentleyCool.21:44
lifelessaarrgghh21:59
lifelessabentley: you'll love this. I'm trying to update the turbogears package for freebsd22:00
lifeless1.0.4.3 wants turbojson 1.1.222:00
lifelessthere is no egg for 1.1.222:00
abentleyThat's nutsy22:01
lifelesshttp://files.turbogears.org/eggs/ is where the package is looking22:01
abentley1.1.2 is available on PyPI, though.  It doesn't fall pack to that?22:02
abentleys/pack/back22:02
lifelessno22:02
abentleyStrange.  I thought it did.22:03
lifelesseasyinstall may22:03
abentleyOh.22:04
abentleyYes, that's what I was talking about.22:04
lifelessI'm really not sure what to do at this point22:05
threeveI'm trying to get bzr-svn going on Windows using Python 2.5(.2).  I have svn 1.4.6 installed, an have installed bzr 1.3 and bzr-svn 0.4.9 using the binary installers, and installed the updated svn 1.4.6 python bindings.  `bzr version` now crashes for me.  Have I missed something I need to install?22:06
wildfirelifeless, i think going back to linux is the answer ;-)22:08
lifelesswildfire: this machine has never been linux :(22:09
lifelesssquid-cache.org22:09
jelmerthreeve: How did you install svn 1.4.6 ?22:09
threevejelmer: windows binary installer from Tigris, iirc.22:09
cr3interesting coincidence, I'm installing squid as we speak22:10
wildfirelifeless, ahh, right. well that's nothing a chroot couldn't solve if you get really stumped22:10
lifelesswildfire: but even if I did that, this points out a generic problem for folk that are not on development editions of linux22:10
jelmerthreeve: You can't use a stock subversion 1.4. You need either the one with the patches linked from the bzr-svn wiki page or Subversion 1.5.22:10
wildfirelifeless, i don't think developers will ever be 'generic folk' personally. Most people never miss the 'new'22:11
lifelesswildfire: EPARSE ?22:12
threevejelmer: Okay, I thought that might be the case but I thought maybe only the patched bindings were necessary.  Building a new Subversion now.  Thanks22:13
lifelesscr3: :P22:13
wildfirelifeless, most people are not neophiliac's like you and I and most other developers. People who are not on development editions will never, generally, run into the issue since "shiny" isn't what they care about - they are 'generic folk'.22:16
wildfire Therefore the problems of generic folk and development folk are not normally intertwingled.22:16
jelmerwildfire: I think more people care about "shiny" than just a couple of developers :-)22:17
lifelesswildfire: for this discussion, I'm wearing the hat of generic folk22:17
lifelesswildfire: I don't want a shiny bb, I want a working bb.22:17
lifelesswildfire: dependency issues between components used by bb have forced bb to require versions that are not available on freebsd; either by being too old, or once fixed, by being too new.22:18
wildfirelifeless, with my (slight-tipsy) sysadmin hat on, I'd suggest the best thing would be a specific python chroot devoted to have the right dependancies for tg, sqlalchemy and bb all installed at the specific versions22:21
wildfires/to have/to having/22:21
wildfireonce they OS has the appropriate ones you can always migrate it back out of the chroot22:21
lifelesswildfire: I don't want to sysadmin this service :P. So I'm simply punting the problem to the -noc team there22:22
Prettohi all22:25
mwhudsonthis is strange, right:23:08
mwhudsonmwh@grond:debian-packaging$ cat .bzr/branch/last-revision23:08
mwhudson2 ted@canonical.com-20080401051631-3zsnbir02j3c0ihp23:08
mwhudsonmwh@grond:debian-packaging$ bzr revision-history | wc -l23:08
mwhudson3023:08
mwhudson?23:08
jelmermwhudson: yeah, that's very weird23:08
lifelessthe cached revcount would appear to be wrong23:13
mwhudsonsure looks like it23:14
mwhudsoni can try and grab ted and ask what he did i guess23:15
mwhudson(it's this branch)23:15
mwhudsonhttps://code.edge.launchpad.net/~ted-gould/gnome-power/debian-packaging23:15
lifelessabentley: so the api I proposed in my new stream doco doesn't work23:15
abentleyI guess we're all a bunch of boobs, then.23:16
lifelessabentley: I think it will work better if rather than returning the bytes, I return a factory object that can return as_knit, as_fulltext, etc.23:16
lifelessI mean, it works ok in the common case23:16
lifelessbut isn't able to handle the iter_rev_trees thing. I tink that the small change above will.23:17
lifelessso I'm doing a hallway test :P23:17
lifelessbreakfast23:18
abentleyI don't get it.  Isn't this just for fetch?23:20
lifelessits for fetch including the case of plain -> rich roots23:22
lifelessI have a call in ~8 minutes with thumper and an errand to run first, back to chat after that23:23
igcmorning23:53
jelmerHi Ian!23:54
igchi jelmer - I'm back from holidays23:55
igcfiji was awesome23:55
jelmer:-)23:55

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!