/srv/irclogs.ubuntu.com/2014/03/03/#bzr.txt

=== BasicMBP is now known as BasicOSX
achiangquestion on how bzr handles history and binary objects - let's say i have a repo where someone committed 100 jpgs in the first commit and it takes an excessively long time to clone. now, many commits later, if we bzr rm those jpgs, will the main branch still take ages to pull from LP?11:54
beunoachiang, it will for the first time, yes12:03
beunoachiang, they are there forever and ever*12:03
beuno*unless you do something icky like rebase and break compatibility with existing branches12:04
achiangbeuno: are there any tricks i could play?12:04
achianghm12:04
achiangrebase12:04
achiangyeah12:04
achiangcan you bzr pull without grabbing all the history, perhaps?12:05
achiangmaybe something related to "shallow" ?12:06
beunoachiang, I don't believe partial history was ever implemented12:06
beunomaybe a lightweight checkout12:06
beunomaybe12:06
achiangdoes bzr even have rebase?12:07
achiangbzr help says no12:07
beunonot by default12:07
bob2not built in12:07
beunothere's: http://wiki.bazaar.canonical.com/Rewrite12:07
bob2bzr-rewrite12:07
beunoachiang, keep in mind once you rebase, all existing branches out there are incompatible/unmergeable12:08
achiangugh, yeah12:08
achiangit might be better to do a rebase and then create a brand new branch12:09
* beuno nods12:09
achiangbeuno: but what if the existing branches out there are only "leaf" branches... that is, i do not expect any incoming MP's from them?12:09
beunoachiang, then it shouldn't matter12:09
beunothey won't be able to pull anymore without doing something like --overwrite12:10
achiangbeuno: could an existing leaf branch still successfully pull from lp:project ?12:10
achiangah12:10
achianga one-time --overwrite for the 1 or 2 people with the branch12:10
beunoyeah, all the answers around this are going to to suck  :)12:10
* beuno nods12:10
beunoif it's a small amount of people, it's manageable12:11
achiangchanging the branch name isn't fun either12:11
achiangwe actually have more consumers of that12:11
beunoachiang, well, if you create a new branch, LP maps whatever to lp:projectname12:11
beunoso I think that would be fine12:11
achiang(but they have ephemeral environments and do brand new pulls every time)12:11
achiangoh, that's interesting12:12
beunolp:projectname is a symlink, in that sense12:12
achianggot it12:12
achiangso i currently have 'trunk' and lp:project maps to trunk12:12
achiangif i were to create say... trunc, i could remap lp:project to trunc?12:13
achiangcould i then delete trunk12:13
beunowell, you have ~someteam/someproject/trunk12:13
achiangand rename trunc => trunk?12:13
beunoyes12:13
achiang(the trunc is short for truncate, which is what i want to do with those jpegs ;)12:14
achiangpuns! everywhere!12:14
* beuno regrets helping12:16
achiangboo12:16
achiangso this is interesting12:21
achiangthe giant blobs were all added in literally -r 112:22
achiangbut nothing else from -r 1 has survived over time12:22
achiangso i wonder if that means my rewrite command will be easier, since nothing from that bad commit even remains anymore12:22
beunoachiang, yeah, it may be easier to rewrite and chop off the first commit12:25
achianghow do i install this plugin?12:26
bob2note that everyone still needs to reclone12:28
achiangbob2: noted12:28
beunoachiang, IIRC, you throw it in ~/.bazaar/plugins12:29
beunojust branch it in there12:29
achiangah, ok12:29
jelmerachiang: please be warned that bzr-rewrite is a little bit rough around the edges12:32
achiangjelmer: define "rough" ?12:32
jelmerachiang: its UI is a bit clunky, and there there are some open issues around how it rewrites branches12:34
achiangmmm...12:34
achiangnow that i've discovered that -r 1 is my bad commit, perhaps i should restate my question/problem: how might i clone a bzr branch with everything *but* the first commit?12:36
achiangor Nth, commit, since in reality, i want everything from -r 4 onward12:36
jelmerachiang: there isn't really a way to do that12:37
jelmeryou can do a lightweight checkout or a stacked branch to work around it12:38
jelmerthe revision will still be in your history, it just won't be pulled down to your local disk12:38
achiangmaybe i'll just experiment with rewrite for a bit and see how far it gets me12:38
beunoo/ jelmer12:45
jelmerhey beuno!12:45
achiangjelmer: so briefly, what would the syntax of bzr rebase be here? i'm trying to grok the help you wrote but it's not clicking.12:45
jelmerbeuno: long time no see - how are things?12:45
jelmerachiang: you probably want something like run "bzr replay -r2..-1 /path/to/original/branch" from a newly inited branch12:46
achiangjelmer: will things get screwed up if i'm inside a repo?12:47
beunojelmer, things are good!  busy busy busy, so that doesn't seem to change over time  :)  You?  I heard rumours you moved to London voluntarily12:47
jelmerachiang: no, it will not change any existing revisions - just add new ones12:48
achiangjelmer: ok, thanks. i'll give it a shot12:48
jelmerbeuno: :) What are you hacking on these days?12:48
jelmerbeuno: I did indeed, working very close to the old C offices :)12:48
beunojelmer, as good of a view?   I'm doing a bit of everything nowadays, but the Ubuntu click appstore is probably the most exciting one12:49
jelmerbeuno: It's pretty much impossible to beat that view. :-)12:50
jelmerbeuno: Cool - that's the mobile side of things?12:50
beunojelmer, well, it's the future of everything!  but currently works best on phones and tablets, yes12:51
ychaoucheHello !17:54
ychaoucheIs there a way to search in log messages ?17:54
jelmerychaouche: yes, bzr-search17:54
ychaouchethanks jelmer17:54
=== zyga_ is now known as zyga-remote

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