Comment #2 on issue 2456 by eyuw...@gmail.com: RB API doesn't allow
updating changenum field for Git
Thanks for your quick response! Yes, I understand RB currently only
supports change number if the backend SCM supports such concept natively.
But wouldn't it be nice if the web service API provides the ability to
update the field? Right now that field always shows 'None' if the
underlying SCM is not Perforce. As an administrator/developer/user, I'd
like to be able to "overload" that field to do meaningful task, such as use
it to store the commit SHA1 string associated with the change, rather than
be wasted? From there, I can do a lot more work build on top of it...
Would you consider providing such functionality in the API? I mean people
who use the API probably know what they are doing, isn't it?
You received this message because you are subscribed to the Google Groups
To post to this group, send email to email@example.com.
To unsubscribe from this group, send email to
For more options, visit this group at