From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: LMML <linux-media@vger.kernel.org>
Subject: [ANNOUNCE] Changes at the master repository (media-tree.git)
Date: Tue, 5 Mar 2013 09:32:55 -0300 [thread overview]
Message-ID: <20130305093255.4595eb49@redhat.com> (raw)
I did today one change at the master driver development repository.
In the past, we used to have per-kernel release branches. The rationale is that
we were doing rebases on each new version, when we migrated from hg to git.
Well, we don't do such rebases anymore; instead, when a new version comes, we
just merge from Linus tree (typically at *-rc1). So, we don't need that schema
anymore.
Also, as we'll now have sub-maintainers, it is better to keep the branch
namespace ready for topic branches.
So, I renamed all previous "staging/for*" branches to "staging/for*" tags.
Also, we'll now be using the "master" branch for development.
Except for the noise during this transition phase, I expect that this
way, it will be easier for developers, as they don't need anymore to
track when a new "staging/for*" branch is created, in order to do their
work.
It also prevents me and others to change any existing auto-building script
to work with the newly "staging/for*" branch when it is created.
Regards,
Mauro
reply other threads:[~2013-03-05 12:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130305093255.4595eb49@redhat.com \
--to=mchehab@redhat.com \
--cc=linux-media@vger.kernel.org \
/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).