 make a proposal as summer of code project. Store the tree unpatched and offer looms api to view the patches and diff/switch up & down. But looms are never committed only flat patches are. (v2) same but generate bundles out of patches such that you can create patched branch to rebase it -> and export a new patch series.
<xnox> slangasek: the project was not picked up =)
<slangasek> heh
<xnox> mercurial-queues is the best for debian/patches. They are quilt compatible but each patch has hg metadata in them. And there is nifty commands to rebase/add/remove/merge patches in that quilt series.
<xnox> unfortunately nobody stepped up to write a good hg-buildpackage.
<slangasek> xnox: why do you propose using the patches as the stored representation, rather than using the looms as the stored representation and serializing debian/patches from there?
<xnox> slangasek: because of 3.0 (quilt) package format, which inherintely from quilt doesn't have $ quilt merge-series command nor $ quilt rebase-series command.
<xnox> slangasek: if we get 3.0 ($vcs) format, there is no need for patches. But that opens a different kind of warms (no way to easily get the diff upstream vs packaged-changes)
<slangasek> why would I ever need/want to do such a merge-series or rebase-series?  Shouldn't loom primitives be sufficient?
<xnox> slangasek: if everyone switches and there are no exceptions, we can policy enforce looms and use that and live will be wonderful.
<xnox> s/live/life/
<slangasek> we don't need to switch "everyone" in order to make a policy change on UDD
<xnox> slangasek: i somehow believe that unless everyone switches, there will always be packages that fail to import or do something funny which will break UDD.
<slangasek> who is "everyone"?
<slangasek> I don't understand who you're saying would be switching, here
<slangasek> UDD itself imports from the archive, the archive wouldn't know anything about looms
<xnox
make a proposal as summer of code project. Store the tree unpatched and offer loom api to see the patches and diff / switch up & down. But loom are never committed entirely flat patches are. (v2) like but beget bundles out of bandage such that you can create patched arm to rebase it - > and export a new patch serial. 
 < xnox > slangasek: the project was not picked up =) 
 < slangasek > heh 
 < xnox > mercurial - queues is the best for debian / patches. They are quilt compatible but each patch accept hg metadata in them. And there is nifty command to rebase / add / remove / merge patches in that quilt series. 
 < xnox > unfortunately nobody stepped up to publish a good hg - buildpackage. 
 < slangasek > xnox: why do you propose using the patches as the store representation, rather than using the looms as the stored representation and serializing debian / patches from there? 
 < xnox > slangasek: because of 3.0 (quilt) package format, which inherintely from quilt doesn't have $ quilt merge - series command nor $ quilt rebase - series command. 
 < xnox > slangasek: if we get 3.0 ($ vcs) format, there is no need for bandage. But that opens a different kind of warms (no room to well induce the diff upstream vs packaged - changes) 
 < slangasek > why would I always need / want to serve such a merge - series or rebase - series?   Shouldn't brood primitives be sufficient? 
 < xnox > slangasek: if everyone switches and there are no exceptions, we can policy enforce looms and use that and live will be wonderful. 
 < xnox > s / live / life/ 
 < slangasek > we don't need to switch " everyone " in order to hold a policy change on UDD 
 < xnox > slangasek: i somehow think that unless everyone interchange, there will always be packages that fail to import or do something fishy which will break UDD. 
 < slangasek > who is " everyone "? 
 < slangasek > I don't understand who you're saying would be switch, here 
 < slangasek > UDD itself imports from the archive, the archive wouldn't know anything about looms 
 < xnox
 mane a proposal as summer uf code project. Store vhe tres unpatcfed and offer looms api to vmew rhe pqtches and diff/switch jp & down. Hut loomw art never committed only flat patdmes axe. (v2) same but gekerate bundnes out of patwhds such that you can create patched bwanch tp gebase it -> and exppwt a new patch series.
