/srv/irclogs.ubuntu.com/2013/06/12/#bzr.txt

bob2Demosthenex, sure, cherrypicking is a thing00:17
bob2Demosthenex, but in practice it'd often be better to not do that and instead make use of the templates and derive from them or whatever00:17
Demosthenexmy example was where while making a document, a change should return to the parent to be included in new/updated docs from now on.00:23
Demosthenexobviously not everything should be ported back00:24
Demosthenexand the alternative is manually updating...00:24
Demosthenexthe second example i have is another common one, where you have a standardized config file as the parent, each host has a branch with it's changes. why not push a single commit from a child back to parent, so it can push to the other children (ie: updating the standard)00:25
Demosthenexthat is cherry picking?00:25
lifelessno00:25
lifelesscherry picking is merging a non-connected part of the history graph00:25
Demosthenexwell, branching/merging tends to imply that changes will eventually return to the trunk...00:27
Demosthenexthat's why i thought fork was right...00:27
Demosthenexparallel forks00:27
Demosthenexhow can you exchange single commits when they share a parent?00:27
bob2cherry-pick00:54
=== wedgwood is now known as wedgwood_away
lifelessor ensure they are teh first commit on the branch :)01:09
Demosthenexboth examples start from a very slow to change parent... all the work is in the children.01:11
Demosthenexi'm thinking it sounds likely i just may do it manually :P01:11
Demosthenexi didn't see much in the bazaar site on cherry picking.01:11
bob2well, you'd need to read the manual01:13
Demosthenexhttp://wiki.bazaar.canonical.com/CherryPick01:15
bob2sure01:16
lifelessDemosthenex: I generally just make sure there is a branch which can be fully merged.01:17
lifelessDemosthenex: don't tangle up 'things you want to merge' and 'things you don't want to merge.'01:17
Demosthenexlifeless: i think that's the question... do i want to merge?01:19
Demosthenexit's just a common occurance, i'm using a documentatio template, it's small and contains code...01:19
Demosthenexi write a document, and change the code snippets (lots of docs, little code), and i want to push just the code portions that came from the template back01:20
Demosthenexright now i hand repeat those changes.01:20
bob2which is silly01:20
bob2either make the changes upstream or use cherry-pick01:20
lifelessright01:21
Demosthenexthat's why i was asking if cherry picking might do it01:21
lifelessor use a third branch for those changes until you're satisfied and merge that branch both upstream and to your doc branch01:21
lifelessyes cherrypicking will copy patches, its basically the same as diff+patch01:22
Demosthenexi'm pretty sure i can isolate the changes that i want to a whole commit, thus my interest01:22
_archHey, I want to add a revno as a variable to each committed file. Any suggestions? I've tried to write a post_commit-hook but it does not seem to recognize changed files.08:13
lifelesspost-commit would be too late08:13
lifelessthere is a plugin for doing variable injections like that08:13
_archThe keyword-plugin?08:14
bob2suggest not doing that08:15
_archat all? I don't like the idea much either but I need some way to get revno for each file a customer is using for support and debug :(08:16
lifeless_arch: do they have bzr?08:16
lifeless_arch: if so, just have them run 'bzr revision-info'08:17
_archNo. I'll try to explain08:18
bob2add it somewhere during your build process08:18
_archThe files run on an embedded system. Our customer gets modified files from us every now and then. They might not have to update all of the files on the system08:19
_archthey also might roll back on some of the files every now and then08:20
bob2use 'bzr revision-info' in your build script08:20
lifelessdo they edit the files ?08:20
_archno they don't08:20
lifelessIf not, just ask them for the shasum of the file08:20
lifelessyou can look that up08:20
lifelessor, as bob2 says, embed version info as you ship the file to the customer, rather than in VCS08:21
_archcan't look that up, because they don't remember which version of the file they are using and it's not trivial to get the shasum from the embedded system.08:21
_archI guess that's a better way08:21
_archit's a damn stupid problem anyway :)08:22
hikikohello11:56
hikikois there any bazaar command/option to see the differences between 2 different branches? (like bzr diff but for all files)11:57
=== wedgwood_away is now known as wedgwood
rlyIs there a gitk like tool for bzr?14:19
rlyALso, what's the command to delete all local changes like git reset --hard?14:22
vilarly:  try qbzr or bzr-gtk plugin14:24
vilarly:  probably 'bzr revert'14:24
rlyvila: note that I didn't commit anything.14:25
vilaright, so 'bzr revert' will  do (more explanations with 'bzr help revert')14:26
rlyvila: how do I do the equivalent of git pull?14:27
rlyvila: bzr merge does something different.14:27
rlyIt seems to be bzr update14:28
vilabzr pull ?14:30
rlyvila: thanks14:35
rlyI don't get why there are so many version control systems, but I suppose everyone must be thinking that everybody else before did it wrong.14:36
LeoNerdOften because projects have to get to a certain level before they become "public" enough that everyone else sees them, so you tend to get multiple differnet ones being started all at the same time14:37
rlySo far I have used: cvs, svn, bzr, monotone, darcs,git,fossil,veracity,mercurial, and I am sure I am forgetting a few.14:38
LeoNerdp4?14:39
rlyNo14:39
LeoNerdAh.. lucky :)14:39
rlyI installed bzr-gtk, and then what?14:42
rlyI had expected a bzr-gtk command in /usr/bin14:42
rlybzrk also does nothing.14:45
rlyAt no point does this page explain how to use it: http://wiki.bazaar.canonical.com/bzr-gtk?action=show&redirect=BzrGtk14:47
rlyIt lists a changelog which is at best a detail.14:47
rlyI get it finally.14:52
=== mmrazik is now known as mmrazik|afk
=== SamB_ is now known as SamB
ianbrandtGreetings.  I had a symlink in Bazaar that prevented Windows users from checking out the project per https://bugs.launchpad.net/bzr/+bug/81689.  I've removed the symlink, added a copy of the file in its place, and committed a new HEAD revision.  On Windows I still get the same error trying to branch the project.  Does this bug apply if there is a symlink anywhere in the history of the project?  I would have thought a checkout would18:41
ianbrandtif the latest revision contains no symlinks.18:41
ubot5Launchpad bug 81689 in Bazaar "Branches with symlinks can't be checked out on Windows" [High,In progress]18:41
ianbrandtabentley: Hello.  I noticed you started the wiki page on Windows symlink support (http://wiki.bazaar.canonical.com/WindowsSymlinkSupport).  Do you know if there is any workaround for getting "bzr: ERROR: Unable to create symlink 'foo' on this platform" on checkout even after the 'foo' symlink has been removed and replaced with a file in the latest commit?19:14
abentleyianbrandt: No, if the symlink was removed in the latest commit, I'm surprised that you can't do a checkout.19:15
ianbrandtabentley: Okay.  Me too.  This is with 2.5.1.  On my mac when I do revno I get 4102.  Same on Windows where the repository was checkout out, but the tree failed to populate.19:17
ianbrandtbzr ls -R --kind=symlink at the root of the project returns nothing on my mac.19:21
ianbrandtbzr revert -r 4102 on Windows results in "bzr: ERROR: No final name for trans_id 'new-1120' file-id: None root trans-id: 'new-0'"19:21
=== ianbrandt_ is now known as ianbrandt
=== Logan_ is now known as Eating
=== wedgwood is now known as wedgwood_away
=== Eating is now known as Logan_

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