=== jaguarondi_ [n=david@82.243-246-81.adsl-dyn.isp.belgacom.be] has left #bzr []
=== cprov is now known as cprov-afk
=== jml [n=jml@ppp121-44-213-76.lns1.hba1.internode.on.net] has joined #bzr
=== Demitar [n=demitar@c-212-031-182-147.cust.broadway.se] has joined #bzr
=== BasicOSX [n=BasicOSX@216-250-174-201.static.iphouse.net] has joined #bzr
=== lifeless [n=robertc@ppp245-86.static.internode.on.net] has joined #bzr
lifelessyay net fuckage01:08
=== jkakar [n=jkakar@204-174-36-45.dhcp802.dsl.ucc-net.ca] has joined #bzr
=== pete__c_ [n=pete@032-461-712.area7.spcsdns.net] has joined #bzr
=== mpt [n=mpt@canonical/launchpad/mpt] has joined #bzr
=== Admiral_Chicago [n=FreddyM@ubuntu/member/admiral-chicago] has joined #bzr
mptOk, this may be a silly question01:27
mptBut is there any way to revert to how a file/tree looked on a particular date?01:28
mptShort of first using bzr log to find the newest revision before that date?01:28
Pengbzr revert -r date:2007-09-3001:28
PengSee 'bzr help revisionspec'.01:28
mptAnd that's not mentioned directly in "bzr revert --help" because revisionspec is also used by diff01:31
=== Admiral_Chicago [n=FreddyM@st074039212101.monm.edu] has joined #bzr
=== pete__c [n=pete@032-461-712.area7.spcsdns.net] has joined #bzr
=== BasicOSX [n=BasicOSX@216-250-174-201.static.iphouse.net] has joined #bzr
=== AfC [i=andrew@office.syd.operationaldynamics.com] has joined #bzr
lifelessmpt: we should add a seealso to revisionspec I guess01:41
mptlifeless, it already says "See 'help revisionspec' for details", I just didn't realize that the "details" would be interesting or relevant to ARG01:43
mptbecause they were on a separate line01:45
mptwhich is an accident of how long "-r ARG, --revision=ARG" is01:45
Pengmpt: A lot of commands use -r.01:46
=== bitmonk [n=justizin@adsl-76-192-203-38.dsl.pltn13.sbcglobal.net] has joined #bzr
=== poolie [n=mbp@ppp112-44.static.internode.on.net] has joined #bzr
=== bitmonk [n=justizin@adsl-76-192-203-38.dsl.pltn13.sbcglobal.net] has joined #bzr
=== jml [n=jml@ppp108-61.static.internode.on.net] has joined #bzr
lifelessmpt: this is true, but can we make it more clear02:01
pooliempt, lifeless, hello02:12
=== BasicOSX [n=BasicOSX@216-250-174-201.static.iphouse.net] has joined #bzr
=== kiko is now known as kiko-zzz
=== orospakr [n=orospakr@] has joined #bzr
=== cprov [n=cprov@canonical/launchpad/cprov] has joined #bzr
=== ajmitch_ [n=ajmitch@port166-123.ubs.maxnet.net.nz] has joined #bzr
=== jkakar [n=jkakar@204-174-36-45.dhcp802.dsl.ucc-net.ca] has joined #bzr
=== cprov [n=cprov@canonical/launchpad/cprov] has joined #bzr
=== poolie [n=mbp@ppp112-44.static.internode.on.net] has joined #bzr
=== AfC [i=andrew@office.syd.operationaldynamics.com] has joined #bzr
=== Admiral_Chicago [n=FreddyM@ubuntu/member/admiral-chicago] has joined #bzr
=== mpt [n=mpt@canonical/launchpad/mpt] has joined #bzr
=== lifeless [n=robertc@ppp245-86.static.internode.on.net] has joined #bzr
=== abadger1999 [n=abadger1@] has joined #bzr
=== asak [n=alexis@201-0-38-199.dsl.telesp.net.br] has joined #bzr
=== pacharasil_ [n=astromme@12-214-205-206.client.mchsi.com] has joined #bzr
=== herzel104 [i=herzel@gateway/tor/x-3eac73957eb94f65] has joined #bzr
=== Mez_ [n=Mez@ubuntu/member/mez] has joined #bzr
=== Vernius [n=tomger@p508AF23C.dip.t-dialin.net] has joined #bzr
=== thatch [n=thatch@pool-71-96-248-177.dfw.dsl-w.verizon.net] has joined #bzr
=== bigdog [n=scmikes@72-197-8-8-arpa.cust.cinci.current.net] has joined #bzr
=== bigdo1 [n=scmikes@72-197-8-8-arpa.cust.cinci.current.net] has joined #bzr
=== michelp [n=michelp@69-30-72-119.dq1sf.easystreet.com] has joined #bzr
=== kiko-zzz [n=kiko@canonical/launchpad/pdpc.supporter.active.kiko] has joined #bzr
=== ubotu [n=ubotu@ubuntu/bot/ubotu] has joined #bzr
=== niemeyer [n=niemeyer@200-140-230-150.ctame705.dsl.brasiltelecom.net.br] has joined #bzr
=== jamesh [n=james@canonical/launchpad/jamesh] has joined #bzr
=== cory_ [i=cory@zeus.penguinhosting.net] has joined #bzr
=== AnMaster [n=AnMaster@unaffiliated/anmaster] has joined #bzr
=== dous_ [n=dous@ubuntu/member/dous] has joined #bzr
=== statik [n=emurphy@canonical/launchpad/statik] has joined #bzr
=== abentley [n=abentley@] has joined #bzr
=== joejaxx [i=joejaxx@fluxbuntu/founder/joejaxx] has joined #bzr
=== arjenAU [n=arjen@mysql/community/arjenAU] has joined #bzr
=== elijah [n=whatever@c-69-252-219-78.hsd1.nm.comcast.net] has joined #bzr
=== vila [n=vila@lec67-4-82-230-53-244.fbx.proxad.net] has joined #bzr
=== mw [n=mw@] has joined #bzr
=== BjornT [n=bjorn@canonical/launchpad/BjornT] has joined #bzr
=== _logger_ [n=_logger@adsl-75-51-62-134.dsl.chcgil.sbcglobal.net] has joined #bzr
=== probablydrew [n=drew@ip72-211-146-73.tc.ph.cox.net] has joined #bzr
=== duckx [n=Duck@tox.dyndns.org] has joined #bzr
=== Vantage13 [n=Vantage@www.toddcharron.com] has joined #bzr
=== elmo [n=james@83-216-156-21.jamest747.adsl.metronet.co.uk] has joined #bzr
=== welterde [n=welterde@gandalf.srv.welterde.de] has joined #bzr
=== mlh [n=mlh@c211-30-211-232.belrs1.nsw.optusnet.com.au] has joined #bzr
=== hmeland [i=29578@klodrik.uio.no] has joined #bzr
=== metze_asleep [n=metze@ip-217-172-181-76.mx-netz.de] has joined #bzr
=== mwh [n=mwh@62-31-157-102.cable.ubr01.azte.blueyonder.co.uk] has joined #bzr
=== spiv [n=andrew@] has joined #bzr
=== Solarion [n=solarion@cruftix.physics.uiowa.edu] has joined #bzr
=== sii [n=sii@tranquillity.sii.se] has joined #bzr
=== LarstiQ [n=larstiq@cust.7.157.adsl.cistron.nl] has joined #bzr
=== meuh [n=meuh@pdpc/supporter/active/meuh] has joined #bzr
=== jeremyb [n=jeremy@unaffiliated/jeremyb] has joined #bzr
=== james_w [i=jw2328@jameswestby.net] has joined #bzr
=== alla [n=alla@soy.cyber.com.au] has joined #bzr
=== Sigma [n=yann@pdpc/supporter/active/Sigma] has joined #bzr
=== jrydberg [n=johan@] has joined #bzr
=== mneptok [n=mneptok@canonical/support/mneptok] has joined #bzr
=== radix [n=radix@] has joined #bzr
=== Peng [n=mnordhof@fl-69-69-140-112.dyn.embarqhsd.net] has joined #bzr
=== ike [i=ike@unaffiliated/ike] has joined #bzr
=== grantgm [n=gabriel@d57-194-175.home.cgocable.net] has joined #bzr
=== taaz [n=dlehn@] has joined #bzr
=== [PUPPETS] Gonzo [i=gonzo@] has joined #bzr
=== SteveA [n=steve@canonical/launchpad/SteveA] has joined #bzr
=== dato [n=adeodato@debian/developer/adeodato] has joined #bzr
=== siretart [i=siretart@ubuntu/member/siretart] has joined #bzr
=== beuno [n=beuno@ubuntu/member/beuno] has joined #bzr
=== tsuno [n=michael@ninthorder.com] has joined #bzr
=== dirker [n=dirker@woosome.net] has joined #bzr
=== ryanakca [n=ryan@ubuntu/member/ryanakca] has joined #bzr
=== Odd_Bloke [i=oddbloke@compsoc.sunion.warwick.ac.uk] has joined #bzr
=== NfNitLoop [i=codyc@cpe-70-112-28-217.austin.res.rr.com] has joined #bzr
=== uws [n=mathilda@] has joined #bzr
=== fullermd [n=fullermd@adsl-072-148-013-213.sip.jan.bellsouth.net] has joined #bzr
=== quicksilver [n=jules@] has joined #bzr
=== mpt [n=mpt@canonical/launchpad/mpt] has left #bzr ["http://mpt.net.nz/"]
=== ajmitch_ is now known as ajmitch
=== Mez [n=mez@ubuntu/member/mez] has joined #bzr
=== pete__c [n=pete@032-461-712.area7.spcsdns.net] has joined #bzr
=== jkakar [n=jkakar@204-174-36-45.dhcp802.dsl.ucc-net.ca] has joined #bzr
=== marianom [n=marianom@ubuntu/member/marianom] has left #bzr []
=== jml [n=jml@ppp108-61.static.internode.on.net] has joined #bzr
lifelesspoolie: just filed a bug03:13
ubotuNew bug: #147916 in bzr "support for checkout of readonly url has regressed" [Undecided,New]  https://launchpad.net/bugs/14791603:20
=== BasicOSX [n=BasicOSX@216-250-174-201.static.iphouse.net] has joined #bzr
spivhttp://live.gnome.org/iogrind looks shiny03:30
lifelessis it a blocktrace wrapper?03:33
=== orospakr_ [n=orospakr@CPE001c1019cfc4-CM0011ae034e04.cpe.net.cable.rogers.com] has joined #bzr
spivlifeless: the page says03:46
spiviogrind works in 3 parts:03:46
spiv    * tracing the application using valgrind03:46
spiv    * snapshotting the filesystem03:46
spiv    * simulating the trace, against a snapshot to visualise.03:46
lifelessshould use blktrace ;)03:47
lifelessno need for snapshot03:47
lifelessjelmer: yo04:00
=== BasicOSX [n=BasicOSX@216-250-174-201.static.iphouse.net] has joined #bzr
ubotuNew bug: #147927 in bzr "use python -O (assertions off) when running installed copy" [Undecided,New]  https://launchpad.net/bugs/14792704:05
lifelesspoolie: another patch sent in04:22
=== Verterok [n=ggonzale@75-108-235-201.fibertel.com.ar] has joined #bzr
jelmerlifeless: hi04:40
lifelessyour commit mails still say file:///04:41
lifelessyou need a public_url entry in your config04:41
VerterokI don't known if this is a bug or a problem of my installation, but I'm getting a exit value =1 when I run 'bzr diff'04:52
=== yminsky [n=yminsky@user-0cevcqv.cable.mindspring.com] has joined #bzr
VerterokI found this yesterday, while running the test cases of BazaarClient (the java library, part of bzr-eclipse) my test case for diff is broken and is because 'bzr diff' return a exit value = 1, but the output I get is ok04:53
lifelessVerterok: its a feature04:56
lifeless1 - changed04:56
lifeless2 - unrepresentable changes04:56
lifeless3 - error04:56
lifeless0 - no change04:56
Verteroklifeless: thanks, now you tell me, It's a nice feature :D04:57
lifelesscould you file a bug though, bzr help diff should list this04:58
Verterokok, I'll do that04:58
=== Admiral_Chicago [n=FreddyM@ubuntu/member/admiral-chicago] has joined #bzr
ubotuNew bug: #147938 in bzr "bzr help diff should list the meaning of exit values" [Undecided,New]  https://launchpad.net/bugs/14793805:10
=== bigdog [n=scmikes@72-197-8-8-arpa.cust.cinci.current.net] has joined #bzr
=== Admiral_Chicago_ [n=FreddyM@st074039212101.monm.edu] has joined #bzr
=== Admiral_Chicago_ is now known as Admiral_Chicago
=== Admiral_Chicago [n=FreddyM@ubuntu/member/admiral-chicago] has joined #bzr
poolielifeless, are you sure bug 147916 is real?05:43
ubotuLaunchpad bug 147916 in bzr "support for checkout of readonly url has regressed" [High,Incomplete]  https://launchpad.net/bugs/14791605:43
lifelessbut I may be wrong05:44
lifelessor misjudging some root cause05:44
lifelessspiv: damn this patch is long05:44
pooliespiv, can you explain why you want bug 106898?05:45
ubotuLaunchpad bug 106898 in bzr "put_bytes should raise a specific exception when given unicode" [Undecided,New]  https://launchpad.net/bugs/10689805:45
=== jml [n=jml@ppp108-61.static.internode.on.net] has joined #bzr
=== BasicOSX [n=BasicOSX@] has joined #bzr
lifelessspiv: review sent06:18
poolielifeless, i can't reproduce any failure with readonly branches, nor find a likely report in mail06:20
pooliethere may well be one that i can't find06:20
pooliebut for now, i'm going to just work on the other bit - better message when trying to commit to a readonly branch06:20
pooliei think it may be enough to (add a test and) just make that error a user error06:22
poolieand check the message is reasonable06:22
lifelessbbiab, fooding06:31
poolieis it just me or is BB timing out a lot?06:41
lifelessjust you ?06:56
lifelessas in, it works for me07:00
=== jamesh_ [n=james@canonical/launchpad/jamesh] has joined #bzr
=== jamesh_ is now known as jamesh
=== Admiral_Chicago [n=FreddyM@st074039212101.monm.edu] has joined #bzr
lifelessspiv: ping07:56
spivlifeless: pong07:57
lifelessyou promised me a review :)07:57
spivlifeless: thinking of which, lp reviewers meeting in a couple of minutes...07:58
lifelessoh crud07:59
lifelessmy stomach has just decided to throw spasms at me07:59
spivIt dislikes the launchpad review team that much? ;)07:59
lifelessunrelated I think, but I'm going to do a runner08:00
=== lifeless toilets
spivpoolie: I think 106898 was motivated by wanting to know what to catch in test_put_bytes_unicode.  UnicodeEncodeError is raised by some transports, but that seems strange (we don't want to try encode unicode in that method, so why should it raise that?).  Some others raise AssertionError, which always feels a bit funny to catch to me but I guess can be ok.08:36
pooliei guess the heart of it is08:38
=== hdima [n=hdima@idealer.cust.smartspb.net] has joined #bzr
pooliei'm not sure how much we should have apis promise they will reject invalid input08:38
spivIn that they should reject it, but not promise specifically how?08:38
spivi.e. we should test simply for Exception in test_put_bytes_unicode and stop worrying about the details?08:39
lifelesspoolie: I think its reasonable to promise when its a cheap promise; and/or the api is at the edge of a subsystem08:40
pooliethat seems like a good guideline08:40
pooliespiv, well, why are you writing this test?08:40
spivI don't really remember why I wrote it.  (Or if I wrote it or just touched it?)08:41
spivBut it seems good to ensure that put_bytes will not silently accept unicode strings as if they are bytes.08:41
spivOtherwise with sys.getdefaultencoding() == 'ascii', which it is by default, it's easy for it to appear to work reliably when testing, and then fail on real data that isn't 7-bit ascii.08:42
poolieyes, that's true08:43
pooliei would probably add TypeError or ValueError or both to the list of exceptions it can raise08:43
pooliei don't think we need to test that it raises one particular exception08:43
pooliei think declaring a new class would almost certainly be excessive08:44
spivI agree that a new class would be excessive.08:44
spivTypeError seems reasonable to me.  I guess the main thing that bugs me about that test as-is is that UnicodeEncodeError seems like a bogus exception to raise.08:45
spivHmm, and ideally, it should raise when fed u'foo', not just u'\u1234', according to my argument above :)08:45
lifelessTypeError requires LBYL08:45
spiv(But the test currently only tests with u'\u1234')08:46
=== metze_asleep is now known as metze
pooliespiv, i agree that it should do this08:51
pooliecheck the actual type rather than just whether it's convertible08:51
lifelessthe point is that it shouldn't be converted at all08:54
lifelesspoolie: 139478 would be the regression08:56
pooliebug 13947808:58
ubotuLaunchpad bug 139478 in bzr "UnlockableTransport running update in checkout of readonly branch" [Medium,Triaged]  https://launchpad.net/bugs/13947808:58
poolienow that bug numbers are 6 digits maybe ubotu and the markup code should just always recognize them.08:58
pooliei'm working on those two now08:59
lifelessspiv: so, is that review pending? or no-comment ?08:59
spivlifeless: pending09:00
=== Lo-lan-do [n=roland@mirexpress.internal.placard.fr.eu.org] has joined #bzr
=== jml [n=jml@ppp121-44-213-76.lns1.hba1.internode.on.net] has joined #bzr
=== pbor [n=urk@host42-87-dynamic.1-79-r.retail.telecomitalia.it] has joined #bzr
=== pbor [n=urk@host42-87-dynamic.1-79-r.retail.telecomitalia.it] has joined #bzr
=== g0ph3r [n=g0ph3r@p57A09B8E.dip0.t-ipconnect.de] has joined #bzr
ubotuNew bug: #147986 in bzr "branch in test root directory can cause confusing results" [Medium,Confirmed]  https://launchpad.net/bugs/14798609:35
=== BasicOSX [n=BasicOSX@] has joined #bzr
=== allenap [n=allenap@87-194-166-60.bethere.co.uk] has joined #bzr
=== BasicMac [n=BasicOSX@warden.real-time.com] has joined #bzr
=== Zindar [n=erik@stockholm.ardendo.se] has joined #bzr
=== mrevell [n=matthew@canonical/launchpad/mrevell] has joined #bzr
pooliemrevell, hi09:57
mrevellhi poolie09:57
mrevellOver the 30 - 45 minutes, we're going to be discussing Bazaar documentation.10:00
mrevellWelcome to the meeting and thanks for coming :)10:00
mrevellThe aim of this meeting is to identify gaps in the current Bazaar docs.10:01
mrevellYesterday we had a similar meeting and the main issues raised were:10:01
mrevell* We need examples for as many use cases as possible for each command in bzr help/user reference.10:01
mrevell* We need good coverage of what sort of conflicts can happen, how you can provoke them, and how to clean them up.10:01
mrevell* We should make the split between user reference and user manual clearer.10:01
mrevellSo, I'd be keen to hear what you guys feel we're currently missing. I'd like to cover:10:02
mrevell* The user reference: do we have an entry for each command, should we cover more advanced topics in the user reference?10:02
pooliethat's a good list10:02
Lo-lan-doTwo meetings a day?  WHat kind of bureaucratic monster has #bzr become?10:03
mrevellLo-lan-do: The other was yesterday my time :)10:03
fullermdHe's just trying to have one without me around.10:03
Lo-lan-domrevell: Mine too, but one every twelve hours still qualifies as two daily here :-)10:03
mrevell* The user manual: should this become a straight tutorial, with the reference materials moving into the user reference?10:03
mrevellLo-lan-do: Fair point :)10:04
poolieLo-lan-do, they won't repeat daily10:04
mrevellSo, starting with the user reference: have you noticed any obvious gaps in bzr help?10:05
lifelesspacks are now annotation-free; this means their initial commit for any experimentation will be 30 seconds faster than they were yesterday.10:05
lifelessand I'm going to eat, sorry mrevell I will read and comment on minutes though, if there are any10:05
mrevelllifeless: thanks10:05
pooliemrevell, i think there are some gaps,10:06
mrevelllifeless: I'll post minutes to the bazaar list later today10:06
=== lifeless waves
pooliethere's a gap that the commands are not always explained from the right perspective of the person first reading about the command10:06
mrevellpoolie: Ah, interesting.10:06
pooliea good example might be, um10:06
pooliewell, an ok example is 'bzr help send'10:07
poolieit seems a bit like it just jumps into the details10:07
mrevellpoolie: Yeah, I can see that.10:08
pooliei think the other thing that may be happening with the manual vs reference10:08
poolieis that the reference is taken from the materials in the help text10:08
poolieif we stick with this distinction, the online help will be all reference-type material, not introductory10:09
poolieand i'm not sure that's quite right10:09
pooliemaybe it's ok, as long as they have a brief introduction to whatever topic they're talking about10:09
=== mvo [n=egon@p54A66FA4.dip.t-dialin.net] has joined #bzr
mrevellRight, yeah, I agree the online help should continue to have an introduction to each topic and should ease the reader into it10:11
pooliemrevell, did people say more yesterday about what that split should be?10:11
mrevellpoolie: Just a moment, I'll put out a quote.10:11
mrevellfullermd suggested dividing the documentation along these lines, which I broadly agree with:10:12
mrevellfullermdOne is the "quick start".  That's the "bzr in 5 minutes", the "here-kid-the-first-one-is-free" stuff.10:13
mrevellfullermdThe second is the more miniseries-style tutorial stuff, which are individual pieces, but follow a reasonable progression without too much overlap.  Taht would be the "Learning bzr" sort of doc.10:13
mrevellfullermdAnd the third would be the reference.  In-depth discussion of commands and use-cases, lists of config options and revspecs, et10:13
=== mwh [n=mwh@62-31-157-102.cable.ubr01.azte.blueyonder.co.uk] has joined #bzr
mrevellAlthough I take the point that the reference must include introductory material for the online help.10:14
fullermdYou can model those three as "get the flavor of bzr/get a recipe for a quick project contribution", "learn bzr", and "reference bzr".10:15
=== boggle [n=spindler@modemcable212.211-70-69.mc.videotron.ca] has joined #bzr
pooliethat sounds pretty good10:17
=== n2diy [n=darryl@wlk-barre-208-103-148-32.dynamic-dialup.coretel.net] has joined #bzr
mrevellSo, for the user reference we have the suggestion that not all entries are correctly targeted at someone who needs an introduction to a command. Thanks for that poolie.10:18
mrevellThanks fullermd also10:18
pooliei think the only thing to do is to go through them one by one with new-user glasses on10:18
mrevellpoolie: I have those glasses :)10:19
pooliei think the main thing is that the first bit of the description should be a 1-5 sentence summary of what the command is for10:19
pooliethe purpose10:19
=== pbor would like a tips-and-tricks page/FAQ with quick oneliners for common stuff
mrevellthanks pbor10:19
pborI just expressed the desire to have it not to write it, so nothing to thank me about :)10:20
mrevellpoolie: Some of our descriptions are quite a bit longer than 1 - 5 sentences right now. One thing that came up yesterday was that it's sometimes difficult to be concise10:20
mrevellpbor: Thanks for the suggestion :)10:20
mrevellpoolie: Although obviously we can make the writing as tight as possible10:21
pooliepbor, yes, i think a faq would be a good idea -10:21
poolieparticularly a single clearly-identified faq10:21
pooliei've been wondering if we should use answers.launchpad.net for that10:21
poolie(which i posted about recently)10:21
poolieit has some advantages, like trying to guide people who have new questions to the existing answers10:22
mrevellpoolie: So, I like the idea of ensuring the most important info is in the first 1 - 5 sentences10:22
poolieand linking to bugs if the answer relates to a bug, though at the moment only weakly so10:22
pooliei agree that sometimes it is hard to fit it in that limit10:22
pooliethis is partly a problem of knowing just how much you ought to explain10:23
poolieobviously we don't want every command's help going from first principles10:23
mrevellpoolie: I'll tkae an action item of looking at a good way of using the Answers FAQ system for bzr10:25
mrevellI'd like to move onto the user manual, unless anyone has more to say about the user reference.10:26
poolieso for the manual10:28
mrevellI think the user guide's weakest point, at the moment, is in advanced topics.10:28
mrevellPerhaps some material could move out of the current tutorial10:28
mrevellinto advanced topics10:29
=== fullermd somewhat disagrees.
mrevellfullermd: Please go ahead10:29
fullermdWell, it could just be a taxonomy issue, in what we want to have where.10:30
pooliein fullermd's description it looks like there's just one pretty short tutorial, and then the user's guide, and not a long tutorial10:30
fullermdBut I think of a user guide/manual to be the thing you sit down and read through to understand the program and what you'll do with it.10:30
fullermdThe current User Guide is just a collection of rather independent articles.  It's random-access.10:30
fullermd(that may be a more meta position than we want to go into, though)10:31
mrevellfullermd: I agree that we need to make the user guide more cohesive, and that each section should progress naturally one to the next.10:31
fullermdWe don't currently really have a place where we can say to new users "Go here, and read from here to there, and you'll have a good understanding of bzr"; that's what I'd want a User Guide to be.10:32
fullermd(in fairness, that doesn't seem to be what the current UG is _trying_ to do, so...)10:33
pooliei agree about cohesion and flow too10:34
pooliei think that's because it's acreted rather than because it's particularly what people want10:34
fullermdYah.  It's more a "Hey, we have these docs; we better link to them all".10:34
poolieso what, if anything, would be the difference between such a guide, and an extended tutorial?10:34
mrevellfullermd: Right. So, as a relatively inexperienced Bazaar user I'm in a good position to see how we should shape that sort of guide. I think your three split model is a great suggestion but I'm concerned that, because the user ref is also bzr help, we shouldn't overload that. Perhaps we need a rewritten tutorial and then further articles that cover "further reading" type topics10:34
poolieit seems like they might cover the same concepts and commands10:35
pooliebut a tutorial has more of a continuing worked example10:35
fullermdNone, really; that's sort of where I want it to be.  Go in one end of it new, come out the other end with a working bzr gestalt.10:35
pooliemrevell, what kind of thing are you thinking of as 'further reading'?10:35
fullermdWhen I read "tutorial", I tend to read it more as "recipe"; it tells you the steps, and maybe a little about why you take them, but it doesn't leave you with the gestalt.10:36
mrevellpoolie: For example: hosting a team branch in Launchpad, or running a bzr smart server.10:36
fullermdWell, that comes back to my opinion about the place of 'bzr help'.  But I think I'm minority there.10:36
mrevellpoolie: Topics that aren't essential to everyday use of bzr10:37
fullermdI think the User Guide should very much reference the User Reference for more in-depth coverage.10:37
mrevellpoolie: and perhaps that won't be applicable to everyone.10:37
fullermde.g., the USer Guide should talk about the smart server and why you might use it, but setting it up should be the Reference's province.10:37
poolieactually i disagree about that particular case10:38
mrevellfullermd: I think my concern there is that it's not necessarily a clean break between the two.10:38
mrevellpoolie: Ah, okay. Well, perhaps using some of the community's tools such as bzr-svn.10:39
poolieok, so the guide should give you a map to most of the content in the reference?10:40
fullermdI picture the guide as giving you a solid working understanding.  Read it, then you can comfortably use bzr for your projects.10:41
fullermdReference would be more details of each command and its options (--reprocess was an example I used yesterday) and more involved cases where you'd use them, detail coverage of a spectrum of workflows, etc.10:42
mrevellfullermd: Do you think all of that should be in the online help?10:43
pooliemy default position for the online help10:44
fullermdI don't, no.  I want quick-ref.  "I know the concepts, remind me where this command fits and what options it has".  Describing just what the options do and what their side-effects are can be a multi-paragraph endeavor.10:44
poolie(i'm willing to change)10:44
poolieis that, well, what fullermd just said, pretty much10:44
pooliea typical user, if they only had the help and not the guide, could work things out but they'll need to piece it together by themselves10:44
poolieso on the guide in particular10:45
pooliei think we want to get rid of the section called 'tutorial'10:45
mrevellpoolie: Yeah, and make the guide itself work as a tutorial10:46
mrevellpoolie: in that progresses the user through each topic10:47
pooliemaybe a good place to start would be to just change it's index.txt to incorporate an outline of what should be there10:48
fullermdI'm hoping in the next week or two work will calm down enough that I can sketch out an outline for my ideal UG.  Hardly had time to breathe lately   :(10:48
mrevellpoolie: Okay, I'll change the index.txt to create an outline of where I think we should go and then we can get a discussion going on the list.10:50
poolieat the moment 'configuration' is one of the first topics10:50
pooliedid you get enough feedback on the 5 minutes doc?10:50
pooliei glanced at it and it looked godo10:50
mrevellpoolie: Yeah, I got some great feedback, thanks. In particular, I've got some good feedback on how to pitch it. I was worried that I'd used the slightly wrong tone and that was confirmed10:51
mrevellSomeone said one part was a little too "cutesy", which I think was a fair comment.10:52
mrevellRight, well, thanks for your time guys. Over these two meetings I've had some very useful input. I'll write up the minutes of these two meetings and post them to the bazaar list today.10:52
=== boggle is now known as TeTeT
mrevellUnless anyone has anything further they'd like to add, I'll close the meeting and continue discussion on the list.10:53
pooliejust one more thing10:55
poolieone more open issue is this: there are several ways10:55
poolieyou can set up to use Bazaar10:55
poolieso at the moment we have centralized_workflow; we could also talk about team branches, or using pqm, or other thnigs10:56
pooliesimilarly, shared repositories vs standalone branches vs checkouts10:56
pooliethere's potential for confusion10:56
pooliei guess10:57
fullermdWell, for the latter, I think a good Fundamentals piece will cover that well (as I blathered about at excruciating length on the list)10:57
=== jml [n=jml@CPE-124-177-6-69.vic.bigpond.net.au] has joined #bzr
pooliewe should be clear about what the mainstream method is10:57
mrevellbut present the alternatives and why you might want to use them10:57
fullermdFor the former, I think that needs a chapter in the Manual, and emphasizing that it's a continuum rather than a set of points.10:57
pooliethe former?10:57
fullermdThe workflows10:58
fullermdAt one end is a single shared branch everybody works on, at the other is individual branches full-mesh merging, and everything else is in between.10:58
fullermdI have an idea of tackling that by starting with the single-branch case, and walking up through more and more distributed bits until it finally becomes full-mesh.10:59
poolieand then maybe the reference should describe the constituent parts10:59
fullermdBut you could also go the other way.  Or describe the ends, then walk inward from both.  I haven't decided which I like better11:00
fullermdI think what's needed is to cover the continuum, then pick a small handful (3, 4 maybe) points along it and describe how you'd use them specifically, and what use-cases they might well fill.11:00
mrevellI have to admit that this is an area where my lack of experience with bzr lets me down. I understand that there are different workflows but I'm sketchy on when is best to use which workflow.11:01
fullermdNot sure how to split that between Guide and Reference, though.  The whole would be too big and deep for Guide.11:02
fullermd(obviously, I'm a big "understand the concepts, then the 'real' instances are Obvious(tm)" guy.  That may be a blind spot.)11:06
poolietutorials as such do tend to start out with specific examples11:08
poolieanyhow, that gives us something good to go on with11:08
pooliethanks, mrevell11:08
pooliei'm done if you are11:09
mrevellfullermd: I worry that starting with the concepts could overwhelm people.11:09
mrevellbut obviously there's basic ground that needs to be covered to understand what follows11:09
mrevellyes, thanks poolie11:09
mrevellpoolie: I have some great action points and input from these two meetings11:09
fullermdYeah.  It's a problem   :(11:09
mrevellI'll write the meetings up for the list and come up with a first draft contents for the tutorial.11:10
mrevellI think I'll be relying heavily on community input for the more advanced topics.11:10
mrevellThanks everyone.11:10
=== dous [n=dous@] has joined #bzr
vilapoolie: ping11:24
vilapoolie: err, a bite late maybe :-/11:24
=== gabe [n=gabriel@] has joined #bzr
fullermdIs it a bug that heavy checkouts don't inherit the branch nick from their branch?11:34
=== fullermd thinks it is...
=== dous_ [n=dous@] has joined #bzr
=== Enquest [n=Enquest@d54C28B91.access.telenet.be] has joined #bzr
EnquestHow can I make sure that "bzr add" ignores a few directories11:49
poolieEnquest, add them to .bzrignore11:55
Enquestpoolie, could you point me to the docs for this11:56
EnquestWhere is .bzrignore located?11:56
Enqueston my home tree on the server tree?11:56
poolieEnquest, just in the root of your source tree11:56
Enquestthere is no file there .bzrignore?11:57
EnquestI have to create it11:57
pooliesearch for 'ignor'11:57
poolieyou can either create it, or use the 'bzr ignore' command11:57
poolieto create it and add patterns to it11:57
=== jml_ [n=jml@CPE-124-187-233-64.vic.bigpond.net.au] has joined #bzr
ubotuNew bug: #148030 in bzr "Heavy checkouts don't inherit nick" [Undecided,New]  https://launchpad.net/bugs/14803012:16
=== TeTeT [n=spindler@modemcable212.211-70-69.mc.videotron.ca] has joined #bzr
=== AfC [i=andrew@office.syd.operationaldynamics.com] has joined #bzr
=== Mez [n=mez@ubuntu/member/mez] has joined #bzr
pborspeaking of docs, am I the only one to think that in the quick start guide branching a remote branch should come first than creating your own repo?12:39
fullermdI don't think that way, no...12:39
fullermd(at least, necessarily)12:39
pbormaybe it is just me, but I think it is way more common to start using a vcs when joining a project that already uses it than starting a new project12:39
pborusually it goes: "I want to fix this with a patch, how do I get the code"12:40
pborwhen I start a new project and I pick a vcs chances are that I am already familiar with the vcs I pick12:41
fullermdWell, but the steps of using it are pretty much the same, and it's simpler to start describing in isolation (IMO)12:44
gabeEnquest: bzrignore is in your home dir12:45
pborfullermd: dunno, I know that each time I read cvs/svn/bzr doc when I started using them it got on my nerves... every time I thought "I do not want to create no f. repo, I don't even know what a repo is! Just tell me the command to get the code"12:47
fullermdWell.  That gets into why I *HATE* quick-start docs.12:48
=== sii [n=sii@tranquillity.sii.se] has joined #bzr
pborfullermd: if I read I quick start doc I just want to get the job done, I am not interested in the theory, so I prefer to order things by how often they are needed... a full reference is a different matter, there I agree that things should go in logical order12:50
=== cprov [n=cprov@canonical/launchpad/cprov] has joined #bzr
=== jml__ [n=jml@CPE-124-177-1-217.vic.bigpond.net.au] has joined #bzr
=== herzel104 [i=herzel@gateway/tor/x-621bbda4688b0d44] has joined #bzr
=== sabdfl [i=sabdfl@ubuntu/member/pdpc.silver.sabdfl] has joined #bzr
=== mrevell is now known as mrevell-lunch
sabdflhey revisionistas01:31
vilasabdfl: hi01:35
=== AfC [i=andrew@office.syd.operationaldynamics.com] has joined #bzr
=== AfC [i=andrew@office.syd.operationaldynamics.com] has joined #bzr
=== niemeyer [n=niemeyer@200-140-230-150.ctame705.dsl.brasiltelecom.net.br] has joined #bzr
=== allenap [n=allenap@87-194-166-60.bethere.co.uk] has joined #bzr
sabdflvila: what's news in bzr-land?02:39
sabdflis there a bundle-buddy page where I can see what's in the queue for review and landing?02:39
jelmersabdfl: see http://bundlebuggy.aaronbentley.com/02:40
vilaWell, I don't follow as closely as I wish, but lifeless is working on big improvements with pack formats02:40
vilahttp://bundlebuggy.aaronbentley.com/ will show you all pending patches02:40
=== mrevell-lunch is now known as mrevell
vilabulk of lifeless work does not appear there of course only bits he can merge now to bzr.dev02:41
vilaalso, spiv is working on some smart server improvements also not shown on BB02:42
vilabut both their works are supposed to land for 0.92, so soon02:42
sabdflthanks vila, that's a nice list02:43
vilasabdfl: you're welcome, but take it with a grain of salt, that's mostly my personal view, I may miss some parts02:44
vilasabdfl: and finally, mrevell is working on the doc, but you should know that ;)02:45
fullermdAnd I'm just sitting around stirring up trouble, as usual.02:46
vilaand giving good hints for docs ;)02:47
fullermdWell, yeah, in the sense that "someone else should write them the way I think they should be"   ;p02:47
sabdflevery good project has a good curmudgeon02:48
lifelessvila: the packs patch is pretty small now, the review I got today gets rid of the largest non-format delta02:49
lifelessanyhow, its *sleep* time, just dropping by for a last minute irc fix ;)02:50
vilalifeless: glad to know :) Will tell it to sabdfl :)02:50
vilalifeless: have a good night02:50
lifelessonly remaining must-do-before-merge of everything is the index layer; need to give keir's proposed format a fine toothed go-over and profile, or make the toy format do bisection02:51
=== lifeless waves
=== luks [n=lukas@unaffiliated/luks] has joined #bzr
=== cypherbios [n=cyr@ubuntu/member/cypherbios] has joined #bzr
=== nir [n=nir@moinmoin/fan/nir] has joined #bzr
=== orospakr [n=orospakr@bas4-ottawa23-1167864095.dsl.bell.ca] has joined #bzr
sabdfllight lifeless03:06
=== mw [n=mw@] has joined #bzr
=== BasicOSX [n=BasicOSX@warden.real-time.com] has joined #bzr
=== AfC [i=andrew@office.syd.operationaldynamics.com] has joined #bzr
=== BasicOSX [n=BasicOSX@] has joined #bzr
=== g0ph3r [n=g0ph3r@p57A0B930.dip0.t-ipconnect.de] has joined #bzr
=== bigdog [n=scmikes@72-197-8-8-arpa.cust.cinci.current.net] has joined #bzr
=== orutherfurd [n=orutherf@dsl092-164-022.wdc2.dsl.speakeasy.net] has joined #bzr
=== mw [n=mw@] has joined #bzr
=== orospakr [n=orospakr@] has joined #bzr
=== Lllama [n=Lllama@] has joined #bzr
LllamaAfternoon all. Anyone managed to get Trac working with bzr? I'm getting errors about it not being a Svn repository.04:54
orutherfurdhi, anyone have any tips for sharing a branch using ssh?  I think I'm running into bug 5056804:58
ubotuLaunchpad bug 50568 in bzr "'bzr push' does not preserve sgid bit on newly created directories" [Medium,Confirmed]  https://launchpad.net/bugs/5056804:58
=== mthaddon [n=mthaddon@canonical/launchpad/mthaddon] has joined #bzr
fullermdWell, my solution doesn't really help you   :)05:04
SigmaLllama: did you include "tracbzr.* = enabled" in your components ?05:04
LllamaSigma: Yep. I've got [components]  tracbzr.* = enabled at the bottom of the ini file.05:08
=== sabdfl [i=sabdfl@ubuntu/member/pdpc.silver.sabdfl] has left #bzr []
LllamaVarious bzr related messages show up on the source browser of the subversion repositories, so I'm guessing that the plugin is working.05:10
=== sabdfl [i=sabdfl@ubuntu/member/pdpc.silver.sabdfl] has joined #bzr
=== p4tux [n=p4tux@] has joined #bzr
abadger1999Lllama: I can pastebin a working config for you if you still need it.05:16
Lllamaabadger1999: Worth a look. Cheers.05:16
abadger1999Lllama: http://pastebin.ca/72312105:18
Lllamaabadger1999: cheers. You've got a couple of extra lines, so I'll try playing with them.05:37
abadger1999Cool.  Hope it helps!05:37
=== cprov is now known as cprov-lunch
Lllamaabadger1999, Sigma: thanks for the pointers. Upgrading from 0.9 to 0.10 was the key.05:48
=== phanatic [n=phanatic@ubuntu/member/phanatic] has joined #bzr
james_worutherfurd: you can correct that via chmod/chown.06:15
fullermdOnly temporarily.  Later pushes can still screw it up when they create new dirs.06:16
orutherfurdstupid question, I'm sure, but is there any way for paramiko to explicitly create directories w/same owner and permissions as parent directories?  or to change them after the fact?06:20
fullermdNo, the problem is the setgid.  The sftp server strips it.06:20
fullermdSo paramiko can _say_ to set it, but it won't get set.06:20
orutherfurdah, that's unfortunate ;-)06:21
fullermdbzr+ssh is probably a workaround.  And the better choice anyway, if you can run with it.06:21
=== kiko-zzz is now known as kiko
fullermdMy workaround is to not use a system with SysV filesystem semantics   ;)06:21
orutherfurdyeah, I saw that as a suggestion, but one of the big draws for using bzr was not having to install any software on the server06:22
orutherfurdeasier to fly below the radar06:22
NfNitLoopI don't think bzr+ssh requires installing bzr?06:22
NfNitLoopor am I getting them mixed up?06:23
orutherfurdoh, maybe I was misunderstanding -- I thought that was the 'smart server'06:23
fullermdYes, it does.  Otherwise you'll have a lot of trouble with the 'bzr' part of it.06:23
NfNitLoopOoh.  it's bzr tunneled over ssh.  Duh.06:24
=== NfNitLoop reads scrollback before commenting further.
=== BasicOSX [n=BasicOSX@216-250-187-201.static.iphouse.net] has joined #bzr
=== LeoNerd [n=leo@cel.leonerd.org.uk] has joined #bzr
=== cprov-lunch is now known as cprov
=== NamNguyen [n=namnt@cm38.delta196.maxonline.com.sg] has joined #bzr
=== Lllama [n=Lllama@] has left #bzr []
=== mrevell is now known as mrevell-dinner
=== Alien_Freak [n=sfaci2@castor.tavros.net] has joined #bzr
=== mikl [n=mikl@pdpc/supporter/active/mikl] has joined #bzr
=== marianom [n=marianom@ubuntu/member/marianom] has joined #bzr
=== Gwaihir [n=Gwaihir@ubuntu/member/gwaihir] has joined #bzr
=== joejaxx [i=joejaxx@fluxbuntu/founder/joejaxx] has joined #bzr
=== jamesh [n=james@canonical/launchpad/jamesh] has joined #bzr
jelmerphanatic: ping07:38
=== jkakar [n=jkakar@204-174-36-45.dhcp802.dsl.ucc-net.ca] has joined #bzr
phanaticjelmer: pong, i saw you've subscribed a bundlebuggy :)07:38
=== Vernius_ [n=tomger@p508AC107.dip.t-dialin.net] has joined #bzr
phanaticjelmer: got your mail as well. it's awesome, thanks for your work!07:41
fullermdOog.  I hate it when a annoying-but-harmless bug turns into an annoying-but-harmful one   :(07:46
jelmerabentley: ping?07:47
jelmerphanatic: we don't seem to be able to vote yet :-/07:48
=== Admiral_Chicago [n=FreddyM@ubuntu/member/admiral-chicago] has joined #bzr
=== nir [n=nir@moinmoin/fan/nir] has joined #bzr
=== Zindar_ [n=erik@stockholm.ardendo.se] has joined #bzr
phanaticjelmer: yeah, just noticed...07:50
=== asak [n=alexis@201-1-201-182.dsl.telesp.net.br] has joined #bzr
fullermdCan somebody more official take a look at bug 114615, particularly in light of the comment I just posted on it?07:54
ubotuLaunchpad bug 114615 in bzr "AssertionError trying to commit with 0.16.0" [High,Confirmed]  https://launchpad.net/bugs/11461507:54
fullermdI feel the desire to bump Importance to Critical for that, but that's above my paygrade.07:55
=== dpm [n=dpm@p54A116C6.dip0.t-ipconnect.de] has joined #bzr
=== jrydberg_ [n=Johan@c80-216-246-123.bredband.comhem.se] has joined #bzr
jelmerfullermd: please update that bug to reflect that it affects bzr.dev and 0.9108:02
fullermdHm.  I mentioned it in the comment.  Is there an Affects field I don't see?08:03
jelmerThere should be a "Edit Description/Summary" link or something on the left08:06
fullermdOoh, the title?  Gotcha.08:07
fullermdDamn thing bit me on a real project earlier today.  That was fun to try and reproduce...08:10
=== phanatic_ [n=phanatic@dsl54028251.pool.t-online.hu] has joined #bzr
=== kiko is now known as kiko-phone
=== bratsche [n=cody@adsl-68-94-36-166.dsl.rcsntx.swbell.net] has joined #bzr
=== phanatic_ is now known as phanatic
james_wif I do mv a b in one branch and edit a in another I get a conflict upon merging the move to the edit. That seems wrong to me.08:51
james_walso there is no way to resolve it so that the move gets recorded.08:51
=== zyga [n=zyga@ubuntu/member/zyga] has joined #bzr
fullermdI've not seen that.  A quick test doesn't show it here either.08:53
james_wah, it works this time, I don't know what I was doing there.08:57
fullermdI blame violent video games, personally.08:58
=== kiko-phone is now known as kiko
=== luks [n=lukas@unaffiliated/luks] has joined #bzr
=== cypherbios [n=cyr@ubuntu/member/cypherbios] has joined #bzr
=== BasicOSX [n=BasicOSX@216-250-187-201.static.iphouse.net] has joined #bzr
=== cprov is now known as cprov-afk
=== fog [n=fog@debian/developer/fog] has joined #bzr
=== Mez_ [n=Mez@ubuntu/member/mez] has joined #bzr
=== Mez_ is now known as Mez
=== Mez_ [n=mez@ubuntu/member/mez] has joined #bzr
=== mvo [n=egon@p54A66FA4.dip.t-dialin.net] has joined #bzr
=== AnMaster_ [n=AnMaster@unaffiliated/anmaster] has joined #bzr
=== AnMaster_ is now known as AnMaster
=== Zindar [n=erik@h188n1fls12o803.telia.com] has joined #bzr
james_wfullermd: nice bug.10:14
fullermdHrmph.  *I* didn't think it was so nice   ;p10:19
fullermd2 revs down the line...   "WTF?  Why is this totally vital file that's existed in the project for months 'unknown'??"10:20
fullermdIt gave me just enough time to get over "Hmph.  That wacky assertion failure that works the second time isn't fixed yet?"10:22
fullermdThe test case might be trimmable a bit farther.  I think you need the re-rm'd directory to trigger the assert (and so you need a change in that file deleted), and I presume it's the "other file from the same dir mv'd into another dir" bit that triggers the "rm'd/unknown" bit.10:26
fullermdSo maybe some of the other files aren't necessary.  But I don't have time today to try and work up truly minimal cases   :|10:26
james_wI don't think the second directory is needed.10:28
james_wI have just sent an analysis to the report though, so the test case can be trimmed using that.10:29
=== Gwaihir [n=Gwaihir@ubuntu/member/gwaihir] has joined #bzr
fullermdProbably not.  It's part of an earlier attempt I made at trying to figure out what of my real project brought it about.10:30
james_wit was good enough to pinpoint the problem though, so thanks.10:31
james_windeed the second dir is not needed.10:34
fullermdMaybe the bug is really "What the hell are you doing to your poor branches?!"10:35
james_wchanging, renaming and deleting your files all at once? You expect me to merge that?10:36
fullermd"Rise up against your oppressors!  Power to the branches!"10:37
=== ppc [n=ppc@abfv59.neoplus.adsl.tpnet.pl] has joined #bzr
=== ppc [n=ppc@abfv59.neoplus.adsl.tpnet.pl] has left #bzr []
lifelessjames_w: thanks10:48
=== phanatic_ [n=phanatic@dsl5402836B.pool.t-online.hu] has joined #bzr
james_wlifeless: no problem.11:02
james_wlifeless: is there enough there for you to see the problem?11:02
james_wand is the renamed entry the conflict generates the right thing?11:02
=== thumper-office [n=tim@125-236-193-95.adsl.xtra.co.nz] has joined #bzr
=== BasicOSX [n=BasicOSX@216-250-187-201.static.iphouse.net] has joined #bzr
=== _thumper_ [n=tim@canonical/launchpad/thumper] has joined #bzr
=== _thumper_ is now known as thumper
ubotuNew bug: #148287 in bzr "Should be able to refer to historical files by file-id" [Wishlist,New]  https://launchpad.net/bugs/14828711:25
phanatic_jelmer: ping11:34
=== phanatic_ is now known as phanatic
jelmerphanatic: pong11:36
jelmerphanatic: just sent an email about bundlebuggy11:36
jelmerphanatic: you should be able to vote now11:38
phanaticjelmer: the main problem is that i can't log in11:38
jelmerphanatic: can you try again?11:39
phanaticjelmer: doesn't work :(11:40
jelmerphanatic: please try again11:41
jelmertypo in your username :-/11:42
phanaticjelmer: works now, thanks :)11:44
=== herzel104 [i=herzel@gateway/tor/x-012e39f07fb7f8c6] has joined #bzr
=== Rotund [n=rotund@72-160-252-150.dyn.centurytel.net] has joined #bzr
Rotundhi.  My company is looking into a new scm/vcs, and they have some questions about bazaar11:51
Rotundsomeone got time to answer some questions?11:51
RotundDoes bzr have support for locking individual files?11:57
lukslocking as in "CVS-like locking"?11:58
Rotundlike "noone can change this file"11:59
=== jml__ [n=jml@ppp121-44-213-76.lns1.hba1.internode.on.net] has joined #bzr
luksno, it doesn't (by design)11:59
RotundThat's actually a problem for us11:59
luksif you need locking (which I think you don't), then you probably want a strictly centralized vcs12:00
RotundI understand for things actively developed.  We do a lot of testing and have actual releases.12:00
luksin bzr you create a couple of branches and then merge them, instead12:00
=== jml__ is now known as jml
RotundOne thing the people I work with are concerned about is limiting changes to files after they have been reviewed.12:01

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