From: "Aurélien Aptel" <aaptel-IBi9RG/b67k@public.gmane.org>
To: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-cifs <linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
samba-technical
<samba-technical-w/Ol4Ecudpl8XjKLYN78aQ@public.gmane.org>
Subject: Re: smbcmp: new tool to compare SMB traces
Date: Wed, 01 Feb 2017 11:37:29 +0100 [thread overview]
Message-ID: <mpsh94ejixi.fsf@aaptelpc.suse.de> (raw)
In-Reply-To: <CAH2r5mtox_==O1oWq1wik6_wgZ7o56JVNZ_wXcxx87fE79xsHA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi Steve,
Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> This is a great idea - why don't we merge this into Samba git tree, so
> it can be packaged in one of the client/tools rpms?
I think it makes more sense to have a separate repo. I don't like to do
the dance where I'm working on commit X but want the tool in the same
tree at its latest version.
We have a package for openSUSE here [1], it should be simple to adapt
for other distros.
1: https://build.opensuse.org/package/show/home:dmulder/smbcmp
--
Aurélien Aptel / SUSE Labs Samba Team
GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3
SUSE Linux GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2017-02-01 10:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 13:13 smbcmp: new tool to compare SMB traces Aurélien Aptel
[not found] ` <mpspoj3jrtv.fsf-zpEvHKhluMwYitT5tn2FcQ@public.gmane.org>
2017-01-31 15:14 ` Steve French
[not found] ` <CAH2r5mtox_==O1oWq1wik6_wgZ7o56JVNZ_wXcxx87fE79xsHA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-02-01 10:37 ` Aurélien Aptel [this message]
2017-02-01 10:03 ` Sachin Prabhu
[not found] ` <1485943434.11784.23.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-02-01 10:39 ` Aurélien Aptel
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=mpsh94ejixi.fsf@aaptelpc.suse.de \
--to=aaptel-ibi9rg/b67k@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=samba-technical-w/Ol4Ecudpl8XjKLYN78aQ@public.gmane.org \
--cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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;
as well as URLs for NNTP newsgroup(s).