From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] slowly catching up
Date: Sat, 07 Nov 2009 08:56:10 -0800 [thread overview]
Message-ID: <1257612219-sup-7066@masanjin.net> (raw)
In-Reply-To: <1257562722-sup-9854@zyrg.net>
Reformatted excerpts from Rich Lane's message of 2009-11-06:
> As for getting changes to William, I'll occasionally (weekly?) apply
> the patches I deem stable on top of his master branch and send mail to
> the list. This way it should be a fast-forward when he pulls and we
> won't have to worry about resolving merges differently.
Sounds good to me. I'm not even that concerned about fastforward vs
merge.
> As a side note, I just created a Wishlist wiki page for feature requests:
> http://sup.rubyforge.org/wiki/wiki.pl?Wishlist
I agree that these would be great to have on the issue tracker.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2009-11-07 17:01 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
2009-11-07 7:09 ` Rich Lane
2009-11-07 9:34 ` Tero Tilus
2009-11-07 16:56 ` William Morgan [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=1257612219-sup-7066@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