Hi,

technically samba 4 has not been merged into master, yet. So patches on top of the other patches do not make too much sense.

I think that we should in future maintain a branch and apply any changes onto that one until we reach a version that is good enough to merge. Then we should reconsider rebasing that branch on the current master and sending a single squashed patch or a patchset.

In the end this is not a race but we should rather care about quality first.

This patch is good but the three samba patches are now all over the mailing list and harder to track. This statement is also true for many other things and not only samba. Yet this is a good and easy example to illustrate that.

So please consider carefully if something is ready to be sent to the mailing list yet and if a patchset does not make more sense. It helps to make our jobs a bit easier.

Best, -Michael

On Thu, 2016-09-08 at 05:35 +0000, Alexander Marx wrote:

fixes: #11178

• NTLMv1 authentication disabled by default
• Support for LDAP_SERVER_NOTIFICATION_OID
• KCC improvements for sparse network replication
• VLV - Virtual List View
• DRS Replication for the AD DC
• samba-tool drs replicate with new options

Signed-off-by: Alexander Marx alexander.marx@ipfire.org

samba/samba.nm | 2 +-  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/samba/samba.nm b/samba/samba.nm index 9a1ef37..5f033b8 100644 --- a/samba/samba.nm +++ b/samba/samba.nm @@ -4,7 +4,7 @@  ############################################################################# ##    name       = samba -version    = 4.4.0 +version    = 4.5.0  release    = 1    groups     = Networking/Daemons