From: Christoph Hellwig <hch@infradead.org>
To: sandeen@redhat.com
Cc: linux-xfs@vger.kernel.org
Subject: xfsprogs process question
Date: Thu, 12 Mar 2020 07:13:51 -0700 [thread overview]
Message-ID: <20200312141351.GA30388@infradead.org> (raw)
Hi Eric and others,
I've recently tried to port my attr cleanups to xfsprogs, but noticed
that a lot of patches from others are missing before I could apply
my ptches. Any chance we could try to have a real xfsprogs for-next
branch that everyone can submit their ports to in a timely fashion?
Without that I'm not sure how to handle the porting in a distributed
way.
next reply other threads:[~2020-03-12 14:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 14:13 Christoph Hellwig [this message]
2020-03-12 15:46 ` xfsprogs process question Eric Sandeen
2020-03-12 16:17 ` Allison Collins
2020-03-12 16:32 ` Eric Sandeen
2020-03-12 17:33 ` Allison Collins
2020-03-13 6:54 ` Christoph Hellwig
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=20200312141351.GA30388@infradead.org \
--to=hch@infradead.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.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