From: Samuel Williams <space.ship.traveller@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Shallow Push?
Date: Wed, 22 Jul 2015 19:27:59 +1200 [thread overview]
Message-ID: <CAHkN8V8hcdBD1oBYEpf74rsY2mpzxE08v+czue9ORzDB8ZGn=w@mail.gmail.com> (raw)
In-Reply-To: <xmqqmw2iardi.fsf@gitster.dls.corp.google.com>
> What is the receiving repository expected to have? Does it have
everything that is required to checkout the back-then latest HEAD
the last time a push was made into it, and you are pushing an
update?
Yes, something like that
On 9 April 2015 at 15:54, Junio C Hamano <gitster@pobox.com> wrote:
> Samuel Williams <space.ship.traveller@gmail.com> writes:
>
>> Is it possible to only push what is required to checkout the latest HEAD?
>
> What is the receiving repository expected to have? Does it have
> everything that is required to checkout the back-then latest HEAD
> the last time a push was made into it, and you are pushing an
> update?
>
prev parent reply other threads:[~2015-07-22 7:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 15:08 Shallow Push? Samuel Williams
2015-04-09 3:54 ` Junio C Hamano
2015-07-22 7:27 ` Samuel Williams [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='CAHkN8V8hcdBD1oBYEpf74rsY2mpzxE08v+czue9ORzDB8ZGn=w@mail.gmail.com' \
--to=space.ship.traveller@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).