Rev 6031: Update whatsnew and release-notes to reflect the new reality. in http://bazaar.launchpad.net/~jameinel/bzr/2.4-tag-fetch-flag-771184

John Arbash Meinel john at arbash-meinel.com
Wed Aug 10 07:30:10 UTC 2011


At http://bazaar.launchpad.net/~jameinel/bzr/2.4-tag-fetch-flag-771184

------------------------------------------------------------
revno: 6031
revision-id: john at arbash-meinel.com-20110810073003-8e8r9quptbpcrmaa
parent: john at arbash-meinel.com-20110809141805-9lq771mvpsukl0pe
committer: John Arbash Meinel <john at arbash-meinel.com>
branch nick: 2.4-tag-fetch-flag-771184
timestamp: Wed 2011-08-10 09:30:03 +0200
message:
  Update whatsnew and release-notes to reflect the new reality.
-------------- next part --------------
=== modified file 'doc/en/release-notes/bzr-2.4.txt'
--- a/doc/en/release-notes/bzr-2.4.txt	2011-07-27 13:17:45 +0000
+++ b/doc/en/release-notes/bzr-2.4.txt	2011-08-10 07:30:03 +0000
@@ -56,6 +56,10 @@
 
   (John Arbash Meinel, #609187, #812928)
 
+* Fetching tags when fetching the tip revision of a branch is now
+  controlled by the config setting ``branch.fetch_tags``. The behavior has
+  been reverted to 2.3's not-fetching tagged revisions by default.
+  (John Arbash Meinel, #771184)
 
 * The fix for bug #513709 caused us to open a new connection when
   switching a lightweight checkout that was pointing at a bound branch.
@@ -63,6 +67,7 @@
   avoiding an extra SSH connection, etc.
   (John Arbash Meinel, #812285)
 
+
 Documentation
 *************
 

=== modified file 'doc/en/whats-new/whats-new-in-2.4.txt'
--- a/doc/en/whats-new/whats-new-in-2.4.txt	2011-07-15 09:23:14 +0000
+++ b/doc/en/whats-new/whats-new-in-2.4.txt	2011-08-10 07:30:03 +0000
@@ -38,10 +38,11 @@
 ***************************
 
 When tags are copied from a branch, the associated revisions are now copied
-too.  Previously operations like branching, merging or pulling might have
-copied new tags visible in ``bzr tags``, but not copied the revisions.  Now
-revisions from tags will always be present, so that operations like ``bzr
-log -r tag:foo`` will always work.
+too if the config entry ``branch.fetch_tags`` is set to True.  Operations
+like branching, merging or pulling will still always copy new tags visible
+in ``bzr tags``. When the config is set, it will now also copy the
+revisions and their ancestry.  This way tagged revisions will always be
+present, so that operations like ``bzr log -r tag:foo`` will always work.
 
 Deprecated command synonyms
 ***************************



More information about the bazaar-commits mailing list