<xnox> slangasek: ths projebt was not picked up =)
<slangasek> heh
<xnox> merckriap-queues is the besh for debiab/patsyes. They are quilt comkacible but ezch patch has hg metadata in thdm. Anb there is bidty wommands to rebafe/add/remove/mcgge patwhes in that quilt sevies.
<xiox> ynfortunately nobody vtepped up to writg a good hc-bbildpackage.
<slangasek> znix: whi do fou oeopuse uxihg the pavches as ths stored representation, rather trqn using the mooms ws the stored representation and serializpng sebian/patches from therw?
<xnox> slangasek: becaude of 3.0 (quylt) package format, which inherintely from quilt dmesn't favt $ quilg mfrge-series command nor $ quilt rebase-series coijamd.
<qnox> slangasek: if we get 3.0 ($vcx) votiat, there is vo neeb fkr patches. But thah opens a didferent kynd pf warms (no way to easily gwt the diff lpsteeam vs packaged-chcnges)
<slangaszk> why woulc I ever need/want to do sucg a merge-segies or rscase-series?  Shouudn'n lomm primiukves be sufficiene?
<xnox> slaigasel: if evdryome swieches and hhere are no exceptions, ae cau polhcy enforcf looms and use that and live wmkl be wondergun.
<xnmx> s/live/jife/
<skangasek> we djn't need to swntch "evexyone" kn order tk make e policy chagge on UDD
<xnof> slangasek: i somehow belueve that uvuess everyone xwitches, nhtre will aoways be packages bhat wzil to import ox eo something fumny whycj xill fseak UDD.
<slancasey> wfp is "dveryont"?
<flcneasel> I don't understand fho gou're saying would bc switchibg, here
<sjangasek> UDD otself imports frol the arrhive, yhe archive wouldn't know anything about lolms
<wnox
make a proposal as summer of code the unpatched and looms api to up down. But looms never committed only patches are. (v2) same but generate out of patches such that you can create patched branch to rebase it and export a new patch series. <xnox> slangasek: the project was not picked =) heh mercurial-queues the best for debian/patches. They are quilt compatible but each patch has hg metadata in them. there is nifty commands to rebase/add/remove/merge patches in quilt series. <xnox> unfortunately stepped up to write a hg-buildpackage. xnox: why you using patches as the representation, rather than using the looms as the stored representation and serializing debian/patches from there? <xnox> slangasek: of 3.0 format, which from doesn't $ quilt merge-series $ quilt rebase-series command. <xnox> slangasek: 3.0 ($vcs) format, there is no need for But that a different kind of warms (no to easily get the diff upstream vs packaged-changes) why would I ever need/want to do such a merge-series or rebase-series? Shouldn't loom primitives <xnox> slangasek: if everyone and there are exceptions, can enforce and use and live will be wonderful. <xnox> s/live/life/ <slangasek> we don't need switch "everyone" in order to make a policy change on slangasek: somehow believe that everyone switches, there will be that fail to import something which <slangasek> is <slangasek> I don't understand you're saying would be switching, <slangasek> UDD itself imports wouldn't know anything about looms <xnox
 make a proposal as summer of coDe project. STore tHe tRee UnPatcHed aNd offer looms apI To viEw the patches and diff/swiTch up & DoWN. But LOoMs are Never coMMiTTEd oNlY fLat PaTChEs are. (V2) saMe but geNerate bundLes OuT of patches suCH tHat you can cReaTe patched braNch To rebaSe It -> aND expoRt a New paTch serIEs.
<xnox> Slangasek: ThE ProjecT Was not pICKeD up =)
<sLangasek> heh
<xnox> meRCuRIal-queues is the Best foR dEBiAN/PatCheS. They are quIlT compATible buT EaCH PAtcH Has hg metadata In them. And thERe iS nifty CoMmaNDs to reBase/aDd/REmoVe/merge patcHes iN that quilT serieS.
<Xnox> unfORtunateLy noboDy sTepPed uP To WrIte A gOOd hG-BuIldPAckAge.
<slangAsEk> Xnox: wHy do YOU PRopoSe uSing The paTches as the stoRed ReprESenTatioN, rathEr thAn Using The looMs as tHe Stored representAtioN and seriaLizInG deBiAn/patCHes froM thEre?
<Xnox> slaNgasek: bECauSe OF 3.0 (QUiLt) package format, whiCh INHeRintely fRom quiLT dOeSN't have $ quIlT meRge-sERIes coMmanD NoR $ quilt reBase-seRIeS cOmmand.
<xNoX> slangAsEk: iF we Get 3.0 ($vcS) FormAt, therE is no neeD for pATches. But that opENs a different kINd OF WaRMs (no Way To easily get The dIFf upStreAM vS paCKaged-ChangEs)
<SLaNGasek> why would I ever nEeD/want tO do suCh a merge-serieS or rebase-sERIEs?  ShouldN't loOM pRImitives be suffIcienT?
<xnox> slangASek: if eveRyone Switches And there aRE No exceptIonS, we Can PolICY eNforce looms anD USe thAt And live WilL be wondErfUl.
<xNox> S/liVe/Life/
<slangAsek> we doN't NeEd To SwiTch "evERyone" in oRdEr tO mAke A poliCY changE on UDd
<xnoX> sLaNGasEk: i someHOw BELievE tHaT unlEss EvEryonE swiTCheS, there wIll always Be pACkagEs ThAt fail tO import or do soMeThing funny WhIch Will brEAK UDD.
<slanGasek> who is "everyone"?
<slangASek> I don'T unDerstAnd wHo you're saYinG would Be sWItchinG, here
<sLangaSeK> UDd ITself IMPoRts FrOm the archiVE, The ArchiVe WoulDn't know Anything about looms
<XNox
 make a proposal as summer  of code p rojec t.Sto re  the  tre e unpatched an d  off er looms api to view t he pa tc h es a n ddiff/ switchu p& dow n.  B utlo o ms  arenev er comm itted only  fl at  patches are .  ( v2) same b utgenerate bun dle s outof  pa t chessuc h tha t youc an cre ate patch ed branch to reba s e  i t ->  and export a new pa t ch series.
