Hello all,
Thank you for all your contributions to X2Go code. However, sometimes it is not easy to test and apply patches, that you send us via a developer mailing list. To make this procedure for us easier, please create your patches like it described in the GIT documentation:
http://www.git-scm.com/book/en/Distributed-Git-Contributing-to-a-Project#Pub...
@Mike: What do you think about it? Should we include this link in our Wiki-Documentation?
regards, Alex
Oleksandr Shneyder | Email: o.shneyder@phoca-gmbh.de phoca GmbH | Tel. : 0911 - 14870374 0 Ludwig-Feuerbach-str. 18 | Fax. : 0911 - 14870374 9 D-90489 Nürnberg | Mobil: 0163 - 49 64 461
Geschäftsführung: Dipl.-Inf. Oleksandr Shneyder
Amtsgericht München | http://www.phoca-gmbh.de HRB 196 658 | http://www.x2go.org USt-IdNr.: DE281977973
Hi Alex,
On Mi 05 Mär 2014 11:49:02 CET, Oleksandr Shneyder wrote:
Yes, please do add it to this page [1]. Patches should always be sent
via our bug tracker!!!
Mike
[1] http://wiki.x2go.org/doku.php/wiki:bugs#bug_submission_with_a_patch
--
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Hi Alex,
On Mi 05 Mär 2014 11:49:02 CET, Oleksandr Shneyder wrote:
One more feedback on the above article.
Best practice for applying patches (for me at least) is if
contributors attach patches to mails as an attachment (or several
attachments).
Patches sent inline (as recommended by the howto linked above) are
much harder to handle (at least for me, my mail client, my workflows).
Thanks+Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
-
Mike Gabriel -
Oleksandr Shneyder