From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: dccp@vger.kernel.org
Subject: Re: [PATCH 0/5] CCID 4: initial implementation of CCID 4
Date: Thu, 20 Sep 2007 13:01:52 +0000 [thread overview]
Message-ID: <200709201401.52593@strip-the-willow> (raw)
In-Reply-To: <20070920111557.GA1288@kikai.katei.fi>
| Re-submitting, with hopefully proper tags etc.
|
|
| After discussing the topic on IRC, we figured we need a place to have
| the sources for CCID 4 available for everyone. This way we can finally
| start cooperating on it.
|
The patches applied fine, a new subtree `ccid4' has been created to host these.
The subtree can be checked out by
1) create a subtree
git-checkout -b ccid4 master
2) pull the CCID4 subtree
pull eden-feed:/usr/src/GIT/dccp_exp.git ccid4
This tree now sits on top of the test tree, i.e. inherits it. As said, I am ok
tracking changes required to ensure that patches remain applicable.
What I can't do is to track updates to CCID3 into your code, since that would mean
altering your patches; so it is something you need to keep track of yourselves.
Gerrit
next prev parent reply other threads:[~2007-09-20 13:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 11:15 [PATCH 0/5] CCID 4: initial implementation of CCID 4 Tommi Saviranta
2007-09-20 13:01 ` Gerrit Renker [this message]
2007-09-20 13:08 `
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=200709201401.52593@strip-the-willow \
--to=gerrit@erg.abdn.ac.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox