BzrTools

`bzr heads` don't show branches as HEAD if there is children revisions in the shared repository

Bug #375375 reported by Alexander Belchenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
BzrTools
New
Undecided
Unassigned

Bug Description

I have shared repository with several branches. I run `bzr heads` and it show my HEADs right. Then I delete HEAD branch and again run `bzr heads` and now I see nothing. This is confusing behavior.

C:\Temp>bzr init-repo repo

C:\Temp>cd repo
C:\Temp\repo>

C:\Temp\repo>bzr init a

C:\Temp\repo>bzr ci a -m1 --unch
Committing to: C:/Temp/repo/a/
Committed revision 1.

C:\Temp\repo>bzr get a b
Branched 1 revision(s).

C:\Temp\repo>bzr ci a -m2 --unch
Committing to: C:/Temp/repo/a/
Committed revision 2.

C:\Temp\repo>bzr heads
TIP of branch: C:/Temp/repo/a/
HEAD: revision-id: <email address hidden>
  committer: Alexander Belchenko <email address hidden>
  branch nick: a
  timestamp: Tue 2009-05-12 13:45:00 +0300
  message:
    2

C:\Temp\repo>del a

C:\Temp\repo>bzr heads
<nothing here>

Revision history for this message
Aaron Bentley (abentley) wrote : Re: [Bug 375375] [NEW] `bzr heads` don't show branches as HEAD if there is children revisions in the shared repository

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alexander Belchenko wrote:
> Public bug reported:
>
> I have shared repository with several branches. I run `bzr heads` and it
> show my HEADs right. Then I delete HEAD branch and again run `bzr heads`
> and now I see nothing. This is confusing behavior.

I'm pretty sure that's how you designed it to work.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkoJZ70ACgkQ0F+nu1YWqI1eOACeKX/HkssMW0Jhjfk8xmRmY30f
gbMAnAp5XWVOefiTW0Bi8/s5D8j1O8D2
=hD0h
-----END PGP SIGNATURE-----

Revision history for this message
Alexander Belchenko (bialix) wrote :

I'd say "this is how I implemented it", not as "how I designed it".
I should admit I never realized this scenario.

So my question: do you think current behavior is right? What is your opinion?

Revision history for this message
Aaron Bentley (abentley) wrote : Re: [Bug 375375] Re: `bzr heads` don't show branches as HEAD if there is children revisions in the shared repository

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alexander Belchenko wrote:
> I'd say "this is how I implemented it", not as "how I designed it".
> I should admit I never realized this scenario.
>
> So my question: do you think current behavior is right? What is your
> opinion?

I only ever use --dead-only. --all would be okay as a default, but if
- --dead-only is the most common, maybe it should be the default.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkoJcAYACgkQ0F+nu1YWqI089ACeMAQQHux83861MRQzWIhRiS4M
nCwAnjS2Hp232bUwdKAi7jOdRwm8DXfg
=u7dV
-----END PGP SIGNATURE-----

Revision history for this message
Jelmer Vernooij (jelmer) wrote :

I also never use the current default, only "bzr heads --dead-only" and "bzr heads --all". I think it would be a good idea to change the default.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.