From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] slowly catching up
Date: Fri, 06 Nov 2009 05:47:51 -0800 [thread overview]
Message-ID: <1257509523-sup-3428@masanjin.net> (raw)
In-Reply-To: <1257476207-sup-3459@zyrg.net>
Reformatted excerpts from Rich Lane's message of 2009-11-05:
> Rather than committing directly to mainline, I'd rather keep a public
> repo that I apply incoming patches to and that William can pull from.
> This way I could do a lot of the first-line work and he could get a
> more stable flow of patches to make releases from.
That sounds good to me. I'm happy to add you to the gitorious repo, of
course, but this is definitely more in line with the git lifestyle.
We have a couple options on how to organize this, but I think the best
would be for you to maintain one or more branches that I treat as
integration branches, and periodically merge into master whenever you
tell me they're ready. That's a very minimal amount of work for me. I
can just merge it and forget it.
The only things to be careful about in such a setup are not merging next
into your branch (merging master in is fine and good to keep up with
other stable changes), and not rebasing. And we will have to coordinate
on releases, if nothing else so that I can make reasonable changelogs
and release notes.
How does that sound?
> I can imagine that a lot of William's work caused by being the central
> repository is reviewing the patches that get sent in. I'd like for
> anyone who feels interested to read through incoming patches and comment
> on them. I don't want any strict processes just yet, but I'd like to see
> a couple of positive reviews (depending on the complexity of the patch,
> etc) before things get merged.
That would be great. Or heck, even an "I applied it and it works for
me" is useful.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2009-11-06 13:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-31 14:03 William Morgan
2009-11-02 7:29 ` Tero Tilus
2009-11-03 18:14 ` William Morgan
2009-11-06 2:38 ` Andrei Thorp
2009-11-06 4:13 ` Rich Lane
2009-11-06 13:47 ` William Morgan [this message]
2009-11-07 7:09 ` Rich Lane
2009-11-07 9:34 ` Tero Tilus
2009-11-07 16:56 ` William Morgan
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=1257509523-sup-3428@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=sup-talk@rubyforge.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