unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
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: Sat, 17 Jan 2015 19:57:58 +0100	[thread overview]
Message-ID: <CAKrPhPP559a=aPRxT3Vd5+UBWJ7KFX2qZm4NVhqa5=5q2OYSMw@mail.gmail.com> (raw)
In-Reply-To: <87egqtjosx.fsf@netris.org>

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.

I would like to double check if I'm the only one having done any
commits to wip-gobject-introspection branch (even local, not pushed
ones.  This is because the git manual warns people away from rebasing
branches which have been made public and on which somebody else has
done some work. So, I would like to make sure I don't mess up with
anyone.

If I understand correctly this is the command I would issue from the
wip-gobject-introspection branch:

git rebase master

>
> Note that since 'udev' was removed completely in core-updates, and now
> 'eudev' is its own package that doesn't inherit from, your 'eudev'
> commits will have to be manually adjusted.

OK

I've also noticed that xorg-server failed to pass a test on hydra. I'm
surprised because on my x86_64 machine everything goes smooth.  Maybe
the rebase will help as I see that master has a newer xorg-server
version.

Regards,
Fede

  reply	other threads:[~2015-01-17 18:58 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       ` Federico Beffa [this message]
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             ` 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='CAKrPhPP559a=aPRxT3Vd5+UBWJ7KFX2qZm4NVhqa5=5q2OYSMw@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).