Remove own declaration of errno

[metux]

branch: 1780_remove_errno_decl
changeset:1780_remove_errno_decl

[slavazanko]

Added commits:

• 4b730c24a0f41b2178e1c5d02d64f220d2f35714: Removing calls of strerror() function in mc-core
• b94fb331c3860004119179a289945ea774cb6db9: Removed calls to strerror() function from own libsamba implementation.

Please remember: own libsamba will dropped in near time (we will use libsmbclient instead)
Therefore no need to much changes in own deprecated code.

[metux]

rebased to current master

[metux]

rebased to current master, running through testfarm

please review

[angel_il]

initial changeset:7e07bf97a126f07a3453f5b02095a61ea0fe92af

[metux]

rebased to current master, now running through testfarm

[slavazanko]

No need to often rebase.

• b3e5c4ca3262e5588a04e49309919483a2dac88c: removing own declaration of errno and strerror()
• 49f5893c15e12465940ca3ed16b75570bbdb6b64: Removing calls of strerror() function in mc-core
• 7393892f2a4037969b7baddfdc4816927f69320f: Removed calls to strerror() function from own libsamba implementation.

I'm made last patch, therefore review please.

[metux]

Replying to slavazanko:

No need to often rebase.

I'm rebasing all my branches when the origin (in this
case master) is updated. the rule is: keep as close
as possible. This prevents later merge conflicts.

As master changed, and there _WAS_ an conflict, i rebased again.

I'm now voting for your commits, you could do it for mine,
(count them together as one) and then wait for another one ...

[slavazanko]

I'm rebasing all my branches when the origin (in this
case master) is updated. the rule is: keep as close
as possible. This prevents later merge conflicts.

Just try:

git checkout master
git merge origin/your_branch
# see if any conflicts present this stage
git reset --hard origin/master

This operation checks if your branch will conflict with master. In this case (and only in this case) you may rebase branch. You may do this check in dedicated script... :)

I'm now voting for your commits, you could do it for mine

In this branch? No, I can't vote. I'm owner of last patch, therefore others will vite for this patch, not I. We always vote to last patch.

and then wait for another one ...

yep, now we wait for another one vote.

[metux]

Replying to slavazanko:

I'm rebasing all my branches when the origin (in this
case master) is updated. the rule is: keep as close
as possible. This prevents later merge conflicts.

Just try:

git checkout master
git merge origin/your_branch
# see if any conflicts present this stage
git reset --hard origin/master

Well, I'm doing contigious integration workflow (running through testfarm once something's changed) to catch errors as soon as possible. So contigious rebasing absolutely makes sense, IMHO.

[metux]

Please review.

[andrew_b]

git log --pretty=oneline e5fdb34..09e2003