public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Rich Johnston <rjohnston@sgi.com>
To: xfs-oss <xfs@oss.sgi.com>
Subject: linux-3.12 userspace Take 2
Date: Mon, 28 Oct 2013 17:40:15 -0500	[thread overview]
Message-ID: <526EE7CF.7090603@sgi.com> (raw)
In-Reply-To: <526A6FF9.8000506@sgi.com>

Hey Folks,

Sorry for any confusion, let me try again.

In preparation for the new userspace release, are there any outstanding
userspace patches that should be marked as critical and hold up the new
userspace release?


Code shared by userspace and kernelspace are committed by different
maintainers, I propose we discuss how to make it clear which patch
series are tied together. This would aid reviewers and testers also.

	One thought is to state in the kernel [PATCH 0/XX] email body
	something like:
		This kernel series shares the same headers as the
		userspace series "NAME OF USERSPACE SERIES"

	and a similar email for the userspace series.

	The second commit should contain the first series commit id to
	tie them together.

Userspace patch series will be committed when the entire patch series 
has been reviewed.  Partial series commits will happen only with the 
authors approval (confirmation posted to the list).

Thanks
--Rich

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

  parent reply	other threads:[~2013-10-28 22:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-25 13:19 linux-3.12 userspace Rich Johnston
2013-10-25 15:02 ` Eric Sandeen
2013-10-25 17:55   ` Rich Johnston
2013-10-28  2:23     ` Dave Chinner
2013-10-28 22:40 ` Rich Johnston [this message]
2013-10-29 21:30   ` linux-3.12 userspace Take 2 Eric Sandeen
2013-10-29 22:05   ` 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=526EE7CF.7090603@sgi.com \
    --to=rjohnston@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox