DCCP protocol discussions
 help / color / mirror / Atom feed
From: "Arnaldo Carvalho de Melo" <arnaldo.melo@gmail.com>
To: dccp@vger.kernel.org
Subject: Re: [PATCH 0/17] [DCCP]: patch-backlog, bug-fixes, some code simplifications
Date: Tue, 24 Oct 2006 16:03:53 +0000	[thread overview]
Message-ID: <39e6f6c70610240903h65b11515j7a41979a75ec58d7@mail.gmail.com> (raw)
In-Reply-To: <200610241458.51517@strip-the-willow>

On 10/24/06, Gerrit Renker <gerrit@erg.abdn.ac.uk> wrote:
> As promised earlier, this is the set of patches which I have been
> keeping up-to-date; they divide into:
>
>         * patches sent to this list that have not been merged
>           [I claim that this is exhaustive, i.e. all other patches
>            have been merged - notify me if there is one missing]
>         * bug fixes
>         * `cosmetic' patches to simplify and consolidate code
>
> The set is consistent in itself and patches on top of the latest davem-2.6
> tree, but: all are stacked, i.e. the best way of applying is
>
>         for p in $patches; do git-apply < $p; done
>
> There are no new files introduced, so this works without problem. I have put
> in extra time to check / tidy each and every one. I hope that this will pay
> off, as I have little benefit from this and had to take this time away from
> other commitments.

Thanks a lot for this Gerrit, now I have a work related meeting, but
later today I'll try and review these patches and get them into a
net-2.6.20 tree

- Arnaldo

  reply	other threads:[~2006-10-24 16:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-24 13:58 [PATCH 0/17] [DCCP]: patch-backlog, bug-fixes, some code simplifications Gerrit Renker
2006-10-24 16:03 ` Arnaldo Carvalho de Melo [this message]
2006-10-25  2:52 ` Ian McDonald
2006-10-25 11:58 ` Gerrit Renker
2006-10-26 13:36 ` Gerrit Renker
2006-10-26 22:45 ` 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=39e6f6c70610240903h65b11515j7a41979a75ec58d7@mail.gmail.com \
    --to=arnaldo.melo@gmail.com \
    --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