From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [RFC] Handling of reviewed patch series
Date: Fri, 13 Dec 2013 03:19:59 -0800 [thread overview]
Message-ID: <20131213111959.GF23546@infradead.org> (raw)
In-Reply-To: <20131213053611.GQ10988@dastard>
I'm a big fan of the for-next vs for-linux split for next release work
vs bugfixes which we've not applied yet. The whole topic branches
scheme makes sense for large changes like the crc work, but seems
utterly confusing if applied to every little change, as now the amount
of branches you can conflict againt multiplies. I'm defintively in
favour of a model that has less active branches.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-12-13 11:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 5:36 [RFC] Handling of reviewed patch series Dave Chinner
2013-12-13 11:19 ` Christoph Hellwig [this message]
2013-12-13 11:47 ` Dave Chinner
2013-12-13 13:42 ` Brian Foster
2013-12-13 22:44 ` Dave Chinner
2013-12-13 18:56 ` Ben Myers
2013-12-13 23:14 ` Dave Chinner
2013-12-13 23:59 ` Dave Chinner
2013-12-16 23:39 ` Ben Myers
2013-12-17 3:54 ` 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=20131213111959.GF23546@infradead.org \
--to=hch@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox