oship-dev team mailing list archive
-
oship-dev team
-
Mailing list archive
-
Message #00865
Re: [Branch ~oship-dev/oship/main] Rev 368: Commented out line 42 in extract.py -- Eduardo to fix.
There is something still flawed with our workflow:
yesterday I received mail from launchpad that revno 366 was committed
and/or made public.
[Oship-dev] [Branch ~oship-dev/oship/main] Rev 366: Created EhrAccess
class and added tests for it. Created the security file.
Today, again a mail was received from launchpad wrt revno 366:
[Oship-dev] [Branch ~oship-dev/oship/main] Rev 366: updated documentation
And another 7 commits were sent via e-mail the last 24 hours, that are
going to have duplicate revision numbers (at least in the first part
of the subject line of the e-mails). Now their revision numbers are
renamed to 365.1.1 to 365.1.8.
Either I should not have received those messages (keeping the branch
private or the like?) or I should receive them with other branch
names/nicks/descriptions.
Or is this a launchpad/bzr bug?
I find this very confusing.
Cheers anyway,
Roger
2010/1/4 Eduardo César <xcesar@xxxxxxxxx>:
>
>> I can answer some questions but this would be a good topic for you to
>> bring to the mailing list. It will likely help others.
>>
>> Studying alone is a slow process.
>
> Well, in the specs of extraction module, the attribute "extract_request" of
> the ExtractRequest class has a schema of EXTRACT_REQUEST. I searched in the
> docs if it already exists, but it seems to not. I guess I will have to
> define one, but I dont know yet what EXTRACT_REQUEST means and how it is
> constructed.
>
> Cheers
> Eduardo
>
> _______________________________________________
> Mailing list: https://launchpad.net/~oship-dev
> Post to : oship-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~oship-dev
> More help : https://help.launchpad.net/ListHelp
>
>
Follow ups
References