From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Sending in patches Date: Fri, 15 Jan 2016 01:25:43 +0000 Message-ID: <1452821143.5665.79.camel@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8875770234616862209==" List-Id: --===============8875770234616862209== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hi, so about half a week has passed since my initial email. I suppose this is all that is coming and that the others are perfectly satisfied with this process. So let's conclude: On Mon, 2016-01-11 at 21:40 +0100, Larsen wrote: > On Sun, 10 Jan 2016 22:54:26 +0100, Michael Tremer > wrote: > > > I find this process with "git send-email" very easy and I am > > not sure where the problems could be. > > I am using TortoiseGit with Windows 7. I don't know if this tool > supports > "git send-email" and I wouldn't want to use command line git (it is > annoying to use more than one tool for the same job, IMHO). I didn't know that this many people use Windows. The problem with that is you cannot build the distribution. You can copy some files back and forth, but never build. I consider this to be a huge disadvantage. Is this just by choice or did you not want to go through the trouble setting up a Linux system? > Therefore, I > create a patch file using TortoiseGit (I need a workflow reminder for > this > to get it right), then send the contents with Thunderbird where I > have to > remember to disable line wrap (also using a workflow reminder text). When ever you make personal notes, why not use the wiki for that and share? Many other people might have the same questions. > In other projects (using Github), IMHO it is much easier to push to > one's > own repository and create a merge request to the upstream repository. We can't use GitHub. I have explained that at various occasions and this thread wasn't started to discuss other tools. Other things have been proposed, too, and the same goes for them. At the end the only problem I understand you are experiencing here is actually emailing the patch files without your mail agents not making garbage out of that. This can't be too hard to get right. > Discussion can take place with that merge request. No, not at all. This process is actually well thought through and designed to maximise participation of the users and make everything easy for developers. And I actually think it does that well. > In case you are open to using other tools in place of Patchwork, what > > about Gitlab? Patchwork is just a view to the patches. My actual repository for that is my inbox. > > > Lars -Michael --===============8875770234616862209== Content-Type: application/pgp-signature Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="signature.asc" MIME-Version: 1.0 LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KVmVyc2lvbjogR251UEcgdjEKCmlRSWNCQUFC Q2dBR0JRSldtRXFYQUFvSkVJQjU4UDl2a0FrSDNJRVAvMXFNQmlmNnI0b05wN1AwUERiU3NkNlIK RUg0TGFyT2NFbDZldzBxQTBZY3ZNbXVhOVJIVStySDRqZ1d1TVdOeTgzUUpEWjhiam5IZUR6VjU5 eXZKMllaNQp5TkVVNXJTSzR3K3RXTnVISTk0SS9ubTh3dk16eWVzR1hrcEhHSWU0cVJyTTJPekJ4 RXB1Ry9vbXJlbTlKamdTCnViRkpjMllGblJBcHcvOFlmRUwyMkI3RVNJOTJrc1Fsd29JM1h4SjdZ Z1RmYWtlOTBRNUV1YUFxdTBaeG5Od3oKeHBlYUtMbXVJLy82Y052a3ZzZDhreWNoRXg5Sy9kVmI2 NHdwNkNqTTh2ZUNYWFlEMEdTd3NkWlloVVNBTVVNUApFb2dkcWZ5cTFYZVVhc0hwTlZEL0hvQllZ TTFhOTNlbVBQaUxuUXB3d1R4V2VDT0dwRkRxUk0vejlTUFZhdnpCCjdvTFU3VVdlY2hPTysyNUVi M25uTjUvRkkreWM4S1NwUi9yZnBvV2l2NjI2ZzV6enFVamNkZ0YzSlg4K2hrV1QKZmMxaytjZFY0 MU1nM0RIaHJ3VzZOU3B5cUZpNU1rVXYzV3dqa0NEQWg3WXgyMmdaY0k2cmFJdlhiUTJwUHdubAo1 N0dWN1R5MWQvRkY4ZW0rREZjQVYrMERxUy9zSFBCMG0wanNXcWRCT2EveFoweDJGcVhGVi9leVpj cTRaZm9GCklnQzlmVFNJVzk4Sjg4NllDVk5hRklVb25FMWpSYlVyOStFSW9icG5HT2UxS3llQ3NN N3NWZ3dyWFJNeGYwYXgKVU10RFZJTlhtbFJycm5lS3Vvc1lvZGJNSlFxOENlVTBvMklKTnJiUk1I ZUxhMUIrb0FjQ0hrZWhiRUwweEthSgpkb1c1MSsrMlFZMlRwZlFPbUY5UAo9ZnpVLwotLS0tLUVO RCBQR1AgU0lHTkFUVVJFLS0tLS0K --===============8875770234616862209==--