Hello, I have also tried to do couple "first bugs" and failed to send them in using Larsen cheat sheet. He tried to help me twice, but no luck.
It just takes longer to send in patches then it is to deal with a bug. Unleast for us on Windows. I do it in my own time, as do you, so I dont have too much time to waste.
I would recomend a youtube tutorial to get started, I think its easiest to select an easy bug and record sending proccess. Windows setup would be great, but I can manage in Linux as virtual machine.
Poslano s mog Windows Phonea ________________________________ Šalje: Larsenmailto:larsen007@web.de Poslano: 11.1.2016. 21:40 Prima: development@lists.ipfire.orgmailto:development@lists.ipfire.org Predmet: Re: Sending in patches
On Sun, 10 Jan 2016 22:54:26 +0100, Michael Tremer michael.tremer@ipfire.org 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). 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).
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. Discussion can take place with that merge request.
In case you are open to using other tools in place of Patchwork, what about Gitlab?
Lars
Hi,
thanks for your input.
How to use Git on Windows? I suppose there is no (good) command line. Are there graphical tools that support sending emails?
-Michael
On Mon, 2016-01-11 at 21:55 +0100, Blago Culjak wrote:
Hello, I have also tried to do couple "first bugs" and failed to send them in using Larsen cheat sheet. He tried to help me twice, but no luck.
It just takes longer to send in patches then it is to deal with a bug. Unleast for us on Windows. I do it in my own time, as do you, so I dont have too much time to waste.
I would recomend a youtube tutorial to get started, I think its easiest to select an easy bug and record sending proccess. Windows setup would be great, but I can manage in Linux as virtual machine.
Poslano s mog Windows Phonea Šalje: Larsen Poslano: 11.1.2016. 21:40 Prima: development@lists.ipfire.org Predmet: Re: Sending in patches
On Sun, 10 Jan 2016 22:54:26 +0100, Michael Tremer michael.tremer@ipfire.org 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). 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).
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.
Discussion can take place with that merge request.
In case you are open to using other tools in place of Patchwork, what
about Gitlab?
Lars
Hi,
I'm using TortoiseGiton win7 as well, this Tool has a send email function,
https://tortoisegit.org/docs/tortoisegit/tgit-dug-settings.html#tgit-dug-set...
but I can't use it because I can't setup the sender from email address which is mandatory for GMX. So I use Thunderbird as well and even with line-warp disabled it still wrap it sometimes.
Aside form GitHub and GitLab, there is also Gogs which is more light-wight than GitLab, Open Source and under MIT License.
-Kim
Am 13.01.2016 um 00:51 schrieb Michael Tremer:
Hi,
thanks for your input.
How to use Git on Windows? I suppose there is no (good) command line. Are there graphical tools that support sending emails?
-Michael
On Mon, 2016-01-11 at 21:55 +0100, Blago Culjak wrote:
Hello, I have also tried to do couple "first bugs" and failed to send them in using Larsen cheat sheet. He tried to help me twice, but no luck.
It just takes longer to send in patches then it is to deal with a bug. Unleast for us on Windows. I do it in my own time, as do you, so I dont have too much time to waste.
I would recomend a youtube tutorial to get started, I think its easiest to select an easy bug and record sending proccess. Windows setup would be great, but I can manage in Linux as virtual machine.
Poslano s mog Windows Phonea Šalje: Larsen Poslano: 11.1.2016. 21:40 Prima: development@lists.ipfire.org Predmet: Re: Sending in patches
On Sun, 10 Jan 2016 22:54:26 +0100, Michael Tremer michael.tremer@ipfire.org 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). 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).
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.
Discussion can take place with that merge request.
In case you are open to using other tools in place of Patchwork, what
about Gitlab?
Lars
Hi,
On Wed, 2016-01-13 at 05:39 +0100, Xaver4all wrote:
Hi,
I'm using TortoiseGiton win7 as well, this Tool has a send email function,
https://tortoisegit.org/docs/tortoisegit/tgit-dug-settings.html#tgit- dug-settings-network-email
but I can't use it because I can't setup the sender from email address which is mandatory for GMX.
Have you ever tried to use something else than GMX?
So I use Thunderbird as well and even with line-warp disabled it still wrap it sometimes.
Or file a bug report at Thunderbird?
Aside form GitHub and GitLab, there is also Gogs which is more light -wight than GitLab, Open Source and under MIT License.
-Kim
Am 13.01.2016 um 00:51 schrieb Michael Tremer:
Hi,
thanks for your input.
How to use Git on Windows? I suppose there is no (good) command line. Are there graphical tools that support sending emails?
-Michael
On Mon, 2016-01-11 at 21:55 +0100, Blago Culjak wrote:
Hello, I have also tried to do couple "first bugs" and failed to send them in using Larsen cheat sheet. He tried to help me twice, but no luck.
It just takes longer to send in patches then it is to deal with a bug. Unleast for us on Windows. I do it in my own time, as do you, so I dont have too much time to waste.
I would recomend a youtube tutorial to get started, I think its easiest to select an easy bug and record sending proccess. Windows setup would be great, but I can manage in Linux as virtual machine.
Poslano s mog Windows Phonea Šalje: Larsen Poslano: 11.1.2016. 21:40 Prima: development@lists.ipfire.org Predmet: Re: Sending in patches
On Sun, 10 Jan 2016 22:54:26 +0100, Michael Tremer michael.tremer@ipfire.org 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). 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).
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.
Discussion can take place with that merge request.
In case you are open to using other tools in place of Patchwork, what
about Gitlab?
Lars
-
Blago Culjak -
Michael Tremer -
Xaver4all