To: dccp@vger.kernel.org
Subject: Re: Towards the ccid-3 and ccid-4 integration
Date: Wed, 26 Sep 2007 23:51:12 +0000 [thread overview]
Message-ID: <5bc4c4570709261651t29d2c7f2u98c98fb068af0c97@mail.gmail.com> (raw)
In-Reply-To: <5bc4c4570709241115u1254baa9j7033d1bdc9dc079@mail.gmail.com>
2007/9/25, Gerrit Renker <gerrit@erg.abdn.ac.uk>:
> Sorry for the delay there were local bank holidays here.
>
> | - Rewrite all the patches (from me and Tommi) and resubmit to Gerrit
> | as a unique patchset, as suggested by Ian. Besides, ask Gerrit to
> | overwrite the current ccid4 branch;
> | - Identify and provide common code between ccid-4 and ccid-3.
> | 1 - minor functions from ccid-3.c to ccid-3.h and include it (.h) in
> | the ccid-4.c, as suggested by Ian and Arnaldo
> | 2 - for more complex functions, write a dccp_ccid3_lib.ko, as
> | suggested by arnaldo
> The ideas sound good, and I think it is a good idea to factor out what is
> not needed - just unclear which patch set to use, the latest so far is from
> Thursday?
> -
> To unsubscribe from this list: send the line "unsubscribe dccp" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Hi,
Gerrit, the latest so far is from Friday, the mine, which it was
similar to the Tommi patch, so then I just patches the differences
between the mine and the tommi's patchset. But I'm put all the patches
together (the mine and tommi as one patchset and I will ask you to
overwrite the current ccid4 branch. Besides, I'm going through the
ideas of dccp_ccid3_lib.ko.
Leandro.
next prev parent reply other threads:[~2007-09-26 23:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 18:15 Towards the ccid-3 and ccid-4 integration
2007-09-24 21:35 `
2007-09-25 2:45 ` Ian McDonald
2007-09-25 9:01 ` Gerrit Renker
2007-09-26 13:41 ` Tommi Saviranta
2007-09-26 23:41 ` Ian McDonald
2007-09-26 23:51 ` [this message]
2007-09-27 8:19 ` Gerrit Renker
2007-09-27 8:49 ` 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=5bc4c4570709261651t29d2c7f2u98c98fb068af0c97@mail.gmail.com \
--to=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.