All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Dave Chinner <david@fromorbit.com>, xfs@oss.sgi.com
Subject: Re: [ANNOUNCE, DISCUSS] xfsprogs: libxfs-4.1-update branch created
Date: Mon, 11 May 2015 09:48:03 -0500	[thread overview]
Message-ID: <5550C123.8060806@sandeen.net> (raw)
In-Reply-To: <20150511000508.GD16689@dastard>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 5/10/15 7:05 PM, Dave Chinner wrote:
> Hi folks,

...

> This userspace update work needs to
> be distributed over the developers making the API and functionality
> changes, so I'm throwing this out there to see what people think
> about solving this problem.

...

> So, what do the people I'm asking to do more work so I don't have
> to spend so much time on time consuming maintenance tasks think?

I think it makes perfect sense, and I'm happy to do it.  The giant
sync-ups after the fact have never been ideal from any perspective.

I'm glad you brought this up; I don't think anyone ever meant to simply
leave this to the maintainer - it just ended up that way, because the
rules or best practices weren't necessarily clear.

So; do you envision a 0/8 patch series, 4 of which touch libxfs, to
now be a 0/12 patch series, with the userspace bits i.e. at the end?
I'd be perfectly happy with this; once libxfs stays up to date in
userspace, it should be trivial.

- -Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQIcBAEBAgAGBQJVUMEiAAoJECCuFpLhPd7gwsEP/24cd6X9CQAAiCQGmB5rfTON
jj2QcvyANY0AFIxZGiJWlaulSGYsnzcN55G1W0JkoIDSfCwQq+I1UgCVtcns9nUU
LXaPgWQh0LgJSfYs+LezkwlulOAYWW2LOolDPPIyEyoVxkAHmm6M9kajj2NaHd5S
OmvoqBxRM/nl3DfRw3H/b5ARH2EDWQvgkbBoPwzD74oYMrxBK0bDV7dHrBh9I4yu
HE3R8zI+eIZxMy6hAV2WGRQg00GPW9bWJfuDp2HvekcdsbGc8JJN1fF/j5nlJX/r
h8dz0HbkB2ioZ2ErgcB7v4xZjpvcqg/sD6Zo7ehSyW0TE1Nxr9I4L7x1k048fh4P
JCZWViR4ddo5h4Wiheq7wFmNqSu0VL6lPzYpty/M8wIt2nLZcgjKq1agtDMHKcvJ
PeDanT2u6PkgrJIlZORnhCaGLfu1bNBqtnUGJXtPUMKGwl+CdZBqAsEe3pg5LH4f
3007zGBHhPg93/ZTdmgkjjbZlGt3qeT+tpFgnYJYSNTzj3Pom1ZvxXvXl3TnATTu
3phKrSpuWvHETmm9vz1xj/a2KXeyLOMpdgZYkDULfrwJnERbyE5wcNFNwSmUH0lI
69Ul/KvSY1TdrhvuAPA121TsuhSPP9YTZaeZnkITDn841P4wnaKb1TtP6NKldje0
f/4574r8AUVM5RoLuW9K
=PWIs
-----END PGP SIGNATURE-----

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2015-05-11 14:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-11  0:05 [ANNOUNCE, DISCUSS] xfsprogs: libxfs-4.1-update branch created Dave Chinner
2015-05-11  5:37 ` Christoph Hellwig
2015-05-11 12:39 ` Brian Foster
2015-05-11 13:20   ` Dave Chinner
2015-05-11 14:14     ` Brian Foster
2015-05-11 14:50   ` Eric Sandeen
2015-05-11 14:48 ` Eric Sandeen [this message]
2015-05-11 21:28   ` Dave Chinner
2015-05-11 23:47     ` Eric Sandeen
2015-05-13 22:14 ` Eric Sandeen
2015-05-13 22:25   ` Eric Sandeen
2015-05-13 22:42     ` Eric Sandeen
2015-05-14  1:04   ` Dave Chinner

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=5550C123.8060806@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=david@fromorbit.com \
    --cc=xfs@oss.sgi.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 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.