Modify

Opened 2 years ago

Last modified 2 years ago

#1918 confirmed defect

Branch changes in the thornlist are ignored when updating

Reported by: Ian Hinder Owned by:
Priority: major Milestone:
Component: GetComponents Version: development version
Keywords: Cc:

Description

When updating an existing GetComponents checkout, if the branch has changed in the thornlist, the old branch is checked out, so the result of running GetComponents --update is to ignore the new branch in the thornlist.

Attachments (0)

Change History (1)

comment:1 Changed 2 years ago by Frank Löffler

Status: newconfirmed

The code seems to specifically implement that behavior:

  • It updates all branches that were specified to the 'update' command, plus 'master' (last). The branches that are specified are all branches specified for REPO_BRANCH, delimited by comma.
  • It then switches back to the branch that the repository was at before the update.

In this sense, it does an 'update', not a 'switch to another branch'. Now the question is what we want GetComponents to do when given the command to 'update'.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as confirmed The ticket will remain with no owner.
Next status will be 'review'.
as The resolution will be set.
to The owner will be changed from (none) to the specified user.
The owner will be changed from (none) to anonymous.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.