| === doko_ is now known as doko | ||
| === Hydrogen_ is now known as Hydrogen | ||
| === bob2_ is now known as bob2 | ||
| === unenough_ is now known as unenough | ||
| === sdboyer|dcc is now known as sdboyer | ||
| pdf23ds | Is there a way to import files from one bzr branch into another with history? | 06:23 |
|---|---|---|
| === AfC is now known as AfC|tea | ||
| === AfC|tea is now known as AfC | ||
| tetha | hi | 09:48 |
| jml | hi | 09:49 |
| tetha | currently, I am collecting some of my basic data structures into some sort of private library (which is versioned using bazaar). Differing subsets of this library will be used in different projects, which are going to be versioned in bazaar again. I s there a neat way to nest checkouts, so I can have something like std/ co'd rom repository 1 and everything else to repository 2? | 09:50 |
| tetha | on the other hand, thinking this further: I need apt for source modules | 10:02 |
| Odd_Bloke | tetha: Yeah, I think you'd be better off structuring the private library such that you can check all of it out for every project. | 10:14 |
| Odd_Bloke | Furthermore, there's not really a good way to do it. Nested trees might help, once they land. | 10:14 |
| Odd_Bloke | I'll subtly ping LarstiQ, who's working on them. | 10:14 |
| tetha | Yeah, that's what I didjust now | 10:18 |
| Odd_Bloke | tetha: Cool. :) | 10:18 |
| tetha | if it grows large enough to be a problem, I will either try to abuse apt directly, look if someone wrote something like it for software or write my own ;) | 10:18 |
| Odd_Bloke | tetha: What exactly are you looking to do? | 10:19 |
| tetha | Odd_Bloke: the ideal tool would be able to contain a bunch of modules (that is, code and test-files). Each module has a name and a description and dependencies on different modules. | 10:20 |
| Odd_Bloke | tetha: Have you considered just packaging them? | 10:20 |
| tetha | given that, I am able to say "get module A" to that tool and it will get module A and transitive dependencies | 10:20 |
| tetha | furhtermore, some unified "update egverything" would be nice | 10:21 |
| tetha | I didnt dig much into that topic yet, so no | 10:22 |
| Odd_Bloke | Right. | 10:22 |
| Odd_Bloke | That would certainly solve this problem. :) | 10:22 |
| tetha | I guess so :) | 10:23 |
| LarstiQ | Odd_Bloke: 'working on them' is a bit too big a word | 12:22 |
| Odd_Bloke | LarstiQ: 'meant to be working on them'? ;) | 13:45 |
| LarstiQ | 'slowly plodding through' | 13:49 |
| unenough | how can i view a version tree of a file and graphically select revisions to diff? | 16:08 |
| LarstiQ | unenough: that sounds like work for viz from bzr-gtk or qlog from qbzr | 16:08 |
| mwhudson | unenough: 'bzr viz' | 16:09 |
| unenough | ok | 16:09 |
| ramvi | I'm looking for a revision control system for web pages. I need the source code to be able to run as well, meaning if you go to a url, you're actually running the last revision. Can bazaar do this or should I look at something else? | 17:54 |
| thumper | ramvi: I'm not entirely sure what you are asking | 17:54 |
| thumper | ramvi: there is a bzr plug-in called bzr-upload that may do what you are after | 17:55 |
| * thumper goes back to hacking | 17:55 | |
| ramvi | thumper: that's because I didnt explain myself very well | 17:55 |
| ramvi | :) | 17:55 |
| ramvi | My idea is that I've got some guys working on a webpage. php. And when I go to thewebpage.com/bzr I see the code running, not the source of the php | 17:56 |
| ramvi | thumper: so that you can test if it's working or not | 17:57 |
| beuno | I still don't understand what you mean | 17:57 |
| ramvi | jeez, I suck. i'm sorry. launchpad is a place where you the view the branch source, right? | 17:58 |
| thumper | ramvi: launchpad has a branch viewer | 17:59 |
| thumper | ramvi: but the branch has to be in launchpad in order to see it | 17:59 |
| beuno | ramvi, so, you want loggerhead to view source | 17:59 |
| beuno | ramvi, loggerhead is a bzr web viewer | 17:59 |
| === fta_ is now known as fta | ||
| ramvi | thanks | 18:04 |
| fullermd | Heh. | 18:54 |
| fullermd | http://thread.gmane.org/gmane.os.dragonfly-bsd.kernel/12079/focus=12144 | 18:54 |
| fynn | in Bazaar, what's the proper way to get all patches committed by a certain username? | 19:01 |
| beuno | fynn, bzr whoami 'Name Lastname <your@email>' | 19:01 |
| Pieter | beuno: I think he means something along the lines of bzr log --author="Name Lastname" | 19:03 |
| fynn | indeed I do. | 19:04 |
| beuno | :) | 19:04 |
| fynn | I want "display all patches committed by James Hacker" | 19:04 |
| fynn | in SVN, the way to do it is dump an XML log and parse it. | 19:05 |
| fynn | Doesn't bzr have an xml log? | 19:05 |
| beuno | fynn, bzr log --short | grep 'James Hacker' | 19:05 |
| beuno | ? | 19:05 |
| beuno | yes | 19:05 |
| beuno | there's a plugin calles bzr-xmloutput | 19:05 |
| beuno | http://launchpad.net/bzr-xmloutput | 19:05 |
| fynn | beuno: yeah, my problem is with grepping a short common string like "sam" | 19:06 |
| beuno | fynn, you can do it with xml | 19:06 |
| beuno | or, do bzrlib hackery | 19:06 |
| Pieter | or use git-bzr and git log --author="sam" ;) | 19:07 |
| * beuno hits Pieter on the head | 19:07 | |
| === abentley1 is now known as abentley | ||
| poolie | hello | 21:53 |
| mwhudson | hi poolie | 21:55 |
| poolie | hi | 21:55 |
| poolie | are you back home now? | 21:55 |
| mwhudson | no, still epic-ing | 21:56 |
| === thunderstruck is now known as gnomefreak | ||
| === thunderstruck is now known as gnomefreak | ||
| lifeless | just found the git book; for folk interested in tracking what they do | 22:26 |
| lifeless | http://book.git-scm.com/7_the_packfile.html | 22:26 |
| beuno | that's a very nice explanation | 22:32 |
| beuno | I'm jealous of their webpage | 22:32 |
| beuno | http://git-scm.com/about | 22:32 |
| === mark1 is now known as markh | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!