[Kolab-devel] my current patchset
hede
kolab983 at der-he.de
Fri Dec 1 21:02:14 CET 2017
Hi all,
sorry for asking this stupid question; I'm pretty sure I should know the
answer. But what's the currently favoured way to send patches for
review?
In the past I usually uploaded my changes as some home repo to OBS, but
those patches hardly arrived to the upstream repository (some arrived to
OBS, others indeed to the upstream git repo, but others are still
missing at all); on the other hand it seems I'm not allowed to use my
own branch on git/diffusion.
So here we go...
(btw: one half of those patches are not initially made by me - they're
found elsewhere on the net so maybe it's indeed harder to get them
upstream as it should be)
regards
hede
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cyrus-imapd-2.5.11.41_fsigned-char_with_ARM_builds.patch
Type: text/x-diff
Size: 1114 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/devel/attachments/20171201/17cb70c1/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: erlang-3.21.1-fix_readlink_for_relative_path_names.patch
Type: text/x-diff
Size: 1716 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/devel/attachments/20171201/17cb70c1/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: guam-0.9.2-stalling-client-buffer-and-split-command-handling.patch
Type: text/x-diff
Size: 5075 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/devel/attachments/20171201/17cb70c1/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pykolab-0.8.7-tcp_keepalive_in_virtual_containers_T2094.patch
Type: text/x-diff
Size: 2767 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/devel/attachments/20171201/17cb70c1/attachment-0003.bin>
More information about the devel
mailing list