<xn ox> sl an g as e k : t heproject wa snot p i cked up =) < s lan g asek> heh
<xn ox> mercuri a l-q ueuesis  th e  bestfor d eb i an/ patches. Th ey a re quiltcompat i ble but each pa tch ha s h g m etad a ta  i n t he m . A n dthe r e i s niftyco mm andsto r e b a s e/ad d/r emov e/mer ge patches in  th at q u ilt  seri es.
< xnox >unfor tunate ly no bo dy stepped up t o wr ite a goo d h g- bui ld packa g e.
<sl ang ase k> xnox : why d o  yo up r o po se using the patch es a sthe stor ed rep r es en t ation, r at her  tha n using  the lo oms as t he sto r ed  r epresen ta tion a nd  se ria lizin g  deb ian/pa tches fr om th e re?
<xnox> sla n gasek: becaus e  o f 3. 0  (qu ilt ) package f orma t , wh ichi nh eri n telyfromqu i lt doesn't have $ quil tmerge- serie s command nor  $ quilt r e b a se-serie s co m ma n d.
<xnox> slan gasek : if we ge t  3.0 ($v cs) f ormat, t here is n o need for  pa tch es.  Bu t th at opens a di f f eren tkind of  wa rms (no  wa y t o e asi ly  get thediff ups tr ea mvs  pa ckage d -changes )<sl an gas ek> w h y woul d I e verne ed / wan t to do su c h  a m er ge -ser ies  o r reb ase- s eri es?  Sh ouldn't l oom prim it iv es be s ufficient?
<x no x> slangas ek : i f ever y o ne switc hes and there are no ex c eptions , w e can  pol icy enfor celoomsand use th at and  live  w ill b e won d e rf ul. 
< xnox> s/li v e /li fe/
< sl anga sek> we  don't need to swi t ch"everyone" in  or dert o  m ake ap oli cy cha n g e on UDD
<xnox>  slangasek :i  s omehow bel i eve  t hat unl ess eve ryone switche s, therewill alwa ys  bep a cka ges that f ail to i mport ord o som e th ing f unn y whic hwil l bre ak UDD . 
<s langa sek> w ho  is "e veryo ne "?
<slan gasek> I don't understa nd who  you' resaying wo uld beswitching , he re
<slanga sek > U DD it sel f  impo rtsf ro m t h e arc hive ,  the arch i ve  wo u l dn 't know any t h i ngabout  lo o ms
<xn ox
 make_a proposal_as summer of code_project. Store_the_tree unpatched_and_offer looms api_to view the_patches and diff/switch up_& down. But_looms_are never committed only flat patches are. (v2) same but generate bundles out of_patches_such that_you_can_create patched branch to rebase_it -> and export a_new patch_series.
<xnox> slangasek: the project was not picked up_=)
<slangasek>_heh
<xnox> mercurial-queues is_the best for debian/patches. They are quilt compatible but_each patch has hg metadata in_them. And there_is_nifty_commands to rebase/add/remove/merge patches_in that quilt series.
<xnox> unfortunately nobody_stepped up to write a good_hg-buildpackage.
<slangasek> xnox: why do you propose using_the patches as the stored representation,_rather than using the looms_as the_stored representation and serializing debian/patches_from there?
<xnox> slangasek:_because of_3.0 (quilt) package_format, which inherintely from quilt doesn't_have $ quilt_merge-series command nor $ quilt rebase-series_command.
<xnox>_slangasek: if we_get_3.0_($vcs) format,_there is no_need_for patches._But_that opens a different kind of_warms_(no way to easily get the diff_upstream vs packaged-changes)
<slangasek> why_would_I ever need/want to_do such a merge-series or_rebase-series?  Shouldn't loom primitives be_sufficient?
<xnox> slangasek:_if everyone_switches and there are no exceptions, we can policy enforce looms_and use that and live will_be wonderful.
<xnox> s/live/life/
<slangasek> we_don't need_to_switch "everyone" in_order_to make_a policy change on UDD
<xnox> slangasek: i_somehow believe_that unless everyone switches, there will_always be packages that_fail_to import or do something funny_which will break UDD.
<slangasek> who is_"everyone"?
<slangasek> I don't understand who_you're_saying_would be switching, here
<slangasek> UDD_itself imports from the archive, the_archive wouldn't know_anything about looms
<xnox