[Ksummit-discuss] [CORE TOPIC] Recruitment (Reviewers, Testers, Maintainers, Hobbyists)

[Geert Uytterhoeven]

On Mon, Jul 13, 2015 at 12:00 AM, Laurent Pinchart
<laurent.pinchart at ideasonboard.com> wrote:
> On Friday 10 July 2015 21:00:12 David Woodhouse wrote:
>> On Fri, 2015-07-10 at 15:51 -0400, Steven Rostedt wrote:
>> > On Thu, 9 Jul 2015 19:07:06 -0700 Darren Hart wrote:
>> > > As far as recruitment goes, I think we're talking about barriers to
>> > > first-timers and such - and git-send-email is one of those things.
>> > > Eventually, a developer>
>> > +1000
>> >
>> > I still don't use git-send-email, as I afraid that I'll blow it and end
>> > up sending a thousand patches to every developer that ever touched the
>> > kernel ;-)
>>
>> Rather than sending messages, it's actually better to put them as
>> *drafts*, ready to be sent by the user's normal mailer. It's not hard
>> to do this — I usually dump the mails into
>> ~/.local/share/evolution/mail/local/.Drafts/new/ for example.
>>
>> And then I can *read* them before sending them, which is good practice
>> anyway. Am I the only person who often finds a final minor nit with
>> their own patch, in that final read-through just before hitting 'send'
>> on an email?
>
> Certainly not, but what prevents you from doing that with git-send-email ? In
> my workflow I always format patches with git-format-patch, proof-read them
> with my favourite $EDITOR and then use git-send-email to send them.

Apparently some people think you should feed a rev-list to git-send-email
(a feature I learned about only recently), instead of patches created by
git-format-patch. As you need the patches for checkpatch.pl anyway...

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds