[
https://issues.apache.org/jira/browse/MYNEWT-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900428#comment-15900428
]
ASF subversion and git services commented on MYNEWT-495:
--------------------------------------------------------
Commit a7c0235607ab10427aab02f7631e1a451cf889cc in incubator-mynewt-newt's
branch refs/heads/1_0_0_dev from [~utzig]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-newt.git;h=a7c0235
]
MYNEWT-495: updates to sync command
- When repo is already cloned, try to update from remote
- If -f is passed, create a modifications diff, and try harder
to update current local (stash, clean, checkout, pull)
> newt sync needs a refactor
> --------------------------
>
> Key: MYNEWT-495
> URL: https://issues.apache.org/jira/browse/MYNEWT-495
> Project: Mynewt
> Issue Type: Improvement
> Affects Versions: v1_0_0_beta1
> Reporter: Sterling Hughes
> Assignee: Fabio Utzig
> Fix For: v1_0_0_rel
>
>
> newt sync currently deletes and resynchronizes the repository.
> It's behaviour needs a review, minimally I think it should:
> - go to the repositories its synching
> - detect whether or not there are any local changes
> - if so, goto #a
> - if not, git pull the latest changes
> #a
> - check if -f (force) flag is present, if not, abort and print error message
> - if -f is present, then it should stash the changes and save a diff, and
> then pull the latest from the remote repo (and print notice messages.)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
