~bzr-pqm/bzr/bzr.dev : changes

~bzr-pqm/bzr/bzr.dev » Changes from revision 6123.11.14

Rev	Summary	Authors	Date
6123.11.14	Avoid using deprecated api in the unit tests for bzrlib.miss... Avoid using deprecated api in the unit tests for bzrlib.missing.	Martin von Gagern	13 years ago
6123.11.13	Rename --include-sidelines to --include-merged. Rename --include-sidelines to --include-merged. This better matches phrases used in existing code and docs.	Martin von Gagern	13 years ago
6123.11.12	Merged bzr.dev Merged bzr.dev	Martin von Gagern	13 years ago
6123.11.11	Completed renaming of argument in bzrlib.missing. Completed renaming of argument in bzrlib.missing. Previous comit there forgot a number of lines.	Martin von Gagern	13 years ago
6123.11.10	Print deprecation warnings for all uses of include_merges. Print deprecation warnings for all uses of include_merges.	Martin von Gagern	13 years ago
6123.11.9	Rename argument to include_sidelines in bzrlib.missing api a... Rename argument to include_sidelines in bzrlib.missing api as well.	Martin von Gagern	13 years ago
6123.11.8	Mention the change of option name for bzr missing in the rel... Mention the change of option name for bzr missing in the release notes.	Martin von Gagern	13 years ago
6123.11.7	Moved include_sidelines to the argument position previously ... Moved include_sidelines to the argument position previously occupied by include_merges. That way, callers that pass argumenty by position instead of by keyword (even though doing so is discouraged) will start using the new argument name already, which will probably make it easier to remove the old name at some point in the future.	Martin von Gagern	13 years ago
6123.11.6	Add new paraneters add signature's ends, fix a test and a ty... Add new paraneters add signature's ends, fix a test and a typo, check that no errors and no output is emitted when using assertLogRevnos.	Vincent Ladeuil	13 years ago
6123.11.5	Document the --omit-merges and --include-sidelines options i... Document the --omit-merges and --include-sidelines options in the release notes.	Martin von Gagern	13 years ago
6123.11.4	Introduce an option "--omit-merges" for "bzr log". Introduce an option "--omit-merges" for "bzr log". This will omit the merging commits themselves, i.e. commits with more than a single parent. The idea is that these commits tend to describe the mechanics of code development, but are at best only summaries of the work done in sidelines. So omitting them but including the sidelines will print all the commits that actually contributed features to the code, without too much noise and duplicate information. This is particularly useful when generating change logs for websites or tarballs.	Martin von Gagern	13 years ago
6123.11.3	Add blackbox test for --include-sidelines option. Add blackbox test for --include-sidelines option.	Martin von Gagern	13 years ago
6123.11.2	Suggest --include-sidelines instead of --include-merges. Suggest --include-sidelines instead of --include-merges.	Martin von Gagern	13 years ago
6123.11.1	Rename --include-merges option to --include-sidelines. Rename --include-merges option to --include-sidelines. The rationale behind this rename is the following: a MERGE is a single commit with two parents. But instead of the merge itself being ommitted from the log, it is the line(s) of development starting with the secondary parent(s). We already call the primary undotted-revno left-parent-only line of development MAINLINE, so calling the other lines SIDELINES should be an intuitive concept. The UI change is backwards compatible, as the old option name is preserved. If both options are specified, in either their positive or their negative form, then the sideline one takes precedence. Conflicting options are not reported. That means that a --include-sidelines argument in an alias might take precedence over an --no-include-merges argument on the command line. As aliases and command line tend to be written by the same person, this should be a rare scenario. The tests have not been updated yet, in order to show that the modification does not break any existing tests. Updated tests will be in a separate commit. The Python API hasn't been changed, as it's more difficult to hide backwards-compatibility options there, and as two options to the same effect might confuse programmers.	Martin von Gagern	13 years ago
6123.1.14	(jr) add class GettextIndentedHelpFormatter to add gettext t... (jr) add class GettextIndentedHelpFormatter to add gettext translations to option help (Jonathan Riddell)	Canonical.com Patch ...	13 years ago
6123.1.13	(vila) Provide NameMatcher for config stores using arbitrary... (vila) Provide NameMatcher for config stores using arbitrary names for the sections. (Vincent Ladeuil)	Canonical.com Patch ...	13 years ago
6123.1.12	(jr) Turn on translations for help topics. (Jonathan Riddell... (jr) Turn on translations for help topics. (Jonathan Riddell)	Canonical.com Patch ...	13 years ago
6123.1.11	(jr) ensure all tests using gpg keys run self.import_keys() ... (jr) ensure all tests using gpg keys run self.import_keys() first (Jonathan Riddell)	Canonical.com Patch ...	13 years ago
6123.1.10	(jr) Turn on translations for errors. (Jonathan Riddell) (jr) Turn on translations for errors. (Jonathan Riddell)	Canonical.com Patch ...	13 years ago
6123.1.9	(jelmer) In "bzr tag", (jelmer) In "bzr tag", mention when an existing tag has been updated (with --force). (Jelmer Vernooij)	Canonical.com Patch ...	13 years ago

Older »