Sorting tags

Re: Sorting tags

On linux:

    bzr tags | sort -k 2 -n

you can also add the -r switch to get the newest first.

On 01/02/12 11:46, Brendan Simon (eTRIX) wrote:
> My 'bzr tags' command produces the following:
>
>     v5.6.14              251
>     v5.6.14-rc1          246
>     v5.6.14-rc2          250
>     v5.7.0               301
>     v5.7.0-dev1          257
>     v5.7.0-dev2          259
>     v5.7.0-dev3          264
>     v5.7.0-dev4          280
>     v5.7.0-rc1           281
>     v5.7.0-rc2           300
>
>
> Note that the release candidates (-rc*) and dev builds (-dev*) are 
> displayed earlier than the final releases.
>
> I want to display in revision order.  Is there a way to get bzr tags 
> to display in chronological revision order ??
>
>     v5.6.14-rc1          246
>     v5.6.14-rc2          250
>     v5.6.14              251
>     v5.7.0-dev1          257
>     v5.7.0-dev2          259
>     v5.7.0-dev3          264
>     v5.7.0-dev4          280
>     v5.7.0-rc1           281
>     v5.7.0-rc2           300
>     v5.7.0               301
>
>
> The help (bzr tags --help) wasn't that helpful for the sort arguments :(
> Note: using bzr 2.4.2.
>
> Thanks,
> Brendan.
>

--

-- 

*David Ingamells * Test Architect *Mapscape *

Henri Wijnmalenweg 5b  | 5657 EP Eindhoven  | The Netherlands
Phone +31 (0)40 7113571  | Fax +31 (0)40 7113599
www.mapscape.eu <http://www.mapscape.eu/>

Mapscape B.V. is ISO9001:2008 certified.
This e-mail and any attachment may contain corporate proprietary 
information and may only be read, copied and used by the intended 
recipient. If you have received it by mistake, please notify us 
immediately by reply e-mail and delete this e-mail and its attachments 
from your system. We believe but do not warrant that this message and 
any attachments are virus free.
Mapscape B.V. is registered at the Kamer van Koophandel Oost-Brabant 
located in Eindhoven, The Netherlands, number 17210210.

Re: Sorting tags

