public inbox for gentoo-science@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kacper Kowalik <xarthisius.kk@gmail.com>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] moving the science overlay to github?
Date: Sat, 25 Feb 2012 20:46:12 +0100	[thread overview]
Message-ID: <4F493A84.5030607@gmail.com> (raw)
In-Reply-To: <4F4938C4.6090708@gentoo.org>

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

On 25.02.2012 20:38, Kacper Kowalik wrote:
> On 25.02.2012 13:52, Kacper Kowalik wrote:
>> On 19.02.2012 15:07, Kacper Kowalik wrote:
>>> account on github and will try to work on mutual sync. When the latter
>>> is finished we can get things going. I'll keep you posted.
>>
>> It seems it's not possible to keep two writable git repos in sync in an
>> automated fashion. All solution I came up with/googled require at least
>> one repo to be read-only. Can anyone prove me wrong?
> 
> Ok, there's nice solution to the problem, as suggested by wired on
> g-dev[1], we should just push two both overlays at once. It requires
> manual tweaking of .git/config in your repo:
> 
> [remote "origin"]
>    fetch = +refs/heads/*:refs/remotes/origin/*
>    url = git+ssh://git@git.overlays.gentoo.org/proj/sci.git
>    pushurl = git@github.com:gentoo-science/sci.git

Correction to that ^^, you need both addresses to be in pushurl:

   pushurl = git@github.com:gentoo-science/sci.git
   pushurl = git+ssh://git@git.overlays.gentoo.org/proj/sci.git

Cheers,
Kacper


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]

      reply	other threads:[~2012-02-25 21:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-07 17:24 [gentoo-science] moving the science overlay to github? Sébastien Fabbro
2012-02-07 17:51 ` My Th
2012-02-07 18:26   ` Andrea Arteaga
2012-02-07 18:34 ` Alexey Shvetsov
2012-02-07 18:41   ` Christoph Junghans
2012-02-07 21:13     ` Sébastien Fabbro
2012-02-07 21:35       ` My Th
2012-02-08  8:23         ` Kacper Kowalik
2012-02-08  9:38         ` Thomas Kahle
2012-02-07 20:52 ` fbissey
2012-02-08  0:31   ` Alexey Shvetsov
2012-02-08  0:45     ` Christoph Junghans
2012-02-08  8:28     ` Kacper Kowalik
2012-02-08  9:35     ` Thomas Kahle
     [not found]       ` <201202081302.17255.marten@xtal.rwth-aachen.de>
2012-02-08 16:25         ` Christoph Junghans
2012-02-09  7:04           ` justin
2012-02-08 10:46   ` Christopher Schwan
2012-02-09  7:08 ` justin
2012-02-19 14:07 ` Kacper Kowalik
2012-02-19 14:42   ` Thomas Kahle
2012-02-19 21:54     ` Andrea Arteaga
2012-02-25 12:52   ` Kacper Kowalik
2012-02-25 19:38     ` Kacper Kowalik
2012-02-25 19:46       ` Kacper Kowalik [this message]

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=4F493A84.5030607@gmail.com \
    --to=xarthisius.kk@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