From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: Guix-devel <guix-devel@gnu.org>, Federico Beffa <beffa@ieee.org>
Subject: Re: wip-gobject-introspection
Date: Sat, 17 Jan 2015 23:51:03 +0100 [thread overview]
Message-ID: <87zj9hdns8.fsf@gnu.org> (raw)
In-Reply-To: <87a91hjdeb.fsf@netris.org> (Mark H. Weaver's message of "Sat, 17 Jan 2015 16:38:52 -0500")
Mark H Weaver <mhw@netris.org> skribis:
> You're right to be wary of rebasing public branches, but I think it's
> okay with short-lived experimental branches like this. If it turns out
> that someone else has done work on it, the situation is easily remedied.
Agreed. There’s the unwritten rule inherited from Guile that a branch
prefixed with “wip-” may be rebased.
Ludo’.
next prev parent reply other threads:[~2015-01-17 22:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 19:48 wip-gobject-introspection Federico Beffa
2015-01-14 20:51 ` wip-gobject-introspection Ludovic Courtès
2015-01-15 8:12 ` wip-gobject-introspection Federico Beffa
2015-01-16 20:33 ` wip-gobject-introspection Ludovic Courtès
2015-01-17 17:32 ` wip-gobject-introspection Mark H Weaver
2015-01-17 18:57 ` wip-gobject-introspection Federico Beffa
2015-01-17 21:38 ` wip-gobject-introspection Mark H Weaver
2015-01-17 22:51 ` Ludovic Courtès [this message]
2015-01-18 9:44 ` wip-gobject-introspection Federico Beffa
2015-01-18 17:26 ` wip-gobject-introspection Federico Beffa
2015-01-18 18:03 ` wip-gobject-introspection Federico Beffa
2015-01-18 18:45 ` wip-gobject-introspection Federico Beffa
2015-01-25 18:22 ` wip-gobject-introspection Federico Beffa
2015-01-25 23:42 ` wip-gobject-introspection Mark H Weaver
2015-01-26 2:26 ` wip-gobject-introspection Mark H Weaver
2015-01-26 8:11 ` wip-gobject-introspection Federico Beffa
2015-01-26 9:18 ` wip-gobject-introspection Andreas Enge
2015-01-26 20:20 ` wip-gobject-introspection Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zj9hdns8.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=beffa@ieee.org \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).