On 2/1/2012 11:46 AM, Brendan Simon (eTRIX) wrote:
> My 'bzr tags' command produces the following:
> 
> v5.6.14              251 v5.6.14-rc1          246 v5.6.14-rc2
> 250 v5.7.0               301 v5.7.0-dev1          257 v5.7.0-dev2
> 259 v5.7.0-dev3          264 v5.7.0-dev4          280 v5.7.0-rc1
> 281 v5.7.0-rc2           300
> 
> 
> Note that the release candidates (-rc*) and dev builds (-dev*) are 
> displayed earlier than the final releases.
> 
> I want to display in revision order.  Is there a way to get bzr
> tags to display in chronological revision order ??
> 
> v5.6.14-rc1          246 v5.6.14-rc2          250 v5.6.14
> 251 v5.7.0-dev1          257 v5.7.0-dev2          259 v5.7.0-dev3
> 264 v5.7.0-dev4          280 v5.7.0-rc1           281 v5.7.0-rc2
> 300 v5.7.0               301
> 
> 
> The help (bzr tags --help) wasn't that helpful for the sort
> arguments :( Note: using bzr 2.4.2.
> 
> Thanks, Brendan.
> 

bzr tags --sort=time

tag_sort_methods = Registry()
tag_sort_methods.register("natural", sort_natural,
    'Sort numeric substrings as numbers. (default)')
tag_sort_methods.register("alpha", sort_alpha, 'Sort tags
lexicographically.')
tag_sort_methods.register("time", sort_time, 'Sort tags chronologically.')
tag_sort_methods.default_key = "natural"

John
=:->

RE: Sorting tags

John Arbash Meinel wrote:

> bzr tags --sort=time

Interesting - bzr.dev seems to have some unnumbered tags:

...
bzr-2.4.2            6015.45.1
bzr-2.5b3            6252.1.1
bzr-2.5b4            6349.1.1
bzr-2.5b5            6437.2.2
upstream-2.3.0~beta1 ?
upstream-2.3.0~beta3 ?
upstream-2.3.0~beta2 ?
2.3.0-1              ?
2.3.0-3              ?
2.3.0-2              ?
2.3.0-5              ?
2.3.0-4              ?
2.5                  ?
...

Why is this?

Bye,
Berny

Re: Sorting tags

On 1/02/12 10:03 PM, John Arbash Meinel wrote:
> On 2/1/2012 11:46 AM, Brendan Simon (eTRIX) wrote:
>> My 'bzr tags' command produces the following:
>>
>> v5.6.14 251 v5.6.14-rc1 246 v5.6.14-rc2
>> 250 v5.7.0 301 v5.7.0-dev1 257 v5.7.0-dev2
>> 259 v5.7.0-dev3 264 v5.7.0-dev4 280 v5.7.0-rc1
>> 281 v5.7.0-rc2 300
>>
>>
>> Note that the release candidates (-rc*) and dev builds (-dev*) are
>> displayed earlier than the final releases.
>>
>> I want to display in revision order. Is there a way to get bzr
>> tags to display in chronological revision order ??
>>
>> v5.6.14-rc1 246 v5.6.14-rc2 250 v5.6.14
>> 251 v5.7.0-dev1 257 v5.7.0-dev2 259 v5.7.0-dev3
>> 264 v5.7.0-dev4 280 v5.7.0-rc1 281 v5.7.0-rc2
>> 300 v5.7.0 301
>>
>>
>> The help (bzr tags --help) wasn't that helpful for the sort
>> arguments :( Note: using bzr 2.4.2.
>>
>> Thanks, Brendan.
>>
>
> bzr tags --sort=time
>
> tag_sort_methods = Registry()
> tag_sort_methods.register("natural", sort_natural,
> 'Sort numeric substrings as numbers. (default)')
> tag_sort_methods.register("alpha", sort_alpha, 'Sort tags
> lexicographically.')
> tag_sort_methods.register("time", sort_time, 'Sort tags chronologically.')
> tag_sort_methods.default_key = "natural"

Thanks.  So ideally the help for bzr tags should show the available sort args (natural, alpha, time), and/or pointers on how to discover any custom sort methods (or be able to display info on the custom sort methods)

Re: Sorting tags

On Wed, Feb 01, 2012 at 12:12:51PM +0100, Voelker, Bernhard wrote:
> John Arbash Meinel wrote:
> 
> > bzr tags --sort=time
> 
> Interesting - bzr.dev seems to have some unnumbered tags:
> 
> ...
> bzr-2.4.2            6015.45.1
> bzr-2.5b3            6252.1.1
> bzr-2.5b4            6349.1.1
> bzr-2.5b5            6437.2.2
> upstream-2.3.0~beta1 ?
> upstream-2.3.0~beta3 ?
> upstream-2.3.0~beta2 ?
> 2.3.0-1              ?
> 2.3.0-3              ?
> 2.3.0-2              ?
> 2.3.0-5              ?
> 2.3.0-4              ?
> 2.5                  ?
> ...
> Why is this?
These are tags that are set on revisions that are not in the branch
history - and thus they have no revision number.

In this particular case, these are tags that are relevant
from the Debian packaging. I'm not sure how they made it into bzr.dev.

Cheers,

Jelmer

Re: Sorting tags

On 2/1/2012 12:24 PM, Jelmer Vernooij wrote:
> On Wed, Feb 01, 2012 at 12:12:51PM +0100, Voelker, Bernhard wrote:
>> John Arbash Meinel wrote:
>> 
>>> bzr tags --sort=time
>> 
>> Interesting - bzr.dev seems to have some unnumbered tags:
>> 
>> ... bzr-2.4.2            6015.45.1 bzr-2.5b3            6252.1.1 
>> bzr-2.5b4            6349.1.1 bzr-2.5b5            6437.2.2 
>> upstream-2.3.0~beta1 ? upstream-2.3.0~beta3 ? 
>> upstream-2.3.0~beta2 ? 2.3.0-1              ? 2.3.0-3
>> ? 2.3.0-2              ? 2.3.0-5              ? 2.3.0-4
>> ? 2.5                  ? ... Why is this?
> These are tags that are set on revisions that are not in the
> branch history - and thus they have no revision number.
> 
> In this particular case, these are tags that are relevant from the
> Debian packaging. I'm not sure how they made it into bzr.dev.
> 
> Cheers,
> 
> Jelmer

Some of the really old ones were because back in the 0.? days we
weren't merging the release branches back to trunk, which we then
changed our mind on. I manually added a bunch of them once we started
supporting tags (prior to that I just tracked them manually).

John
=:->

Re: Sorting tags

...

>> bzr tags --sort=time
>> 
>> tag_sort_methods = Registry() 
>> tag_sort_methods.register("natural", sort_natural, 'Sort numeric
>> substrings as numbers. (default)') 
>> tag_sort_methods.register("alpha", sort_alpha, 'Sort tags 
>> lexicographically.') tag_sort_methods.register("time", sort_time,
>> 'Sort tags chronologically.') tag_sort_methods.default_key =
>> "natural"
> 
> Thanks.  So ideally the help for bzr tags should show the available
> sort args (natural, alpha, time), and/or pointers on how to
> discover any custom sort methods (or be able to display info on the
> custom sort methods) 
> 
> 

There is already an open bug about 'bzr help' not showing possible
values for RegistryOptions that don't expose the individual values as
flags. I don't remember the number offhand, but that's certainly what
you are hitting.

John
=:->

bzr clean-tree is skipping an unknown directory

I ran ‘bzr clean-tree’ when I had several unknown and unwanted
files in my working tree.  It deleted all of them except one.  Now
this one still appears as ‘unknown’ but clean-tree is not
identifying it or trying to remove it:

  $ bzr st
  unknown:
    battmgr.adb
    build_r11/
    build_r11-small/
    build_r11-small-stack-auto/
    init.c.orig
    old_cc2530_regs.h
    old_compiler_defs.h
    build-1.3/src1/
    build-1.3/src2/
  1 shelf exists. See "bzr shelve --list" for details.
  $ bzr clean-tree
  battmgr.adb
  build_r11
  build_r11-small
  build_r11-small-stack-auto
  init.c.orig
  old_cc2530_regs.h
  old_compiler_defs.h
  build-1.3/src2
  Are you sure you wish to delete these [y/N]?y
  deleting paths:
    battmgr.adb
    init.c.orig
    old_cc2530_regs.h
    old_compiler_defs.h
  $ bzr st
  unknown:
    build-1.3/src1/
  1 shelf exists. See "bzr shelve --list" for details.
  $ bzr clean-tree
  Nothing to delete.
  $ bzr st
  unknown:
    build-1.3/src1/
  1 shelf exists. See "bzr shelve --list" for details.
  $ bzr clean-tree --unknown
  Nothing to delete.
  $ bzr st
  unknown:
    build-1.3/src1/
  1 shelf exists. See "bzr shelve --list" for details.
  $ bzr unknowns
  build-1.3/src1
  $ 
  $ bzr version
  Bazaar (bzr) 2.4.1
    Python interpreter: /usr/bin/python 2.7.2
    Python standard library: /usr/lib/python2.7
    Platform: Linux-3.0.0-15-generic-x86_64-with-Ubuntu-11.10-oneiric
    bzrlib: /usr/lib/python2.7/dist-packages/bzrlib
    Bazaar configuration: /home/cdb/.bazaar
    Bazaar log file: /home/cdb/.bzr.log
  ...

What's going on?
The clean-tree operation found and removed the ‘build-1.3/src2’
directory but is not seeing ‘build-1.3/src1’!!

The directory has no special mode or anything.

Regards,
Colin

Re: bzr clean-tree is skipping an unknown directory

Colin D Bennett пишет:
> 
> What's going on?
> The clean-tree operation found and removed the ‘build-1.3/src2’
> directory but is not seeing ‘build-1.3/src1’!!
> 
> The directory has no special mode or anything.

Perhaps this directory has branch inside. What's `bzr info` in that 
directory says?