From: "Pali Rohár" <pali.rohar@gmail.com>
To: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
Cc: util-linux@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Help with reviewing dosfstools patches
Date: Fri, 14 Jun 2019 21:10:53 +0200 [thread overview]
Message-ID: <20190614191053.22whtrb5f5uqis64@pali> (raw)
In-Reply-To: <9e81aa56-358a-71e1-edc1-50781062f3a4@metux.net>
[-- Attachment #1: Type: text/plain, Size: 677 bytes --]
On Friday 14 June 2019 17:45:20 Enrico Weigelt, metux IT consult wrote:
> On 14.06.19 16:20, Enrico Weigelt, metux IT consult wrote:
>
> <snip>
>
> Currently working through your branches. Smells like they really deserve
> a rebase and signed-off lines.
Every patch/pull request is mean to be based on current upstream
"master" branch.
As some of pull requests were opened long time ago, they are out-of-sync
from upstream "master" branch.
Currently I rebased and force-pushed those changes which had merge
conflict with upstream master branch.
And now on each pull request passed compilation and 'make check'.
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2019-06-14 19:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 10:25 Help with reviewing dosfstools patches Pali Rohár
2019-06-14 14:20 ` Enrico Weigelt, metux IT consult
2019-06-14 14:25 ` Pali Rohár
2019-06-14 14:30 ` Christoph Hellwig
2019-06-14 19:08 ` Pali Rohár
2019-06-14 15:45 ` Enrico Weigelt, metux IT consult
2019-06-14 18:45 ` Enrico Weigelt, metux IT consult
2019-06-14 19:10 ` Pali Rohár [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190614191053.22whtrb5f5uqis64@pali \
--to=pali.rohar@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metux.net \
--cc=util-linux@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;
as well as URLs for NNTP newsgroup(s).