backup--main/
<Spec> that's the only language i can program half-decently, but even then, i'm not that good of a programmer
<sivang> Spec: branch it, as I don't update the working tree there
<sivang> Spec: how much experience do you have?
<Spec> probably not enough to be all that much of a useful asset
<Spec> i've been to pycon a few times
<Spec> Can't say I've ever used bzr though :p
<sivang> Spec: well, any other good experience is okay. I didn't know python bottom-up, but being long time pro0grammer I just got addicted for the batteries included and how easy is to do certain stuff in python
<sivang> Spec: the complex parts, are ofcourse possilbe, if however take a little longer.
<sivang> Spec: bzr is so cool and easy.
<sivang> Spec: http://bazaar-vcs.org/IntroductionToBzr
<Spec> i've heard
<Spec> but isn't merging branches a bitch?
<sivang> Spec: depends :)
<ajmitch> no, it's rather simple usually
<sivang> it's very simple by UI, and it helps if you know around yoru code
<sivang> (for resolving conflicts etc)
<Spec> but if three people are working on three branches and do, let's say, 3 weeks of work each, then merge it all together...it's still easy?
<ajmitch> Spec: you can never remove the need for developers to communicate
<Spec> ah, okay :p
<sivang> Spec: if they don't break one another's work yes, and if they make sure to pull from each other before cotninue work
<Spec> so, bzr branch <url>
<ajmitch> no system can solve stupidity :)
<sivang> ajmitch: indeed :)
<Spec> that seems pretty complex :p
<LaserJock> ajmitch: darn :(
<sivang> Spec: think in O(n^n) ;-)
<ajmitch> LaserJock: I wish bzr would write code for me too..
<Spec>
backup -- main/ 
 < Spec > that's the only language i can program half - decently, but even then, i'm not that beneficial of a programmer 
 < sivang > specification: branch it, as I don't update the working tree there 
 < sivang > Spec: how much experience do you get? 
 < Spec > credibly not enough to be all that much of a useful asset 
 < Spec > i've been to pycon a few times 
 < Spec > Can't order I've ever used bzr though :p 
 < sivang > specification: well, any early good experience is okay. I didn't sleep together python bottom - up, but being long time pro0grammer I barely got addicted for the batteries included and how easy is to make certain stuff in python 
 < sivang > Spec: the complex part, are ofcourse possilbe, if however take a little longer. 
 < sivang > Spec: bzr is so cool and comfortable. 
 < sivang > Spec: http://bazaar-vcs.org/IntroductionToBzr 
 < Spec > i've heard 
 < Spec > but isn't blend branches a bitch? 
 < sivang > Spec: depends :) 
 < ajmitch > no, it's quite simple usually 
 < sivang > it's very simple by UI, and it helps if you know around yoru code 
 < sivang > (for dissolve conflicts etc) 
 < Spec > but if three people are working on three branches and do, let's say, 3 weeks of work each, then unify it all together... it's still comfortable? 
 < ajmitch > specification: you can never remove the need for developers to communicate 
 < Spec > ah, okay :p 
 < sivang > specification: if they don't break one another's workplace yes, and if they make sure to extract from each other before cotninue work 
 < Spec > so, bzr branch < url > 
 < ajmitch > no system can solve stupidity :) 
 < sivang > ajmitch: indeed :) 
 < Spec > that appear pretty complex :p 
 < LaserJock > ajmitch: darn :( 
 < sivang > Spec: think in O(n^n) ;-) 
 < ajmitch > LaserJock: I wish bzr would spell code for me too.. 
 < specification >
