From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Slaughtering the sacred cow
Date: Tue, 8 Jun 2010 11:50:11 +0200 [thread overview]
Message-ID: <AANLkTilzPoCBFEJiJBHubIjqcN7fQdI2Eg8tsGuiSfGZ@mail.gmail.com> (raw)
In-Reply-To: <4C0E0E98.6080806@drmicha.warpmail.net>
Hi,
Michael J Gruber wrote:
> I don't pretend to have a perfect solution for this, but I'm wondering
> whether a longer-lived for-1.x.0 branch (with or without an extra pu,
> i.e. not rewinding itself [leaving that for the extra pu] or rewinding)
> would be feasible which gets everything from next-master-maint and which
> would also be a place to cook larger structural, backwards incompatible
> changes. An alternative would be to have a branch like that for a
> specific large topic (like one of the above) and focus on that for the
> upcoming release.
I'm relatively new to the list but from what I've seen, I think
keeping a longer-lived branch that accepts less-than-complete patches
is a good idea. Small patches that break backward compatibility are
often criticized (often leading to rejection), while larger patches
with the promise of showing the whole picture often tend to be ignored
due to their sheer size.
-- Ram
prev parent reply other threads:[~2010-06-08 9:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 9:34 Slaughtering the sacred cow Michael J Gruber
2010-06-08 9:50 ` Ramkumar Ramachandra [this message]
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=AANLkTilzPoCBFEJiJBHubIjqcN7fQdI2Eg8tsGuiSfGZ@mail.gmail.com \
--to=artagnon@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@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).