public inbox for gentoo-science@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nicolas Bock <nicolasbock@gmail.com>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] Git push problems
Date: Thu, 7 Nov 2013 13:34:10 -0700	[thread overview]
Message-ID: <CAPMKG4DAtr=0RdB=KqO7dG45C41NQa806wko8_RwfcoqkK4PRQ@mail.gmail.com> (raw)
In-Reply-To: <527BF6A3.5050107@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 988 bytes --]

Thanks for the recipe!


On Thu, Nov 7, 2013 at 1:22 PM, justin <jlec@gentoo.org> wrote:

> Hi,
>
> after talking to our infra guys and alexxy about it, I came to the point
> that we should still allow commits to both repos for everyone with
> commit access.
>
> To avoid future trouble here are some rules to stick to.
>
> * Don't _amend_ already pushed commits.
> * Don't _rebase_ already pushed commits.
> * Don't --force a push.
>
> In case you still have problems, then follow this receipt from alexxy.
> He will write some longer instructions soonish in the wiki.
>
> $ git fetch --all (assume that you added github as another upstream.
> origin is g.o.g.o and github is github)
> $ git merge github/master
> $ git push origin
> that will merge github to g.o.g.o
> now we should merge g.o.g.o back to github
> $ git checkout -b github github/master
> $ git merge origin/master
> $ git push github HEAD:master
> $ git checkout master
>
> That should fix our problems.
>
> Justin
>
>

[-- Attachment #2: Type: text/html, Size: 1417 bytes --]

  reply	other threads:[~2013-11-07 20:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05 20:28 [gentoo-science] Git push problems Justin (jlec)
2013-11-05 20:31 ` Nicolas Bock
2013-11-05 20:42   ` Justin (jlec)
2013-11-05 20:48     ` Nicolas Bock
2013-11-05 20:33 ` Christoph Junghans
2013-11-07 20:22 ` justin
2013-11-07 20:34   ` Nicolas Bock [this message]
2013-11-07 20:35   ` François Bissey

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='CAPMKG4DAtr=0RdB=KqO7dG45C41NQa806wko8_RwfcoqkK4PRQ@mail.gmail.com' \
    --to=nicolasbock@gmail.com \
    --cc=gentoo-science@lists.gentoo.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