On Wed, Apr 22, 2015 at 12:57 PM, Thiago Farina wrote:
> On Wed, Apr 22, 2015 at 4:50 PM, Stefan Beller wrote:
>> On Wed, Apr 22, 2015 at 12:38 PM, Thiago Farina wrote:
>>> IMO, sending email is the easiest part.
>>>
>>> The hard begins when you have to edit your patch and resend with the
>
On Wed, Apr 22, 2015 at 4:50 PM, Stefan Beller wrote:
> On Wed, Apr 22, 2015 at 12:38 PM, Thiago Farina wrote:
>>>
>> IMO, sending email is the easiest part.
>>
>> The hard begins when you have to edit your patch and resend with the
>> reviewers' feedback incorporated. For me that is the most tri
On Wed, Apr 22, 2015 at 12:38 PM, Thiago Farina wrote:
>>
> IMO, sending email is the easiest part.
>
> The hard begins when you have to edit your patch and resend with the
> reviewers' feedback incorporated. For me that is the most tricky and
> hard part to get right, specially when using GMail a
On Mon, Dec 29, 2014 at 10:22 PM, Stefan Beller wrote:
> Hi,
>
> so I have been sending commits to the git mailing list occasionally
> for quite some time. In the last couple of weeks I send more and more
> patches to the mailing list as it's part of my job now. Here is a
> collection of practices
Hi,
so I have been sending commits to the git mailing list occasionally
for quite some time. In the last couple of weeks I send more and more
patches to the mailing list as it's part of my job now. Here is a
collection of practices I am following (or want to follow) and they
seem to be effective.
5 matches
Mail list logo