From: Holger Freyther <zecke@selfish.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: SCM scorecards
Date: Thu, 27 Mar 2008 03:11:47 +0100 [thread overview]
Message-ID: <200803270311.47461.zecke@selfish.org> (raw)
In-Reply-To: <47EAF1E0.8090401@xora.org.uk>
On Thursday 27 March 2008 02:01:20 Graeme Gregory wrote:
> Yes, mtn is designed to have many repos which are mirrors. From my
> looks at git it is designed to always end up with one central repo.
>
> The methods of syncing two git trees seem to be hacks or alter
> data. master becomes origin/master for example.
repo.or.cz supports a mirror mode so it can't be too hard. My approach would
consist out of two shell commands:
1. git-fetch remote to fetch everything from the remote
2. git-reset to update the branches to the version of the newly fetched
files.
but then we can ask the provider of repo.or.cz where you can ask it to mirror
any other git tree how he is implementing it.
>
> And because you always have to pull before push, people cant
> use upstreams in parrallel and the tool just works.
I don't follow here. Creating a branch is the first exception, you push before
you pull there. If you mean that currently I can push to wolfson and it will
end up on mtn.oe.org automatically then yes, mtn can do the syncing in a
fantastic way. And yes with mtn it is more easy due multiple heads. I think
it is doable with git as well.
next prev parent reply other threads:[~2008-03-27 2:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 0:32 SCM scorecards Graeme Gregory
2008-03-27 0:50 ` Michael 'Mickey' Lauer
2008-03-27 1:01 ` Graeme Gregory
2008-03-27 2:11 ` Holger Freyther [this message]
2008-03-27 13:40 ` Mark Brown
2008-03-27 1:16 ` Rod Whitby
2008-03-27 2:26 ` Holger Freyther
2008-03-27 2:49 ` Holger Freyther
2008-03-27 16:01 ` Koen Kooi
2008-03-27 16:50 ` Holger Freyther
2008-03-27 16:15 ` Graeme Gregory
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=200803270311.47461.zecke@selfish.org \
--to=zecke@selfish.org \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.