From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] samba: Update to 4.5.0
Date: Thu, 08 Sep 2016 12:46:30 +0100 [thread overview]
Message-ID: <1473335190.2757.62.camel@ipfire.org> (raw)
In-Reply-To: <1473312917-24469-1-git-send-email-alexander.marx@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1803 bytes --]
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(a)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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-09-08 11:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 5:35 Alexander Marx
2016-09-08 11:46 ` Michael Tremer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1473335190.2757.62.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox