[00:04] <Phoenixz> maxb: nope... and its committed, pusehd,  and then pulled by me
[00:53] <kgoetz> has anyone seen a bzr-monotone plugin? i've not found anything, but asking incase
[00:53] <kgoetz> i could probably do it via git, but that sounds scary ;)
[00:56] <kgoetz> ah, lp:bzr-mtn - will investigate
[00:57] <kgoetz> wonder if i can get lp to email me if it gets updated
[00:57] <kgoetz> (aka, starts to exist)
[01:03] <jelmer> kgoetz: you can subscribe to the branch :-)
[01:03] <kgoetz> jelmer: i hadn't noticed it had one - cheers :)
[12:24] <catphish> does bazaar store branches git-style (link to the tip revision) of like hg (all commits are marked with the branch name)
[12:26] <edakiri> To compress and archive a repository: are there expendable indexes which can be erased or a more compact repository format that can be used for a repository which will be archived and compressed?
[12:27]  * catphish has used way to many VCSs this week
[12:28] <edakiri> Hmmmm. Maybe I can save space my removing the working tree.
[12:29] <kgoetz> catphish: just use bzr, and plugins for other vcs' ;)
[12:29] <catphish> lol
[12:29] <catphish> personally i'm afraid i will always use git, but i'm supporting a few others
[12:37] <fullermd> catphish: Pointers to tips.
[12:37] <fullermd> edakiri: Conceptually?  Probably.  But there's no implementation support AFAIK.
[12:37] <catphish> gdgd :)
[12:38] <fullermd> Actually, I thought hg did too.
[12:38] <fullermd> I thought mtn with its certs was the only major system that defined branches by marking revs.
[12:39] <fullermd> Well, and darcs, but that's another story wholesale.
[12:39] <maxb> hg basically has something like bzr's "branch nicknames", except hg actually uses them to define what branch a revision is on
[12:40] <maxb> and there's no explicit tip pointer - just the last revision with a particular nick
[12:44] <catphish> i just got 2 completely opposite answers
[12:47] <maxb> huh?
[12:49] <maxb> catphish: bzr's branches are the pointer to tip revision model. bzr also has a concept called branch nick, where a string is embedded in each revision, but it's just informational (shown in log messages)
[12:49] <catphish> oh ok
[12:49] <catphish> that makes more sense, thanks
[12:50] <maxb> It's not quite clear to me why branch nick exists, but it is occasionally useful *if* people have been populating it suitably
[13:04] <edakiri> I'm having trouble finding (in the documentation) how to change the parent
[13:06] <catphish> why would you want to change the parent of a commit?
[13:06] <catphish> i'm new to bazaar, but that sounds unwise
[13:07] <AfC> Evening
[13:10] <edakiri> catphish: not of a commit. of a repository
[13:11] <catphish> ah
[13:11] <catphish> :
[13:12] <catphish> )
[13:20] <maxb> edakiri: I'm afraid I still don't understand the question - repositories do not have parents
[13:21] <edakiri> maxb: yes, i mean branch.  The current case is a standalone repo.
[13:24] <edakiri> removing the working tree in this case reduced the size by 1/5
[18:55] <mgedmin> launchpad ate my bazaar branch :(
[18:55] <mgedmin> bzr branch lp:~mgedmin/gtimelog/app-indicator -> bzr: ERROR: RemoteRepository() is not compatible with RemoteRepository() different serializers
[18:56] <mgedmin> I _think_ what happened was I created a branch off trunk, pushed it to launchpad (which made it a stacked branch)
[18:56] <mgedmin> and then later I upgraded the trunk branch
[18:56] <mgedmin> and now this one is broken
[18:56] <mgedmin> http://bazaar.launchpad.net/~mgedmin/gtimelog/app-indicator/revision/148 gives me an Oops!
[18:56] <mgedmin> maybe I should talk in #launchpad and not here
[19:27] <vadi2> Would anyone know how to create a diff of a file between it's current and the latest tagged (with any tag) version in bzr?
[19:28] <Meths> bzr help diff and bzr help revisions  will probably help with that.
[19:34] <vadi2> nothing on revisions
[19:35] <vadi2> Guess I got it, though. bzr tags
[19:35] <mgedmin> bzr diff -r tag:TAGNAME filename.txt ?
[19:35] <vadi2> yeah, I don't know the tagname - have to find it out
[19:35] <vadi2> bzr tags shows them, so that works for me. thank you
[19:48] <psusi> is there a bzr equivalent of git describe?  Meaning give me the name of the most recent tag?
[19:51] <LeoNerd> bzr tags | head -1  ?
[19:51] <LeoNerd> Er.. tail perhaps
[19:52] <LeoNerd> Oh..  bzr tags --sort=time | tail -1
[19:52] <LeoNerd> That's getting awkward
[19:52] <LeoNerd> Damnit, can we please have shell aliases in bazaar.conf now?
[19:52] <LeoNerd> lasttag = tags --sort=time | tail -1    would be nice
[19:52] <jelmer> psusi: there is an open bug about it, I plan on implementing a command like that
[19:53] <vadi2> LeoNerd: cool, thanks
[19:53] <LeoNerd> I have an ever-growing list of things I'd like ot put in aliases but I can't because they're full shell pipelines
[19:54] <LeoNerd> bzr di | view "+setf diff" -
[19:54] <jelmer> LeoNerd: why not put that in your shell aliases?
[19:54] <LeoNerd> Because I want to type  bzr viewdiff   and not   bzr-viewdiff
[19:54] <LeoNerd> I played that game with CVS
[19:55] <LeoNerd> I had a  bin/cvs  that simply tested if  cvs-$1 was available, exec'ed that, or real cvs
[19:55] <jelmer> LeoNerd: alternatively, perhaps a trivial bzr plugin that provides that command?
[19:55] <LeoNerd> It's 2011, not 1970. I shouldn't have to resort to such hackery
[19:55] <psusi> there we go...
[19:56] <lifeless> LeoNerd: so the tension is that we need bzr configs to work on windows too and its severely lacking in the shell dept
[19:56]  * jelmer waves to lifeless 
[19:56] <LeoNerd> I wouldn't mind a plugin tat didn't work on Window
[19:56] <LeoNerd> A plugin that provides more flexible aliases
[19:58] <jelmer> LeoNerd: The question is how much shell-like behaviour would you like to support? And which shell would you want to be compatible with?
[19:59] <LeoNerd> Something I can easily play Lego^W unix with it
[19:59] <LeoNerd> bzr di -rtag:`bzr latesttag`..    would be nice
[19:59] <LeoNerd> bzr di -rafter:tag:`bzr latesttag`..    would be nicer still, but I don't believe  after   works yet
[20:00] <psusi> what the hell... I seem to have some broken tags... bzr tags shows ? for the revision
[20:00] <jelmer> LeoNerd: we already have one extension language for bazaar, I would be wary of adding another, especially if it's a custom language.
[20:01] <jelmer> psusi: those would be tags of revisions that are not in your currnet branch
[20:01] <jelmer> they're not necessarily broken
[20:01] <psusi> well shoot.... how can I ignore those?  it's putting a damper on my attempt to diff the wc against the last tag ;)
[20:06] <psusi> wth?  bzr tags --sort=time is not putting them in a sane order either... I'm testing this on a copy of lp:ubuntu/e2fsprogs I had around and it's showing the tags all out of order
[20:06] <jelmer> it sorts by the time of the revision that was tagged IIRC
[20:07] <lifeless> thats correct
[20:07] <lifeless> you probably want a debversion sort
[20:10] <psusi> actually I guess they are mostly in order... but for some reason it messes up at the end... goes from upstream-1.41.14 to 1.41.14-1, then back to 1.35-8ubuntu2, then up to 1.37-2sarge1, and finally ends with upstream-1.37, which it shows as ?
[20:11] <lifeless> perhaps you could file a bug on bugs.launchpad.net/udd
[20:51] <mgedmin> thank you for bzr push :parent
[23:13] <mgedmin> bzr branch lp:~gtimelog-dev/gtimelog/packaging gtimelog-packaging
[23:13] <mgedmin> KeyError: 'Bazaar-NG Loom branch format 7\n'
[23:13] <mgedmin> my guess would be I'm missing some plugin (loom)?