From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Netfilter Developer Mailing List <netfilter-devel@vger.kernel.org>
Subject: Re: [pull] all patches complete
Date: Mon, 16 Feb 2009 13:15:58 +0100 [thread overview]
Message-ID: <499958FE.2060002@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.00.0902161307420.12536@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Monday 2009-02-16 11:41, Patrick McHardy wrote:
>
>> Jan Engelhardt wrote:
>>> All patches have been gathered and collected, pullable at the usual place of
>>> git://dev.medozas.de/iptables master
>>>
>>> 20 files changed, 180 insertions(+), 173 deletions(-)
>> I wanted to pull this, but I'm again getting a quite different
>> diffstat:
>
> This is because another patch was added at jamal's request.
>
> I am not quite sure how the preferred workflow is for when
> only a subset of a branch is supposed to be merged (because
> the branch already moved on). I guess
> `git fetch...; git merge $sha1` would work, but that looks
> a bit odd in the changelog.
> stat is currently
> 21 files changed, 242 insertions(+), 258 deletions(-)
The preferred way is to not change the public tree after a pull request
until it has been pulled. Not sure how you work, but I assume you have
a local tree that you push to the public one. In that case simply wait
until I've pulled before you update again.
next prev parent reply other threads:[~2009-02-16 12:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-13 15:45 [pull] all patches complete Jan Engelhardt
2009-02-16 10:41 ` Patrick McHardy
2009-02-16 12:11 ` Jan Engelhardt
2009-02-16 12:15 ` Patrick McHardy [this message]
2009-02-16 12:17 ` Patrick McHardy
2009-02-16 12:25 ` Jan Engelhardt
2009-02-16 12:27 ` Patrick McHardy
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=499958FE.2060002@trash.net \
--to=kaber@trash.net \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@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.