From: Michael Stapelberg <michael+sup@stapelberg.de>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Label colors support
Date: Wed, 26 Jan 2011 21:20:55 +0100 [thread overview]
Message-ID: <1296073198-sup-5439@midna.zekjur.net> (raw)
In-Reply-To: <1282251819-sup-3517@mintaka>
Hi Matias,
Excerpts from Matias Aguirre's message of 2010-08-19 23:04:36 +0200:
> Indeed that will be clearer, here's the changeset:
> http://github.com/omab/sup/commit/1a96a0ae856076d645a11e0b7d94858851343e27
I just created a branch 'label-colors' and merged it into 'next' of
sup/mainline (based on your merged request on gitorious).
Thanks for contributing!
Best regards,
Michael
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2011-01-26 20:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 22:14 Matias Aguirre
2010-08-04 16:41 ` Matias Aguirre
2010-08-04 16:50 ` Matias Aguirre
2010-08-19 8:13 ` Sascha Silbe
2010-08-19 21:04 ` Matias Aguirre
2011-01-26 20:20 ` Michael Stapelberg [this message]
2011-01-26 21:21 ` Matias Aguirre
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=1296073198-sup-5439@midna.zekjur.net \
--to=michael+sup@stapelberg.de \
--cc=sup-devel@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