From: Adrian Bunk <bunk@stusta.de>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Markus Dahms <dahms@fh-brandenburg.de>
Subject: Re: remove broken URLs from net drivers' output
Date: Thu, 10 May 2007 06:07:39 +0200 [thread overview]
Message-ID: <20070510040739.GF23574@stusta.de> (raw)
In-Reply-To: <9a8748490705091604l32b0e6depbc079f69897b34e0@mail.gmail.com>
On Thu, May 10, 2007 at 01:04:24AM +0200, Jesper Juhl wrote:
> On 10/05/07, Jeff Garzik <jeff@garzik.org> wrote:
>> Linux Kernel Mailing List wrote:
>> > Gitweb:
>> http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=2c2a8c531e953c753b06605c8ad6a9161ca527fa
>> > Commit: 2c2a8c531e953c753b06605c8ad6a9161ca527fa
>> > Parent: b96687768a9ac0fdd005c7700093ebb24b93450f
>> > Author: Markus Dahms <dahms@fh-brandenburg.de>
>> > AuthorDate: Wed May 9 07:58:10 2007 +0200
>> > Committer: Adrian Bunk <bunk@stusta.de>
>> > CommitDate: Wed May 9 08:58:18 2007 +0200
>> >
>> > remove broken URLs from net drivers' output
>> >
>> > Remove broken URLs (www.scyld.com) from network drivers' logging
>> output.
>> > URLs in comments and other strings are left intact.
>> >
>> > Signed-off-by: Markus Dahms <dahms@fh-brandenburg.de>
>> > Acked-by: Jesper Juhl <jesper.juhl@gmail.com>
>> > Acked-by: Alan Cox <alan@redhat.com>
>> > igned-off-by: Adrian Bunk <bunk@stusta.de>
>> > ---
>> > drivers/net/3c509.c | 5 ++---
>> > drivers/net/3c59x.c | 2 +-
>> > drivers/net/atp.c | 8 +++-----
>> > drivers/net/eepro100.c | 2 +-
>> > drivers/net/epic100.c | 10 ++++------
>> > drivers/net/natsemi.c | 1 -
>> > drivers/net/ne2k-pci.c | 3 +--
>> > drivers/net/sundance.c | 3 +--
>> > drivers/net/yellowfin.c | 1 -
>> > 9 files changed, 13 insertions(+), 22 deletions(-)
>>
>> Grumble... This stuff should go through my tree.
>>
>> Jeff
>>
>
> Note, just for the record; I never explicitly added an Acked-by to
> this patch, I only said in a conversational email that it made sense
> to me...
> I don't actually mind, in this case, to have an Acked-by tagged on
> with my name, but in general I think that such lines should only be
> added when people explicitly say Acked-by: John Doe, or something like
> "Feel free to add my ACK to this" etc.
Did I miss that "Acked-by:" is considered to be a formal tag like
"Signed-off-by:"?
I thought it was just an informal tag to mark which people did agree
with the patch (and the line between your "Makes good sense to me."
and a "Feel free to add my ACK to this" is really thin).
> Jesper Juhl
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-05-10 4:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200705092102.l49L2Re6028694@hera.kernel.org>
2007-05-09 22:41 ` remove broken URLs from net drivers' output Jeff Garzik
2007-05-09 23:04 ` Jesper Juhl
2007-05-10 4:07 ` Adrian Bunk [this message]
2007-05-10 4:22 ` Jeff Garzik
2007-05-10 4:47 ` Adrian Bunk
2007-05-10 9:44 ` Jesper Juhl
2007-05-10 3:57 ` Adrian Bunk
2007-05-10 4:23 ` Jeff Garzik
2007-05-10 4:58 ` Adrian Bunk
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=20070510040739.GF23574@stusta.de \
--to=bunk@stusta.de \
--cc=dahms@fh-brandenburg.de \
--cc=jeff@garzik.org \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.