|
logilab-devtools #6511 trouble with outgoing changesets [resolved]outgoing changesets return a bad result in vcs_agent.not_up_to_date()
| | priority | normal |
|---|
| type | bug |
|---|
| appeared in | <not specified> |
|---|
| done in | 0.17.0 |
|---|
| load | 0.200 |
|---|
| load left | 0.000 |
|---|
| closed by | <not specified> |
|---|
Workflow history| from state (3) | to state | comment | date | User |
| validation pending | resolved | | 2010/10/13 23:55 | sthenault |
| done | validation pending |
version published
| 2010/06/04 17:48 | |
| open | done | filtering outgoing changeset are done in lgp instead
| 2010/05/17 15:57 | |
| |
|
Comments
-
2009/03/03 15:13 | reply to this comment
-
2009/03/03 18:09 | reply to this comment
-
2009/04/23 10:30, written by sthenault
| reply to this comment
-
2009/04/23 11:00, written by anon
| reply to this comment
(add comment)Is this one identical to 2884?
Not a all.
vcs_agent.not_up_to_date() returns incoming/outgoing changesets as well. Maybe we can consider it as an error.
syt ?
I don't understand what the problem is.
Not really a problem for me.. vcs_agent.not_up_to_date() returns non-empty result where we can have different behaviour with other SCMs (non distributed especially). Feel free to close the ticket..