On 07/17/2011 04:00 PM, Pavel Sanda wrote:
John McCabe-Dansted wrote:
Also, is this OK for branch? Should I commit there as well?
for any commit to branch (except to documentation) you need explicit
OK from branch maintainer, ie Richard.
And the usual method is to reply to the commit
Am 17.07.2011 14:47, schrieb John McCabe-Dansted:
I have finally exercised my commit privileges by committing r39333.
Welcome on board!
regards Uwe
On 07/17/2011 04:00 PM, Pavel Sanda wrote:
> John McCabe-Dansted wrote:
>
>> Also, is this OK for branch? Should I commit there as well?
> for any commit to branch (except to documentation) you need explicit
> OK from branch maintainer, ie Richard.
>
And the usual method is to reply to the commit
Am 17.07.2011 14:47, schrieb John McCabe-Dansted:
I have finally exercised my commit privileges by committing r39333.
Welcome on board!
regards Uwe
I have finally exercised my commit privileges by committing r39333. I
spent an hours checking everything is OK, but this is my first commit
ever to a shared VCS... so expect a rain of fire.
Also, is this OK for branch? Should I commit there as well?
If so, to do that I just check out branch,
John McCabe-Dansted wrote:
I have finally exercised my commit privileges by committing r39333. I
spent an hours checking everything is OK, but this is my first commit
ever to a shared VCS... so expect a rain of fire.
everything seems fine.
Also, is this OK for branch? Should I commit there
I have finally exercised my commit privileges by committing r39333. I
spent an hours checking everything is OK, but this is my first commit
ever to a shared VCS... so expect a rain of fire.
Also, is this OK for branch? Should I commit there as well?
If so, to do that I just check out branch,
John McCabe-Dansted wrote:
> I have finally exercised my commit privileges by committing r39333. I
> spent an hours checking everything is OK, but this is my first commit
> ever to a shared VCS... so expect a rain of fire.
everything seems fine.
> Also, is this OK for branch? Should I commit