From: Peter Harris <git@peter.is-a-geek.org>
To: Andreas Ericsson <ae@op5.se>
Cc: "Patrick Neuner - Futureweb.at" <neuner@futureweb.at>,
Jeff King <peff@peff.net>,
git@vger.kernel.org
Subject: Re: AW: Parallell Development / Switching to GIT
Date: Mon, 29 Jun 2009 12:37:42 -0400 [thread overview]
Message-ID: <eaa105840906290937h14868eb8v7928951876f7e8f1@mail.gmail.com> (raw)
In-Reply-To: <4A487CCD.1040406@op5.se>
On Mon, Jun 29, 2009 at 4:35 AM, Andreas Ericsson wrote:
> Patrick Neuner - Futureweb.at wrote:
>> But having 2 completly different repos would be another solution, but
>> I kinda wonder that mergin would work correctly this way (if both
>> sides have changes).
> I'd advise you to clone the linux kernel and inspecting its history
> using gitk. Every merge-commit you see which has a line saying something
> like "merge foo bar frotz of git://example.com/path/to/repo.git" is a
> merge with branches from different repositories. I wouldn't be the least
> surprised if you find more than 5000 such merges in the linux kernel
> history.
You got me curious, so I looked:
~/linux-2.6$ git log | grep -c "Merge.*git:"
4431
Not quite 5000, but still an average of roughly 2.88 such merges per
day, every single day, since the kernel was moved to git in 2005.
Peter Harris
next prev parent reply other threads:[~2009-06-29 16:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 9:52 Parallell Development / Switching to GIT Patrick Neuner
2009-06-25 10:11 ` Andreas Ericsson
2009-06-28 17:51 ` AW: " Patrick Neuner - Futureweb.at
2009-06-28 18:47 ` Jeff King
2009-06-28 20:08 ` AW: " Patrick Neuner - Futureweb.at
2009-06-28 22:33 ` David Aguilar
2009-06-29 8:35 ` AW: " Andreas Ericsson
2009-06-29 16:37 ` Peter Harris [this message]
2009-07-02 0:47 ` AW: " Patrick Neuner - Futureweb.at
2009-07-02 6:20 ` Johannes Sixt
2009-07-02 11:44 ` AW: " Patrick Neuner - Futureweb.at
2009-07-02 11:55 ` Johannes Sixt
2009-06-30 5:32 ` Jeff King
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=eaa105840906290937h14868eb8v7928951876f7e8f1@mail.gmail.com \
--to=git@peter.is-a-geek.org \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=neuner@futureweb.at \
--cc=peff@peff.net \
/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;
as well as URLs for NNTP newsgroup(s).