Rev 5279: (mbp) avoid inaccurate use of "linux" or non-gnu-compliant "open source" in file:///home/pqm/archives/thelove/bzr/%2Btrunk/
Canonical.com Patch Queue Manager
pqm at pqm.ubuntu.com
Thu Jun 3 04:18:54 BST 2010
At file:///home/pqm/archives/thelove/bzr/%2Btrunk/
------------------------------------------------------------
revno: 5279 [merge]
revision-id: pqm at pqm.ubuntu.com-20100603031853-rzypooksqjaonb9m
parent: pqm at pqm.ubuntu.com-20100602040730-ihpjn6ik36wwnfo3
parent: mbp at canonical.com-20100602050331-n2p1qt8hfsahspnv
committer: Canonical.com Patch Queue Manager <pqm at pqm.ubuntu.com>
branch nick: +trunk
timestamp: Thu 2010-06-03 04:18:53 +0100
message:
(mbp) avoid inaccurate use of "linux" or non-gnu-compliant "open source"
(Martin Pool)
modified:
INSTALL INSTALL-20051019070340-4b27f2fb240c7943
NEWS NEWS-20050323055033-4e00b5db738777ff
bzrlib/breakin.py breakin.py-20070417043829-so46nevf978u713k-1
bzrlib/builtins.py builtins.py-20050830033751-fc01482b9ca23183
bzrlib/config.py config.py-20051011043216-070c74f4e9e338e8
bzrlib/doc_generate/autodoc_man.py bzrman.py-20050601153041-0ff7f74de456d15e
bzrlib/filters/eol.py eol.py-20090327060429-todzdjmqt3bpv5r8-1
bzrlib/help_topics/__init__.py help_topics.py-20060920210027-rnim90q9e0bwxvy4-1
bzrlib/help_topics/en/configuration.txt configuration.txt-20060314161707-868350809502af01
bzrlib/help_topics/en/content-filters.txt contentfilters.txt-20080516145112-7x1meuoci5w41isv-1
bzrlib/tests/stub_sftp.py stub_sftp.py-20051027032739-0e7ef4f7bab0e174
bzrlib/tests/test__dirstate_helpers.py test_dirstate_helper-20070504035751-jsbn00xodv0y1eve-2
bzrlib/tests/test_directory_service.py test_directory_servi-20080305221044-vr2mkvlsk8jypa2y-2
bzrlib/urlutils.py urlutils.py-20060502195429-e8a161ecf8fac004
doc/developers/HACKING.txt HACKING-20050805200004-2a5dc975d870f78c
doc/developers/case-insensitive-file-systems.txt caseinsensitivefiles-20081117224243-p84xpmqnsa1p8k91-1
doc/developers/code-style.txt codestyle.txt-20100515105711-133ealf7ereiq2eq-1
doc/developers/planned-change-integration.txt plannedchangeintegra-20070619004702-i1b3ccamjtfaoq6w-1
doc/en/admin-guide/code-browsing.txt codebrowsing.txt-20091205144603-lgpl0e0z6lzk2rdw-3
doc/en/admin-guide/introduction.txt introduction.txt-20091205144603-lgpl0e0z6lzk2rdw-7
doc/en/admin-guide/upgrade.txt upgrade.txt-20091205144603-lgpl0e0z6lzk2rdw-12
doc/en/upgrade-guide/overview.txt overview.txt-20090702082510-q2pocf7uhntljqnl-4
doc/en/user-guide/branching_a_project.txt branching_a_project.-20071122141511-0knao2lklsdsvb1q-2
doc/en/user-guide/configuring_bazaar.txt configuring_bazaar.t-20071128000722-ncxiua259xwbdbg7-1
doc/en/user-guide/installing_bazaar.txt installing_bazaar.tx-20071114035000-q36a9h57ps06uvnl-4
doc/en/user-guide/plugins.txt plugins.txt-20060314145616-525099a747f3ffdd
doc/en/user-guide/setting_up_email.txt setting_up_email.txt-20060314161707-fd242c8944346173
doc/en/user-guide/version_info.txt version_info.txt-20060921215543-gju6o5xdic8w25np-1
=== modified file 'INSTALL'
--- a/INSTALL 2010-01-29 10:36:23 +0000
+++ b/INSTALL 2010-06-02 05:03:31 +0000
@@ -15,10 +15,10 @@
bzr can optionally use compiled versions of some parts of the code
for increased speed. When installing bzr you need the ability to
-build C extensions. Some Linux distributions package the necessary
+build C extensions. Some GNU/Linux distributions package the necessary
headers separately from the main Python package. This package is
probably named something like python-dev or python-devel. FreeBSD,
-Windows, source-based Linux distributions, and possibly other operating
+Windows, source-based GNU/Linux distributions, and possibly other operating
systems, have the required files installed by default.
If you are installing bzr from a bzr branch rather than a release tarball,
=== modified file 'NEWS'
--- a/NEWS 2010-06-01 14:09:27 +0000
+++ b/NEWS 2010-06-02 05:03:31 +0000
@@ -3950,8 +3950,8 @@
can have a large effect on ``bzr checkout`` times. (John Arbash Meinel)
* selftest now supports a --parallel option, with values of 'fork' or
- 'subprocess' to run the test suite in parallel. Currently only linux
- machine work, other platforms need patches submitted. (Robert Collins,
+ 'subprocess' to run the test suite in parallel. Currently only Linux
+ machines work, other platforms need patches submitted. (Robert Collins,
Vincent Ladeuil)
* ``tests.run_suite`` has a new parameter ``suite_decorators``, a list of
@@ -6705,7 +6705,7 @@
* bzr main script cannot be imported (Benjamin Peterson)
-* On Linux bzr additionally looks for plugins in arch-independent site
+* On GNU/Linux bzr additionally looks for plugins in arch-independent site
directory. (Toshio Kuratomi)
* The ``set_rh`` branch hook is now deprecated. Please migrate
@@ -7048,7 +7048,7 @@
* BZR_LOG environment variable controls location of .bzr.log trace file.
User can suppress writing messages to .bzr.log by using '/dev/null'
- filename (on Linux) or 'NUL' (on Windows). If BZR_LOG variable
+ filename (on Unix) or 'NUL' (on Windows). If BZR_LOG variable
is not defined but BZR_HOME is defined then default location
for .bzr.log trace file is ``$BZR_HOME/.bzr.log``.
(Alexander Belchenko, #106117)
=== modified file 'bzrlib/breakin.py'
--- a/bzrlib/breakin.py 2010-02-26 03:00:34 +0000
+++ b/bzrlib/breakin.py 2010-06-02 04:50:35 +0000
@@ -78,7 +78,7 @@
def hook_debugger_to_signal():
"""Add a signal handler so we drop into the debugger.
- On Linux and Mac, this is hooked into SIGQUIT (C-\\) on Windows, this is
+ On Unix, this is hooked into SIGQUIT (C-\\), and on Windows, this is
hooked into SIGBREAK (C-Pause).
"""
=== modified file 'bzrlib/builtins.py'
--- a/bzrlib/builtins.py 2010-05-25 17:27:52 +0000
+++ b/bzrlib/builtins.py 2010-06-02 04:50:35 +0000
@@ -5128,7 +5128,7 @@
given, in which case it is sent to a file.
Mail is sent using your preferred mail program. This should be transparent
- on Windows (it uses MAPI). On Linux, it requires the xdg-email utility.
+ on Windows (it uses MAPI). On Unix, it requires the xdg-email utility.
If the preferred client can't be found (or used), your editor will be used.
To use a specific mail program, set the mail_client configuration option.
=== modified file 'bzrlib/config.py'
--- a/bzrlib/config.py 2010-05-25 17:27:52 +0000
+++ b/bzrlib/config.py 2010-06-02 04:50:35 +0000
@@ -843,7 +843,6 @@
' or HOME set')
return osutils.pathjoin(base, 'bazaar', '2.0')
else:
- # cygwin, linux, and darwin all have a $HOME directory
if base is None:
base = os.path.expanduser("~")
return osutils.pathjoin(base, ".bazaar")
=== modified file 'bzrlib/doc_generate/autodoc_man.py'
--- a/bzrlib/doc_generate/autodoc_man.py 2010-02-23 07:43:11 +0000
+++ b/bzrlib/doc_generate/autodoc_man.py 2010-06-02 04:50:52 +0000
@@ -186,7 +186,7 @@
.B "help"
.I "command"
.SH "DESCRIPTION"
-Bazaar (or %(bzrcmd)s) is a project of Canonical to develop an open source
+Bazaar (or %(bzrcmd)s) is a project of Canonical to develop an free
distributed version control system that is powerful, friendly, and scalable.
Version control means a system that keeps track of previous revisions
of software source code or similar information and helps people work on it in teams.
=== modified file 'bzrlib/filters/eol.py'
--- a/bzrlib/filters/eol.py 2009-05-07 05:08:46 +0000
+++ b/bzrlib/filters/eol.py 2010-06-02 04:56:07 +0000
@@ -25,8 +25,8 @@
from bzrlib.errors import BzrError
-# Real Linux/Unix/OSX newline - \n without \r before it
-_LINUX_NL_RE = re.compile(r'(?<!\r)\n')
+# Real Unix newline - \n without \r before it
+_UNIX_NL_RE = re.compile(r'(?<!\r)\n')
def _to_lf_converter(chunks, context=None):
@@ -44,7 +44,7 @@
if '\x00' in content:
return [content]
else:
- return [_LINUX_NL_RE.sub('\r\n', content)]
+ return [_UNIX_NL_RE.sub('\r\n', content)]
# Register the eol content filter.
=== modified file 'bzrlib/help_topics/__init__.py'
--- a/bzrlib/help_topics/__init__.py 2010-05-20 11:04:58 +0000
+++ b/bzrlib/help_topics/__init__.py 2010-06-02 04:50:35 +0000
@@ -618,7 +618,7 @@
_files = \
r"""Files
-:On Linux: ~/.bazaar/bazaar.conf
+:On Unix: ~/.bazaar/bazaar.conf
:On Windows: C:\\Documents and Settings\\username\\Application Data\\bazaar\\2.0\\bazaar.conf
Contains the user's default configuration. The section ``[DEFAULT]`` is
=== modified file 'bzrlib/help_topics/en/configuration.txt'
--- a/bzrlib/help_topics/en/configuration.txt 2010-05-04 14:52:33 +0000
+++ b/bzrlib/help_topics/en/configuration.txt 2010-06-02 05:03:31 +0000
@@ -90,7 +90,7 @@
As for the ``PATH`` variables, if multiple directories are
specified in ``BZR_PLUGIN_PATH`` they should be separated by the
-platform specific appropriate character (':' on Unix/Linux/etc,
+platform specific appropriate character (':' on Unix,
';' on windows)
By default if ``BZR_PLUGIN_PATH`` is set, it replaces searching
@@ -185,7 +185,7 @@
Location
~~~~~~~~
-Configuration files are located in ``$HOME/.bazaar`` on Linux/Unix and
+Configuration files are located in ``$HOME/.bazaar`` on Unix and
``C:\Documents and Settings\<username>\Application Data\Bazaar\2.0`` on
Windows. (You can check the location for your system by using
``bzr version``.)
=== modified file 'bzrlib/help_topics/en/content-filters.txt'
--- a/bzrlib/help_topics/en/content-filters.txt 2010-01-03 03:33:10 +0000
+++ b/bzrlib/help_topics/en/content-filters.txt 2010-06-02 05:03:31 +0000
@@ -8,7 +8,7 @@
format from the copy in your working tree. This lets you, or your
co-developers, use Windows development tools that expect CRLF files
on projects that use other line-ending conventions. Among other things,
-content filters also let Linux developers more easily work on projects
+content filters also let Unix developers more easily work on projects
using Windows line-ending conventions, keyword expansion/compression,
and trailing spaces on lines in text files to be implicitly stripped
when committed.
=== modified file 'bzrlib/tests/stub_sftp.py'
--- a/bzrlib/tests/stub_sftp.py 2010-05-14 09:34:16 +0000
+++ b/bzrlib/tests/stub_sftp.py 2010-06-02 04:50:35 +0000
@@ -135,7 +135,7 @@
try:
out = [ ]
# TODO: win32 incorrectly lists paths with non-ascii if path is not
- # unicode. However on Linux the server should only deal with
+ # unicode. However on unix the server should only deal with
# bytestreams and posix.listdir does the right thing
if sys.platform == 'win32':
flist = [f.encode('utf8') for f in os.listdir(path)]
@@ -452,7 +452,7 @@
# Normalize the path or it will be wrongly escaped
self._homedir = osutils.normpath(self._homedir)
else:
- # But Linux SFTP servers should just deal in bytestreams
+ # But unix SFTP servers should just deal in bytestreams
self._homedir = os.getcwd()
if self._server_homedir is None:
self._server_homedir = self._homedir
=== modified file 'bzrlib/tests/test__dirstate_helpers.py'
--- a/bzrlib/tests/test__dirstate_helpers.py 2010-02-23 07:43:11 +0000
+++ b/bzrlib/tests/test__dirstate_helpers.py 2010-06-02 04:50:35 +0000
@@ -737,7 +737,7 @@
def test_trailing_garbage(self):
tree, state, expected = self.create_basic_dirstate()
- # On Linux, we can write extra data as long as we haven't read yet, but
+ # On Unix, we can write extra data as long as we haven't read yet, but
# on Win32, if you've opened the file with FILE_SHARE_READ, trying to
# open it in append mode will fail.
state.unlock()
=== modified file 'bzrlib/tests/test_directory_service.py'
--- a/bzrlib/tests/test_directory_service.py 2010-02-23 07:43:11 +0000
+++ b/bzrlib/tests/test_directory_service.py 2010-06-02 04:50:35 +0000
@@ -28,7 +28,7 @@
class FooService(object):
"""A directory service that maps the name to a FILE url"""
- # eg 'file:///foo' on Linux, or 'file:///C:/foo' on Windows
+ # eg 'file:///foo' on Unix, or 'file:///C:/foo' on Windows
base = urlutils.local_path_to_url('/foo')
def look_up(self, name, url):
=== modified file 'bzrlib/urlutils.py'
--- a/bzrlib/urlutils.py 2010-05-27 22:10:42 +0000
+++ b/bzrlib/urlutils.py 2010-06-02 05:03:31 +0000
@@ -278,7 +278,7 @@
# on non-win32 platform
# FIXME: It turns out that on nt, ntpath.abspath uses nt._getfullpathname
# which actually strips trailing space characters.
- # The worst part is that under linux ntpath.abspath has different
+ # The worst part is that on linux ntpath.abspath has different
# semantics, since 'nt' is not an available module.
if path == '/':
return 'file:///'
=== modified file 'doc/developers/HACKING.txt'
--- a/doc/developers/HACKING.txt 2010-05-27 04:55:13 +0000
+++ b/doc/developers/HACKING.txt 2010-06-02 05:03:31 +0000
@@ -869,7 +869,7 @@
energy by emailing the **bazaar-commits** list implicitly. To do this,
install and configure the Email plugin. One way to do this is add these
configuration settings to your central configuration file (e.g.
-``~/.bazaar/bazaar.conf`` on Linux)::
+``~/.bazaar/bazaar.conf``)::
[DEFAULT]
email = Joe Smith <joe.smith at internode.on.net>
=== modified file 'doc/developers/case-insensitive-file-systems.txt'
--- a/doc/developers/case-insensitive-file-systems.txt 2009-12-02 20:34:07 +0000
+++ b/doc/developers/case-insensitive-file-systems.txt 2010-06-02 05:03:31 +0000
@@ -9,13 +9,13 @@
For example, the FAT32 file-system is most commonly found on Windows operating
systems, and has the characteristics usually associated with a Windows
file-system. However, USB devices means FAT32 file-systems are often used
-with Linux, so the current operating system doesn't necessarily reflect the
+with GNU/Linux systems, so the current operating system doesn't necessarily reflect the
capabilities of the file-system.
Bazaar supports 3 kinds of file-systems, each to different degrees.
* Case-sensitive file-systems: This is the file-system generally used on
- Linux - 2 files can differ only by case, and the exact case must be used
+ GNU/Linux: 2 files can differ only by case, and the exact case must be used
when opening a file.
* Case-insensitive, case-preserving (cicp) file-systems: This is the
=== modified file 'doc/developers/code-style.txt'
--- a/doc/developers/code-style.txt 2010-06-01 07:07:39 +0000
+++ b/doc/developers/code-style.txt 2010-06-02 04:39:08 +0000
@@ -441,5 +441,17 @@
finally:
f.close()
+
+Terminology
+===========
+
+Bazaar is a GNU project and uses standard GNU terminology, especially:
+
+ * Use the word "Linux" to refer to the Linux kernel, not as a synechoche
+ for the entire operating system. (See `bug 528253
+ <https://bugs.launchpad.net/bzr/+bug/528253>`_).
+
+ * Don't say "open source" when you mean "free software".
+
..
vim: ft=rst tw=74 ai
=== modified file 'doc/developers/planned-change-integration.txt'
--- a/doc/developers/planned-change-integration.txt 2009-12-02 20:34:07 +0000
+++ b/doc/developers/planned-change-integration.txt 2010-06-02 05:03:31 +0000
@@ -73,7 +73,7 @@
* Working tree disk ordering: Knowing the expected order for disk operations
may influence the needed use case specific APIs, so having a solid
understanding of what is optimal - and why - and whether it is pessimal on
- non linux platforms is rather important.
+ non-Linux-kernel platforms is rather important.
* Be able to version files greater than memory in size: This cannot be
achieved until all parts of the library which deal with user files are able
=== modified file 'doc/en/admin-guide/code-browsing.txt'
--- a/doc/en/admin-guide/code-browsing.txt 2009-12-11 00:00:04 +0000
+++ b/doc/en/admin-guide/code-browsing.txt 2010-06-02 05:03:31 +0000
@@ -47,8 +47,8 @@
On Ubuntu, `sudo apt-get install python-flup`
or use `easy_install flup`
-Although directions for installing these on Ubuntu Linux are given, most other
-Linux distributions should package these dependencies, making installation
+Although directions for installing these on Ubuntu are given, most other
+GNU/Linux distributions should package these dependencies, making installation
easy. For Windows and Mac OS X, they should all be ``easy_install``-able or at
worst installable from the Python sources.
@@ -101,9 +101,9 @@
This would allow the trunk branch of ProjectX to be browsed at
``http://www.example.com/loggerhead/projectx/trunk``.
-Loggerhead comes with a script allowing it to run as a service on init.d based
-Linux systems. Contributions to do a similar thing on Windows servers would
-be welcomed at http://launchpad.net/loggerhead.
+Loggerhead comes with a script allowing it to run as a service on
+``init.d`` based Unix systems. Contributions to do a similar thing on
+Windows servers would be welcomed at http://launchpad.net/loggerhead.
Other web interfaces
=== modified file 'doc/en/admin-guide/introduction.txt'
--- a/doc/en/admin-guide/introduction.txt 2009-12-07 21:51:01 +0000
+++ b/doc/en/admin-guide/introduction.txt 2010-06-02 05:03:31 +0000
@@ -27,7 +27,7 @@
What you need to run a Bazaar server
------------------------------------
-Where possible, we will discuss both Unix (including Linux) and Windows server
+Where possible, we will discuss both Unix (including GNU/Linux) and Windows server
environments. For the purposes of this document, we will consider Mac OS X as
a type of Unix.
@@ -44,7 +44,7 @@
critical components of the code. Pure Python alternatives exist for all of
these components, but they may be considerably slower. To compile these
extensions, you need a C compiler and the relevant header files from the
-Python package. On Linux, these may be in a separate package. Other
+Python package. On GNU/Linux, these may be in a separate package. Other
operating systems should have the required headers installed by default.
If you are installing a development version of Bazaar, rather than a released
=== modified file 'doc/en/admin-guide/upgrade.txt'
--- a/doc/en/admin-guide/upgrade.txt 2009-12-18 10:09:49 +0000
+++ b/doc/en/admin-guide/upgrade.txt 2010-06-02 05:03:31 +0000
@@ -28,7 +28,7 @@
Upgrading the Bazaar software is as simple as re-installing the Python package
using either the latest binary package for Windows or Mac OS X, the binary
-package provided by your Linux distribution, or installing from the source
+package provided by your GNU/Linux distribution, or installing from the source
release. See http://bazaar-vcs.org/Downloads for the latest releases for all
supported platforms.
=== modified file 'doc/en/upgrade-guide/overview.txt'
--- a/doc/en/upgrade-guide/overview.txt 2009-07-13 06:58:49 +0000
+++ b/doc/en/upgrade-guide/overview.txt 2010-06-02 05:03:31 +0000
@@ -36,7 +36,7 @@
to Bazaar 1.y. In either case, a brief outline of the steps is given
below.
-To upgrade Bazaar on Linux:
+To upgrade Bazaar on Ubuntu:
1. Ensure your package manager is configured with the required
software sources, e.g. the official release PPA for Ubuntu:
@@ -72,10 +72,10 @@
bzr-svn, are more tightly associated with Bazaar's APIs so these
typically need to be upgraded in lockstep with the core software.
-For Windows and OS X users, bzrtools and bzr-svn are typically
-included in the installer so no special steps are required to upgrade
-these. For Linux and UNIX users, bztrools, bzr-svn and many other
-popular plugins can be installed and upgraded using your
+For Windows and OS X users, bzrtools and bzr-svn are typically included in
+the installer so no special steps are required to upgrade these. For
+Ubuntu and other GNU/Linux or Unix systems users, bztrools, bzr-svn and
+many other popular plugins can be installed and upgraded using your
platform's package manager, e.g. Synaptic on Ubuntu.
=== modified file 'doc/en/user-guide/branching_a_project.txt'
--- a/doc/en/user-guide/branching_a_project.txt 2010-03-22 00:29:50 +0000
+++ b/doc/en/user-guide/branching_a_project.txt 2010-06-02 05:03:31 +0000
@@ -8,7 +8,7 @@
agree on a transfer technology.
You may decide to make the top level directory of your branch
a network share, an approach familiar to Windows users.
-Linux and OS X users might prefer access to be
+Unix users might prefer access to be
via SFTP, a secure protocol built-in to most SSH servers.
Bazaar is *very* flexible in this regard with support for
lots of protocols some of which are given below.
=== modified file 'doc/en/user-guide/configuring_bazaar.txt'
--- a/doc/en/user-guide/configuring_bazaar.txt 2009-12-02 20:34:07 +0000
+++ b/doc/en/user-guide/configuring_bazaar.txt 2010-06-02 05:03:31 +0000
@@ -19,7 +19,7 @@
Configuration files
-------------------
-Configuration files are located in ``$HOME/.bazaar`` on Linux/Unix and
+Configuration files are located in ``$HOME/.bazaar`` on Unix and
``C:\Documents and Settings\<username>\Application Data\Bazaar\2.0`` on
Windows. There are three primary configuration files in this location:
=== modified file 'doc/en/user-guide/installing_bazaar.txt'
--- a/doc/en/user-guide/installing_bazaar.txt 2009-09-09 15:08:17 +0000
+++ b/doc/en/user-guide/installing_bazaar.txt 2010-06-02 05:03:31 +0000
@@ -1,11 +1,11 @@
Installing Bazaar
=================
-Linux
------
+GNU/Linux
+---------
-Bazaar packages are available for most popular Linux distributions
-including Ubuntu/Debian, Red Hat and Gentoo.
+Bazaar packages are available for most popular GNU/Linux distributions
+including Ubuntu, Debian, Red Hat and Gentoo.
See http://bazaar-vcs.org/Download for the latest instructions.
Windows
=== modified file 'doc/en/user-guide/plugins.txt'
--- a/doc/en/user-guide/plugins.txt 2009-12-02 20:34:07 +0000
+++ b/doc/en/user-guide/plugins.txt 2010-06-02 05:03:31 +0000
@@ -35,13 +35,13 @@
Installing a plugin is very easy! If not already created, create a
``plugins`` directory under your Bazaar configuration directory,
-``~/.bazaar/`` on Linux and
+``~/.bazaar/`` on Unix and
``C:\Documents and Settings\<username>\Application Data\Bazaar\2.0\``
on Windows. Within this directory (referred to as $BZR_HOME below),
each plugin is placed in its own subdirectory.
Plugins work particularly well with Bazaar branches. For example, to
-install the bzrtools plugins for your main user account on Linux,
+install the bzrtools plugins for your main user account on GNU/Linux,
one can perform the following::
bzr branch http://panoramicfeedback.com/opensource/bzr/bzrtools
=== modified file 'doc/en/user-guide/setting_up_email.txt'
--- a/doc/en/user-guide/setting_up_email.txt 2009-12-02 20:34:07 +0000
+++ b/doc/en/user-guide/setting_up_email.txt 2010-06-02 05:03:31 +0000
@@ -62,7 +62,7 @@
--------------------------------------------
To use the default ini file, create or edit the ``bazaar.conf`` file (in
-``~/.bazaar/`` on Linux and in ``%APPDATA%\bazaar\2.0\`` in Windows)
+``~/.bazaar/`` on Unix and in ``%APPDATA%\bazaar\2.0\`` in Windows)
and set an email address as shown below. Please note that the word DEFAULT
is case sensitive, and must be in upper-case.
::
=== modified file 'doc/en/user-guide/version_info.txt'
--- a/doc/en/user-guide/version_info.txt 2009-12-02 20:34:07 +0000
+++ b/doc/en/user-guide/version_info.txt 2010-06-02 05:03:31 +0000
@@ -25,7 +25,7 @@
branch-nick: bzr.dev
You can easily filter that output using operating system tools or
-scripts. For example (on Linux/Unix)::
+scripts. For example::
$ bzr version-info | grep ^date
date: 2007-12-11 17:51:18 +0000
More information about the bazaar-commits
mailing list