From: Julia Lawall <julia@diku.dk>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: Vegard Nossum <vegard.nossum@gmail.com>,
Bryan Wu <cooloney@kernel.org>,
Alexey Dobriyan <adobriyan@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] blackfin/sram: use 'unsigned long' for irqflags
Date: Wed, 6 Aug 2008 14:21:17 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0808061417540.20424@pc-004.diku.dk> (raw)
In-Reply-To: <8bd0f97a0808060514x5c9ed37exbf8f9852b5a0b55d@mail.gmail.com>
> *shrug* ... i dont see other patches with things like:
> The patch was generated with git.
> The patch was generated with eclipse.
> The patch was generated with emacs.
> etc...
>
> we dont generally list all of the tools in the log message that was
> used in *creating* a patch since it doesnt really add any value when
> looking back historically at changes.
But with git, emacs, eclipse etc, the person is still making the change by
hand. The comment is more like "this patch was generated with perl" or
"this patch was generated with sed", indicating that the change is
uniform enough to be automated. This does have some interest,
although perhaps not for everyone.
julia
next prev parent reply other threads:[~2008-08-06 12:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 10:58 Vegard Nossum
2008-08-06 11:05 ` Mike Frysinger
2008-08-06 11:28 ` Vegard Nossum
2008-08-06 12:14 ` Mike Frysinger
2008-08-06 12:17 ` Mike Frysinger
2008-08-06 12:21 ` Julia Lawall [this message]
2008-08-06 12:52 ` Vegard Nossum
2008-08-06 17:34 ` Mike Frysinger
2008-08-22 13:44 ` Mike Frysinger
2008-08-27 6:56 ` Bryan Wu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0808061417540.20424@pc-004.diku.dk \
--to=julia@diku.dk \
--cc=adobriyan@gmail.com \
--cc=cooloney@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vapier.adi@gmail.com \
--cc=vegard.nossum@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®