From: David Pirotte <david@altosw.be>
To: guile-devel <guile-devel@gnu.org>
Subject: guile-clutter, 1.10.0 -> 1.12.2, git repo quiz
Date: Fri, 11 Apr 2014 17:32:02 -0300 [thread overview]
Message-ID: <20140411173202.4f9895d3@capac> (raw)
Hello guilers,
I started [slowly but hopefully surely :)] to work on updating our guile-clutter
binding from clutter 1.10.0 to clutter 1.12.2. [sorry in advance if some of the
questions I will ask may sound a bit stupid, my knowledge of involved lower level
tools, modules, ... is quite 'superficial' [autotools, g-wrap, gobject, glib ...]].
Preliminary thought: although part of guile-gnome, I think it would be
better to have a separate guile-clutter project, with its own git repo and
website, wdyt?
-] git organization
I locally created a clutter-devel branch: I'd like to push it, if that's ok, so I
can start to submit patches [for review before to push], leaving the actual clutter
branch untouched until ready to merge.
From there, I suggest we maintain a branch model based on clutter itself:
Branch
clutter-1.10
clutter-1.12
...
clutter [would always = the latest stable]
clutter-devel on going work
[ I hope, once I've done 1.12.2, to work on other versions, up to the latest we
will be able to support using guile-gnome-2 ]
Until clutter-2.0 [2.x.x, v2.x.x are actual guile-gnome tags], we can also maintain
tags without clash, then we'll see :) or should we adopt right now another naming
convention, such as c1.10.0, cl-v1.10.0 or even clutter-v1.10.0 maybe?
Cheers,
David
reply other threads:[~2014-04-11 20:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140411173202.4f9895d3@capac \
--to=david@altosw.be \
--cc=guile-devel@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).