/srv/irclogs.ubuntu.com/2011/04/22/#bzr.txt

magciusmgz, http://msdn.microsoft.com/en-us/library/aa363866%28v=vs.85%29.aspx00:02
magciusmgz, also, ctypes00:02
mgzalso need to be running as an administrator00:02
mgzwhich is just what stopped happening by default in the release that api was made available.00:03
magciusin Windows 7, users have the "Create symbolic link" permission by default00:03
magciusbut meh00:03
magciusnot worth it00:03
magciusit would help if you guys just wouldn't *fail*00:03
mgzI agree.00:04
mgzwhat's your source on the symlink cap being for everyone under 7?00:05
mgzI thought I'd read the opposite.00:05
magciuspersonal experience00:06
magciusI don't have the permission, and mklink works for me00:06
Jordan_UHow can i ignore mode changes? I'm working on a project locally (on my Ubuntu machine) and on a Windows machine accessed via CIFS and I don't want bzr diff or my commit history to be cluttered with mode changes.00:12
mgzgood question.00:13
mgzJordan_U: ask on the mailing list if no one pops up here with an answer.00:15
=== Merwin_ is now known as Merwin
KombuchaKipI have a commit I'd like to make to a repository I don't have write access to. How can my commit be sent as an email to the project maintainer?04:10
KombuchaKipHow can I generate a diff for my local working copy when it contains binary files that I added? Right now the binary data isn't generated in bzr diff output.04:17
cody-somervilleKombuchaKip, bzr send04:25
KombuchaKipcody-somerville: I tried. I get a "ERROR: No submit branch known or specified"04:25
cody-somervilleKombuchaKip, 'bzr help send' to see which arguments it expects and how to use it04:25
KombuchaKipcody-somerville: I used "bzr send -o ~/Desktop/Kip.diff" which is what the docs say.04:26
cody-somervilleYou need to pass as the second argument the branch you wish to submit your changes to04:27
KombuchaKipcody-somerville: How do I find that out?04:27
cody-somervilleKombuchaKip, Not sure I understand your question.04:29
KombuchaKipcody-somerville: How do I know what the second argument is? I checked out my code from a URL at bzr://blah04:29
cody-somervilleKombuchaKip, thats the second argument04:30
KombuchaKipcody-somerville: Right. But do I have to commit my changes locally first?04:30
KombuchaKipcody-somerville: I was reluctant to do that in case the commit isn't accepted upstream or needs changing.04:31
cody-somervilleyes, you need to commit locally04:31
KombuchaKipcody-somerville: But what happens if the commit isn't accepted upstream? Doesn't that cause headaches at my end because now the repos are not in sync?04:32
cody-somervilleKombuchaKip, You'd merge in any changes from them, make the changes they've requested of you, and then resubmit.04:32
KombuchaKipcody-somerville: Is there not simply a way I can generate a current diff, including the binary files as well?04:32
cody-somervilleKombuchaKip, You could commit, then push your branch to somewhere they can access, and then ask them to merge your branch in04:34
KombuchaKipcody-somerville: I think I'd prefer to just generate a diff, like I am used to with svn. How do I get bzr diff to generate binary diffs also?04:34
cody-somervilleKombuchaKip, You can't do that with svn. However, you can install bsdiff which is a program for generating and applying a patch between two binary files and tell bzr to use that via the --using argument to bzr diff.04:38
KombuchaKipcody-somerville: That's possible, but convoluted. I guess they call it bazaar for a reason.04:39
cody-somervilleJust sharing your branch with them is much easier.04:39
cody-somervilleKombuchaKip, It has nothing to do with bzr - patches aren't optimal for representing changes to binary files since binary files aren't human readable and patches are intended to be.04:40
KombuchaKipcody-somerville: Not quite. base64 is perfectly valid data for in a patch. Sometimes its necessary for non-plain text files that changed.04:41
=== m4v is now known as mkv
=== mkv is now known as m4v
=== m4v is now known as mkv
=== psynaptic|away is now known as psynaptic
=== psynaptic is now known as psynaptic|away
=== deryck is now known as deryck[lunch]
bialixgood evening dear #bzr16:40
fullermdEvening already?!  I've barely had lunch   :(16:40
bialixmy evening is your lunch :-D16:41
* bialix waves at fullermd16:41
* mgz waves at bialix16:59
bialixhey Martin!16:59
magciusis there a way I can get 'git add' like semantics?17:02
magciusi made changes to a CSS file that I don't want to commit17:02
bialixmagcius: bzr shelve allows you git stash your changes; bzr view allows you to specify subset of the tree you work on17:07
magciusbialix, bzr shelve doesn't allow me to pick out specific parts.17:08
magciusIt says "yes or no", and I want half of it.17:08
bialixsetup editor and then you'll be able to do so17:09
magciusjust $EDITOR?17:09
bialixin bazaar.conf add to DEFAULT section:17:09
bialixchange_editor = vimdiff -fo @new_path @old_path17:10
bialixor adjust the command line for your favorite editor17:10
bialixmagcius: ^17:10
magciusemacsclient -e '(diff "@old_path" "@new_path")'17:12
magciusyay17:12
bialixin the shelve prompt press 'e' now17:13
magciuswhy doesn't ^C work?17:13
magciusnow, when I press "y", I'm telling it to stash it?17:13
magciusput it away for later?17:14
=== deryck[lunch] is now known as deryck
bialixyep17:17
magciusand how can I get it back?17:17
bialixmagcius: bzr unshelve17:19
magciusok, thanks!17:20
bialix:-)17:20
=== beuno is now known as beuno-lunch
ablmf333I've 2 branch, 'svn' is a bzr checkout of svn branch, 'bzr' is branched from 'svn' by `bzr branch'.  Now 'svn' switched to a new branch, And I got lots of conflict when I try to merge 'bzr' to 'svn'.18:25
ablmf333 I guess that's because the new svn branch is created later than those changes in 'bzr'18:25
ablmf333Is there nice way to handle this?18:25
=== beuno-lunch is now known as beuno

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