diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2016-05-13 14:04:22 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2016-05-13 14:04:22 -0400 |
| commit | 527853c9d039a7fb60a0acd6057923cb610a116d (patch) | |
| tree | de35b3e2d1fd6b78c527281700e8df4dd399846a /debian | |
| parent | 316634a2063759c38ad611f57c73c6f6e1fd2a08 (diff) | |
adjust: If the adjusted branch already exists, avoid overwriting it, since it might contain changes that have not yet been propigated to the original branch.
Could not think of a foolproof way to detect if the old adjusted branch was
just behind the current branch. It's possible that the user amended the
adjusting commit at the head of the adjusted branch, for example.
I decided to bail in this situation, instead of just entering the old
branch, so that if git annex adjust succeeds the user is always in a
*current* adjusted branch, not some old and out of date one.
What could perhaps be done is enter the old branch and then update it. But
that seems too magical; the user may have rebased master or something or
may not want to propigate the changes from the old branch. Best to error
out.
Diffstat (limited to 'debian')
| -rw-r--r-- | debian/changelog | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/debian/changelog b/debian/changelog index 1c246ff97..a653efdfd 100644 --- a/debian/changelog +++ b/debian/changelog @@ -3,6 +3,9 @@ git-annex (6.20160512) UNRELEASED; urgency=medium * Change git annex info remote encryption description to use wording closer to what's used in initremote. * webapp: Avoid confusing display of dead remotes. + * adjust: If the adjusted branch already exists, avoid overwriting it, + since it might contain changes that have not yet been propigated to the + original branch. -- Joey Hess <id@joeyh.name> Wed, 11 May 2016 16:08:38 -0400 |