Git-subrepo: pull creates commit despite repo being up to date

[phest]

Steps:

• $ git subrepo pull my/subrepo ---> Subrepo 'my/subrepo' is up to date.
• git commit some local change inside my/subrepo
• $ git subrepo push my/subrepo ---> Subrepo 'my/subrepo' pushed to '<URL>' (<branch>)
• $ git subrepo pull my/subrepo ---> Subrepo 'my/subrepo' pulled from '<URL>' (<branch>) (This pull doesn't bring new changes from the remote, but it creates a commit with the subject "git subrepo pull my/subrepo")

Ideally, the last pull in this example should result in Subrepo 'my/subrepo' is up to date. Currently, it creates a commit despite not bringing new history from the remote.

[VincentClair]

+1

[grimmySwe]

Version 0.3.0 and previous behaves that way. Reason for that is that
.gitrepo file is not updated.

In #142 this is discussed and will hopefully be solved in an upcoming
release.

onsdag 13 juli 2016 skrev Vincent Clair [email protected]:

+1

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ingydotnet/git-subrepo/issues/205#issuecomment-232385108,
or mute the thread
https://github.com/notifications/unsubscribe/AGLignMYeZFXbH92bYGQSXZpgzy2Klxzks5qVP8sgaJpZM4JLGIA
.

[grimmySwe]

@phest Could you please test issue/216 branch and see if that solves your problem?

[bilougit]

@grimmySwe I'm having the same problem and this fixes it :+1:

When is this going to be released?

[grimmySwe]

@bilougit I wish I could give you a date, we are trying to review the changes and see that we don't miss anything. You can use release/0.4.0 branch to see for yourself and see if there are any problems.

[ingydotnet]

@grimmySwe I'd like to make an effort to try to get the release mess solved by the end of this month.