From: "R. Lemos" <rslemos@gmail.com>
To: git@vger.kernel.org
Subject: Empty bundles are not useless
Date: Tue, 14 Jul 2020 10:58:50 -0300 [thread overview]
Message-ID: <CAM6_cxzzWJQpw9akM=JZAnZ0LrPBCPX+q1da8_24vOJexCKeHA@mail.gmail.com> (raw)
When working disconnected (sending bundles back and forth) it is
useful to make bundles like this:
$ git bundle create /tmp/my.bundle master ^disconnected/master
This way I pack all new commits since the last updated from
`disconnected` remote.
But if my local copy is up-to-date, git bundle refuses to create an
empty bundle, since there are no commits to send.
However it would be nice to at least send the information that my
local branch `master` is up-to-date. That is, the bundle would just
convey that my local `master` points to a given commit (even though
this commit is already on the remote site). This way, when I upload
this bundle to the remote site, then bring back changes made there,
the remote site will know which commits I already have.
Thanks.
Rodrigo Lemos
next reply other threads:[~2020-07-14 13:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 13:58 R. Lemos [this message]
2020-07-14 21:47 ` Empty bundles are not useless Johannes Schindelin
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='CAM6_cxzzWJQpw9akM=JZAnZ0LrPBCPX+q1da8_24vOJexCKeHA@mail.gmail.com' \
--to=rslemos@gmail.com \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).