List for cgit developers and users
 help / color / mirror / Atom feed
From: Jason at zx2c4.com (Jason A. Donenfeld)
Subject: Development Flow Improvements
Date: Tue, 27 Sep 2016 20:52:15 +0200	[thread overview]
Message-ID: <CAHmME9o2g_5g8d6Ne4=UVO+Ur0oiD-=xcJ_JA==iYGiw+FnpLQ@mail.gmail.com> (raw)

Hey folks,

I wanted to update you on a conversation a few of us have been having
off-list. In order to hasten the speed of development, we're making
some changes to the way things are done.

All submitted patch series will now live in feature branches. Each
feature branch will be owned by either me (jd), John (jk), Christian
(ch), Ferry (fh), Lukas (lf), or Lars (lh), and will be titled
something like "jk/add-links-to-header". After enough review, and the
feature is ready to land, it will be put into the owner's "for-jason"
branch -- such as "ch/for-jason". Then, when I'm ready, I'll review
and sweep up all the various */for-jason branches (including my own!)
into master, and sometime after that cut a release.

This should pick up the pace a little bit, because it enables any of
us to more easily review a patch series and get it ready for final
inclusion. So, if you submit a patch series, and you get a reply from
me, John, Christian, Ferry, Lukas, or Lars, saying something like,
"I'll review this," it means it should shortly after wind up in a
feature branch on <https://git.zx2c4.com/cgit/>.

I think this will work out well. Looking forward to finally see some
patches land.

Regards,
Jason


             reply	other threads:[~2016-09-27 18:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-27 18:52 Jason [this message]
2016-09-27 21:05 ` jamie.couture
2016-09-27 23:27   ` Jason
2016-09-28  7:16     ` mailings
2016-11-24 23:23     ` peter

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='CAHmME9o2g_5g8d6Ne4=UVO+Ur0oiD-=xcJ_JA==iYGiw+FnpLQ@mail.gmail.com' \
    --to=cgit@lists.zx2c4.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;
as well as URLs for NNTP newsgroup(s).