| mark06 | so, a follow-up to my uncommit discussion from the other day, how about bzr heads --dead-only? | 01:49 |
|---|---|---|
| mark06 | ok it will not show all uncommits, only last one, but it's a good start no? | 01:50 |
| mark06 | is there any case where this might be problematic? bzr branch a b; cp a/.bzr/branch/branch.conf b/.bzr/branch/branch.conf? | 03:57 |
| mark06 | i.e. invalid configuration that doesn't really apply for the new branch? | 03:59 |
| lifeless | shouldn't be; its equivalent to cp -a a b | 04:06 |
| lifeless | modulo some rules about what revisions are cloned in the repo etc | 04:06 |
| === jam3 is now known as jam | ||
| mark06 | ok, thanks! | 04:14 |
| mark06 | although I'm not sure if it's equivalent to filesystem copy, since unreferenced commits (uncommitted commits) will not exist on target branch | 04:15 |
| lifeless | 'modulo some rules about what revisions are cloned in the repo etc' | 04:19 |
| lifeless | mark06: they don't exist in the source branch either | 04:20 |
| lifeless | mark06: only in the source repo | 04:20 |
| lifeless | mark06: and if you have a shared repo, branch a b within it won't be cloning revisions at all | 04:20 |
| mark06 | I only use standalone branches, sorry | 04:20 |
| lifeless | mark06: doesn't worry me; just pointing out some of the subtleties | 04:20 |
| mark06 | I mean they exist in source branch cause it's standalone, containing the repo | 04:21 |
| mark06 | I didn't get modulo | 04:21 |
| === echo-are` is now known as echo-area | ||
| === thumper is now known as thumper-afk | ||
| === mgz is now known as mgzh | ||
| === echo-are` is now known as echo-area | ||
| === thumper-afk is now known as thumper | ||
| === maxb_ is now known as maxb | ||
| === thumper is now known as thumper-afk | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!