From: Hamish D <dmishd@gmail.com>
To: Matthieu Rakotojaona <matthieu.rakotojaona@gmail.com>
Cc: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [sup-talk] Github organization for sup and heliotrope
Date: Thu, 17 Jan 2013 23:01:00 +0000 [thread overview]
Message-ID: <CAOxvSbdYRKwsuuZVuNkuhT-C-JV4nxGr1WQ-0-o59+zbgy04AA@mail.gmail.com> (raw)
In-Reply-To: <CAMiZLn0QPzDPTxAuR9BcdWv2KPU4Zw-8wCQSSnLrYkq-tGSvow@mail.gmail.com>
> I'm quite attracted to the git-flow [1]
> model; I propose we follow it, and have therefore created a develop
> branch which is just a branch at the same level as master. Please,
> feel free to fork develop and code/test over it. I already have a
> bunch of propositions to do and will soon put them in the repo (I just
> realized my own repo was way too dirty to put it up now)
I've pushed the next branch from the old sup repo to the develop
branch of the new sup repo. Those are patches I'd previously reviewed
and accepted.
What is currently on master is what I was thinking about asking
William to release as sup 0.13 but I never quite made that happen.
There are various other branches in the old git repo aswell. Do we
want to put them all on github for merging in our own sweet time? Or
just review them locally and only push the good ones?
Hamish
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
prev parent reply other threads:[~2013-01-17 23:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 20:15 Matthieu Rakotojaona
2013-01-17 20:52 ` Gaute Hope
2013-01-17 21:09 ` Hamish D
2013-01-17 23:43 ` Hamish D
2013-01-17 23:01 ` Hamish D [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=CAOxvSbdYRKwsuuZVuNkuhT-C-JV4nxGr1WQ-0-o59+zbgy04AA@mail.gmail.com \
--to=dmishd@gmail.com \
--cc=matthieu.rakotojaona@gmail.com \
--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