bugArX revision control system - Bugs: bug #4797, new-on-branch

 
 

bug #4797: new-on-branch

Submitted by:  Walter Landry <landry>
Submitted on:  Sun 17 Aug 2003 03:15:21 AM UTC  
 
Severity: 3 - LowItem Group: None
Status: Wont FixPrivacy: Public
Assigned to: NoneOpen/Closed: Closed

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Tue 12 Oct 2004 04:38:25 AM UTC, comment #1:

new-on-branch doesn't exist anymore.

Walter Landry <landry>
Project Administrator
Sun 17 Aug 2003 03:15:21 AM UTC, original submission:

-unavailable- (Alexander Deruwe) wrote:

> Hey all. Some questions about 'new-on-branch'...
>
> Assumption: after I replay exactly 1 patch from another branch in my
> working directory (without previous changes), 'new-on-branch' should
> show just that patch.
>
> How come 'new-on-branch' does not do that? ;) Am I missing its point?
> When I run 'new-on-branch' in my aderuwe-landry branch, I'm even getting
> arch--geisler--1.0 and arch--devo--1.0 mentionings.
>
>
> User error or feature? Please enlighten me. ;)


As far as I can tell, it is either a misapplication of merge-points,
or a bug in merge-points. new-on-branch uses merge-points to tell
what has already been merged into the tree. But that only includes
direct merges into the current tree, not third party merges into a
tree that was subsequently merged in.

But new-on-branch uses "logs" piped to "log-ls" to find out what has
already been applied, which will include all the third party stuff.

I think the way to fix it is to look at merge-points of merged trees.
For example, merge-points of the dists--landry--1.0 gives me

base-0 lord@regexps.com--2002/dists--devo--1.0--patch-36

Now what new-on-branch should do is look at the merge-points of
dists--devo--1.0. Unfortunately, that seems to require the network to
complete.

So I don't know what the right thing is to do here.

Walter

There is a note in the =TODO (I think), that talks about
memoizing the previous revision history when making a
continuation. It would make branches more complicated, and
there would have to be some way of getting rid of old ones
that you don't care about. Even so, it might be the right
answer.

Walter Landry <landry>
Project Administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

Do you think this task is very important?
If so, you can click here to add your encouragement to it.
This task has 0 encouragements so far.

Only logged-in users can vote.

 

Please enter the title of George Orwell's famous dystopian book (it's a date):

 

 

Follow 2 latest changes.

Date Changed By Updated Field Previous Value => Replaced By
Tue 12 Oct 2004 04:38:25 AM UTClandryStatusNone=>Wont Fix
  Open/ClosedOpen=>Closed

Back to the top


Powered by Savane 3.1-cleanup1