git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Empty bundles are not useless

From
RLR. Lemos <rslemos@gmail.com>
Date
Jul 14, 2020, 13:58 UTC
Message-ID
<CAM6_cxzzWJQpw9akM=JZAnZ0LrPBCPX+q1da8_24vOJexCKeHA@mail.gmail.com>

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: Johannes Schindelin
Message 1 of 2 in “Empty bundles are not useless”
  1. R. LemosJul 14, 2020
  2. Johannes SchindelinJul 14, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.