[MERGE] Fix #175520 by implementing a --deep option for log
John Arbash Meinel
john at arbash-meinel.com
Wed Jan 14 16:51:20 GMT 2009
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
...
> Initially we could support just --current and --last. We'll need
> multiple id support in the core of log before --once is added,
> assuming we agree that the right behaviour is to union-log
> against the set of file-ids that once represented a file of that
> name.
I'm not sure about --once as a name, it took me a while to figure out
why you thought of it. The functionality seems ok
>
> While I'm at it, here are some thoughts on "log DIR". By default,
> we should just log what happened to the directory object. To see
> what happened to each of the current children, "log --children DIR".
> (Again, that will need multiple id support.) To see what happened
> to files that were once in DIR, "log --children --once DIR" say.
>
> Ian C.
>
>
I think most people would expect "bzr log DIR" to show the --children
form by default. I think while our current behavior is technically an
alternative, it is pretty useless.
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkluGAgACgkQJdeBCYSNAAPP4ACgr5VbxvLB5rjK9YXboagsKGFR
wf4AoI5Wk7xI7KtT1zIZZU5ct/bx9tE/
=AaQI
-----END PGP SIGNATURE-----
More information about the bazaar
mailing list