[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-gnu-arch] [bug #5634] tla what-changed output is in a funny order

From: nobody
Subject: [Bug-gnu-arch] [bug #5634] tla what-changed output is in a funny order
Date: Tue, 25 Nov 2003 18:02:43 -0500
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031120 Firebird/0.6.1 StumbleUpon/1.76

=================== BUG #5634: LATEST MODIFICATIONS ==================

Changes by: Robert Collins <address@hidden>
Date: Tue 11/25/2003 at 23:02 (GMT)

            What     | Removed                   | Added
          Resolution | None                      | Invalid
              Status | Open                      | Declined

=================== BUG #5634: FULL BUG SNAPSHOT ===================

Submitted by: miles                   Project: GNU arch -- a revision control 
Submitted on: Tue 09/30/2003 at 07:47
Category:  tla                        Severity:  5 - Major                  
Bug Group:  bug                       Resolution:  Invalid                  
Status:  Declined                     Release:                              
Fixed Release:                        Merge Request?:  None                 
Your Archive Name:                    Your Archive Location:                
Assigned to:  None                    

Summary:  tla what-changed output is in a funny order

Original Submission:  

Follow-up Comments

Date: Sat 11/08/2003 at 11:54       By: robertc
I wouldn't classify this as major. To address it we'd need to do id comparisons 
and rename detection before altered file detection. You might care to look into 
that if you've got this being altered as a priority ;].

Date: Sun 10/12/2003 at 14:07       By: miles
Actually I was wrong in my description -- commit uses the `wrong' order too, 
only replay (&c) get it right.

Date: Tue 09/30/2003 at 07:53       By: miles
[damn crappy bug-submission UI...]

When you do `tla what-changed', the resulting changeset report shows renames 
_after_ any modifications to the same files -- but the names under which the 
modifications are listed are the _new_ names.  This is confusing; one tends to 
read the output as if it were a recipe describing what's going to happen (even 
if it isn't exactly that), and seeing renamed files referenced before they're 
renamed is weird.

Commit (and replay) on the other hand, show the correct thing, renames before 

CC List

CC Address                          | Comment
address@hidden             | 

No files currently attached

For detailed info, follow this link:

  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]