From: Junio C Hamano <gitster@pobox.com>
To: "Kai Hendry" <hendry@aplixcorp.com>
Cc: git@vger.kernel.org
Subject: Re: Integration branching
Date: Mon, 07 Apr 2008 11:44:30 -0700 [thread overview]
Message-ID: <7vd4p1pks1.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <b24851260804071118h4eaadef8i8313c5a4cb26495d@mail.gmail.com> (Kai Hendry's message of "Mon, 7 Apr 2008 19:18:45 +0100")
"Kai Hendry" <hendry@aplixcorp.com> writes:
> On Mon, Apr 7, 2008 at 6:41 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> A set of big questions is how that git.webvm.net/srv/git/webkit-test
>> repository was prepared, what its history look like and how it relates to
>> the history your repository has. I presume that that is different from
>> the repository you are pushing from (which is "x61:aplix/test/WebKit"
>> repository), but other than that you did not give any details to guess
>> further.
>
> webkit-test was just a `git --bare init --shared` and completely empty
> with I tried pushing (publishing) the changes to WebKit trunk.
That explains it without the "theory" in my previous message. The
destination repository must be populated with full history somehow (and
one way would have been to start it by cloning from the upstream), but if
it was empty that is alright as well, because your push made it
up-to-date. IOW, there is nothing to worry about and the system is
working as designed.
Further pushes will update it incrementally.
prev parent reply other threads:[~2008-04-07 18:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 13:02 Integration branching Kai Hendry
2008-04-07 17:41 ` Junio C Hamano
2008-04-07 18:18 ` Kai Hendry
2008-04-07 18:32 ` Avery Pennarun
2008-04-08 13:56 ` Kai Hendry
2008-04-08 18:49 ` Junio C Hamano
2008-04-08 19:01 ` Mike Hommey
2008-04-08 20:32 ` Kai Hendry
2008-04-08 20:43 ` Mike Hommey
2008-04-10 20:04 ` Mike Hommey
2008-04-07 18:44 ` Junio C Hamano [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=7vd4p1pks1.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=hendry@aplixcorp.com \
/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).