From: Federico Beffa <beffa@ieee.org>
To: Mark H Weaver <mhw@netris.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: wip-gobject-introspection
Date: Sun, 18 Jan 2015 18:26:51 +0100 [thread overview]
Message-ID: <CAKrPhPPP_c39N5YP-DpZkOS5_3sCNfnWWDkjbhR_0zXOfSgnpA@mail.gmail.com> (raw)
In-Reply-To: <CAKrPhPOc=sERTTaG_-uQzZKuaX4vPn5PE6amX=Y9Ycjsxt0Qvg@mail.gmail.com>
On Sun, Jan 18, 2015 at 10:44 AM, Federico Beffa <beffa@ieee.org> wrote:
>>> On Sat, Jan 17, 2015 at 6:32 PM, Mark H Weaver <mhw@netris.org> wrote:
>>>> At this point, it would be good to rebase (not merge) the
>>>> 'wip-gobject-introspection' branch on current master. Presently, the
>>>> branch is based on master before core-updates was merged, which means a
>>>> considerably different core system than what we currently have.
[...]
>>> If I understand correctly this is the command I would issue from the
>>> wip-gobject-introspection branch:
>>>
>>> git rebase master
>>
>> Yes. It will need help rebasing your 'eudev' commits. As with 'git
>> merge', it will insert merge conflict markers which you must fix up
>> yourself. Then 'git add <files>' and 'git rebase --continue'.
>>
>> Then, after some testing, it would be good to push it to savannah.
>> Because of the rebase, you'll have to delete the branch on savannah and
>> then remake it, as follows:
>>
>> git push origin :wip-gobject-introspection # delete it on savannah
>> git push origin wip-gobject-introspection # push the new one
>>
I've rebased the branch, checked that eudev builds fine after
adjusting it and re-created the branch on savannah.
Regards,
Fede
next prev parent reply other threads:[~2015-01-18 17:26 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 ` wip-gobject-introspection Ludovic Courtès
2015-01-18 9:44 ` wip-gobject-introspection Federico Beffa
2015-01-18 17:26 ` Federico Beffa [this message]
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=CAKrPhPPP_c39N5YP-DpZkOS5_3sCNfnWWDkjbhR_0zXOfSgnpA@mail.gmail.com \
--to=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).