From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: dccp@vger.kernel.org
Subject: Re: [PATCH 2/4] CCID4: Provides organization to the initial
Date: Fri, 21 Sep 2007 14:28:24 +0000 [thread overview]
Message-ID: <20070921142824.GA10051@ghostprotocols.net> (raw)
In-Reply-To: <5bc4c4570709201054n1beda2d8x6bfdcda0cbcbaa35@mail.gmail.com>
Em Fri, Sep 21, 2007 at 05:02:40PM +0300, Tommi Saviranta escreveu:
> On Thu, Sep 20, 2007 at 14:54:32 -0300, ツ Leandro Sales wrote:
> > diff -uprN dccp-ccid4.base/net/dccp/ccids/Makefile
> > dccp-ccid4/net/dccp/ccids/Makefile
> > --- dccp-ccid4.base/net/dccp/ccids/Makefile 2007-09-20 11:45:30.000000000 -0300
> > +++ dccp-ccid4/net/dccp/ccids/Makefile 2007-09-20 11:55:23.000000000 -0300
>
> Signed-off-by: Tommi Saviranta <wnd@iki.fi>
>
> By the way one more question about acking/signing patches. When talking
> about trivial patches such as this, is there a consensus on if simple
> patches need to be (or should be) acked or signed in the first place?
>
> Personally I was a little reluctant to sign this one, but signed it
> anyway as requested.
It is always good to show that you agree with the change, read
Documentation/SubmittingPatches to get more food for thought.
I'll try to harvest the signatures when I get to review/merge the
patches.
And keep up the good work, I'm really happy with how healthy the DCCP on
Linux developer community is getting, thank you all!
- Arnaldo
next prev parent reply other threads:[~2007-09-21 14:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 17:54 [PATCH 2/4] CCID4: Provides organization to the initial entries for CCID 4 to net/dccp/ccids/Makefil
2007-09-21 14:02 ` [PATCH 2/4] CCID4: Provides organization to the initial Tommi Saviranta
2007-09-21 14:28 ` Arnaldo Carvalho de Melo [this message]
2007-09-21 19:47 ` [PATCH 2/4] CCID4: Provides organization to the initial entries for CCID 4 to net/dccp/ccids/Mak
2007-09-21 19:49 `
2007-09-22 20:06 ` Ian McDonald
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=20070921142824.GA10051@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=dccp@vger.kernel.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.