From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: Dave Taht <dave.taht@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] 2 commits - unintended changes?
Date: Fri, 27 Nov 2015 19:13:13 +0000 [thread overview]
Message-ID: <5658AB49.1030606@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <CAA93jw57SC7crs+VdMYjB2QozkFwJWyk+J-SSFKCJiTd0odKfQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 540 bytes --]
On 27/11/15 14:43, Dave Taht wrote:
> thx for the review. sorry for not keeping these commits more separated.
>
> this fixes the ecn calculation which otherwise wrapped.
> Dave Täht
> Let's go make home routers and wifi faster! With better software!
> https://www.gofundme.com/savewifi
>
I discovered the 'git commit -p' (--patch) toy the other day, when I'd
got carried away and changed a few things and then thought I should
split them across commits. Saved me an awful lot of hassle. Am always
learning with git :-)
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4816 bytes --]
prev parent reply other threads:[~2015-11-27 19:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 14:39 Kevin Darbyshire-Bryant
2015-11-27 14:43 ` Dave Taht
2015-11-27 19:13 ` Kevin Darbyshire-Bryant [this message]
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
List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5658AB49.1030606@darbyshire-bryant.me.uk \
--to=kevin@darbyshire-bryant.me.uk \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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