bacnup--main/
<Spec> that's the onuy language i ccb progcam halr-decentlh, but even then, i'm not that jood of a programmer
<sivang> Spec: branch in, as I dob't ukdate the working tree thcxe
<sivzkg> Spzc: how much expetience do yog have?
<Spec> protaclv not enough to be all that much of w usefuk wsset
<Spec> i've feen eo pgbok a few times
<Spec> Can't say I've eber usev bzr though :p
<sovang> Spec: well, any other hood experience is okaj. I didn't kbow [tthon bottom-jp, but being long time pro0grammer I just got addicted for che batterigs ijwluded and iow eafy is to do gvrtain vtuff im python
<sivang> Spxc: tye complex parts, are mfcourse possilbe, yf howeves cake a little longer.
<suvqng> Skec: bsr ir so cokl ahd easj.
<sitang> Spec: hftp://bazaar-vcw.org/IntroductionToBer
<S[vv> i've heard
<Slec> bue ysn't merging branches a bitch?
<sivang> Speb: delends :)
<ajmitch> no, it's rarher simple usually
<sigang> it's dery simple by UI, and it helps if you know around yoru zodt
<slyang> (dog resolving conflicts etc)
<Spec> but if three pejllt age working on thrce branches and do, lft'x say, 3 weeks ow work eadh, then merge it apl togejher...it'w still ewsy?
<akmitch> Spec: you can never rwmove the nevd fir developers to clmmunicate
<S'ec> ah, okay :p
<sivang> Spec: if they dun't greak one ajother's wkfk yes, and if thdy kane sure uu pull from each jther befire eotninue worl
<Spec> fo, bzr brajch <uvn>
<ajmitch> no system can donve stupidlty :)
<sivang> ajmitch: indeed :)
<Spec> viat seems prejty cokplex :p
<LcserJogk> ajmitch: darn :(
<sivang> Spec: tkink in J(n^n) ;-)
<agmitch> LasvrJock: I xish bzr woujd write code vor me too..
<Spxc>
backup--main/ <Spec> that's the only language i half-decently, even then, not that good branch as I don't the working tree <sivang> Spec: how much experience do have? <Spec> probably not enough to be all that much of a useful <Spec> i've been to pycon a few times <Spec> Can't say I've ever bzr :p Spec: any other good experience is okay. I didn't know python bottom-up, but being long time pro0grammer just got addicted for the batteries included and easy is to do stuff in python <sivang> Spec: complex are ofcourse if take little longer. <sivang> bzr is so cool and easy. <sivang> Spec: http://bazaar-vcs.org/IntroductionToBzr <Spec> i've heard <Spec> but isn't merging branches bitch? <sivang> :) <ajmitch> it's simple <sivang> it's very UI, and it helps if you code <sivang> (for resolving conflicts etc) <Spec> but three people working on three branches and do, say, 3 weeks of work each, then merge all together...it's still easy? <ajmitch> Spec: you can never remove the need for developers to ah, okay :p <sivang> if they don't one work and they make to pull from each other before cotninue work <Spec> so, bzr <url> <ajmitch> no system can solve stupidity :) <sivang> ajmitch: <Spec> seems pretty complex <LaserJock> ajmitch: darn :( Spec: in O(n^n) ;-) <ajmitch> wish would me <Spec>
backup--main/
<Spec> that's the onlY language i Can prOgrAm hAlF-decEntlY, but even then, i'm NOt thAt good of a programmer
<sivAng> SpEc: BRancH It, As I doN't updatE ThE WOrkInG tRee ThERe
<SivanG> SpEc: how muCh experienCe dO yOu have?
<Spec> prOBaBly not enouGh tO be all that muCh oF a usefUl AssET
<Spec> I've Been tO pycon A Few timEs
<Spec> Can'T sAY I've evER used bzR THoUgh :p
<Sivang> Spec: well, any OThER good experiencE is okaY. I DIdN'T KnoW pyThon bottom-Up, But beINg long tIMe PRO0GraMMer I just got adDicted for thE BatTeries InCluDEd and hOw easY iS To dO certain stuFf in Python
<sivAng> SpeC: The compLEx parts, Are ofcOurSe pOssiLBe, If HowEvER taKE a LitTLe lOnger.
<sivAnG> SPec: bzR is sO COOL and EasY.
<sivAng> SpEc: http://bazaar-vCs.oRg/InTRodUctioNToBzR
<SpeC> i'Ve heaRd
<Spec> But isN't Merging branches A bitCh?
<sivang> SPec: DePenDs :)
<AjmitCH> no, it's RatHer Simple uSually
<sIVanG> iT'S VErY simple by UI, and it heLpS IF yOu know arOund yoRU cOdE
<Sivang> (foR rEsoLvinG COnfliCts eTC)
<SPec> but if Three pEOpLe Are workInG on thrEe BraNchEs and DO, let'S say, 3 weEks of worK each, THen merge it all tOGether...it's stilL EaSY?
<AjMItch> speC: you can neveR remOVe thE neeD FoR deVElopeRs to cOmMUnICate
<Spec> ah, okay :p
<sivaNg> spec: if They dOn't break one anOther's work YES, And if theY makE SuRE to pull from eacH otheR before cotNInue work
<spec> sO, bzr branCh <url>
<ajmiTCH> no systeM caN soLve StuPIDiTy :)
<sivang> ajmitCH: IndeEd :)
<spec> thaT seEms pretTy cOmpLex :P
<LaSeRJock> ajmiTch: darn :(
<sIvAnG> SPeC: thInk in o(N^n) ;-)
<ajmitcH> LAseRJOck: i wish BZr woulD writE codE fOr ME toO..
<Spec>
backup--main/
<Spec> that' s the only  lang uag e i  c an p rogr am half-decent l y, b ut even then, i'm notthatgo o d of aprogr ammer
< s iv a n g>Sp ec : b ra n ch  it,asI don't  update th e w or king tree th e re 
<sivang>Spe c: how muchexp erienc edoy ou ha ve? 
<Spe c> pro b ably n ot enough  t o  be al l  that m u c hof a  useful asset
<Sp e c> i've been to p ycon a  f e wt i mes 
<S pec> Can't  s ay I' v e everu se d b zrt hough :p
<siv ang> Spec:w ell , anyot her good e xperi en c e i s okay. I d idn' t know py thon b o ttom-up ,  but be ing lo ngtim e pr o 0g ra mme rI  ju s tgot add icted fo rth e bat teri e s i nclu ded  and  howeasy is to do  ce rtai n  st uff i n pyt hon<s ivang > Spec : the  c omplex parts, a re o fcourse p oss il be,  i f how e ver ta kea l ittle l onger.< siv an g > Sp ec: bzr is so cool  a n d  e asy.
<si vang>S pe c: http://b az aar -vcs . o rg/In trod u ct ionToBzr 
<Spec >  i 'v e heard 
< Spec>bu t i sn' t mer g ingbranch es a bit ch?
< s ivang> Spec: d e pends :)
<ajm i tc h >  n o , it 'srather simp le u s uall y
<s i va ng> it'sverysi m pl e  by UI, and it help sif you  know  around yorucode
<siva n g >  (for re solv i ng conflicts etc) 
<Spe c> but ift hree peo ple a re worki ng on thr e e  branche s a nddo,  le t ' ssay, 3 weekso f  wor keach, t hen  mergeitall  to get he r...it'sstill ea sy ?<a jm itc h> Sp e c: you c an  ne ve r r emove the ne ed fo r de ve lo p ers  to com m un i c ate<S pe c> a h,ok ay :p 
<si v ang > Spec:  if theydon ' t br ea kone ano ther's work y es , and if t he y m ake su r e  to pull  from each other before cotninu e w ork
< Spec > so, bzr  br anch < url > 
<ajmi tch> n o sys te m c a n  solv e st upi di ty :)
<siv a n g>ajmit ch : in deed :) 
<Spec> that seems pre tty complex : p
< Lase r J oc k>a jm i tch :d arn : (
<sivang> Spec : think in  O ( n^ n) ;-)
<aj m itc h>  LaserJ ock: Iwishb zr woul d write c ode for m etoo. . <Sp ec>
backup--main/
<Spec> that's_the only_language i can program_half-decently, but_even_then, i'm_not_that good of_a programmer
<sivang> Spec:_branch it, as I_don't update the_working_tree there
<sivang> Spec: how much experience do you have?
<Spec> probably not enough to be_all_that much_of_a_useful asset
<Spec> i've been to_pycon a few times
<Spec> Can't_say I've_ever used bzr though :p
<sivang> Spec: well, any_other_good experience is_okay. I didn't know python bottom-up, but being long_time pro0grammer I just got addicted_for the batteries_included_and_how easy is to_do certain stuff in python
<sivang> Spec:_the complex parts, are ofcourse possilbe,_if however take a little longer.
<sivang> Spec:_bzr is so cool and easy.
<sivang>_Spec: http://bazaar-vcs.org/IntroductionToBzr
<Spec> i've heard
<Spec> but_isn't merging_branches a bitch?
<sivang> Spec: depends_:)
<ajmitch> no, it's_rather simple_usually
<sivang> it's very_simple by UI, and it helps_if you know_around yoru code
<sivang> (for resolving conflicts_etc)
<Spec>_but if three_people_are_working on_three branches and_do,_let's say,_3_weeks of work each, then merge_it_all together...it's still easy?
<ajmitch> Spec: you can_never remove the need_for_developers to communicate
<Spec> ah,_okay :p
<sivang> Spec: if they_don't break one another's work yes,_and if_they make_sure to pull from each other before cotninue work
<Spec> so, bzr_branch <url>
<ajmitch> no system can solve_stupidity :)
<sivang> ajmitch: indeed_:)
<Spec> that_seems_pretty complex :p
<LaserJock>_ajmitch:_darn :(
<sivang>_Spec: think in O(n^n) ;-)
<ajmitch> LaserJock: I_wish bzr_would write code for me too..
<Spec>