On Fri, Nov 8, 2024, at 03:01, Junio C Hamano wrote: > kristofferhaugsbakk@xxxxxxxxxxxx writes: > >> +We'll discuss two cases: >> + >> +1. Taking a full backup of a repository >> +2. Transfer the history of a repository to another machine when the two >> + machines have no direct connection > > Contrasting (1) taking a backup and (2) extracting a backup later is > a very useful way to frame the problem, but then, I'd say > > 1. taking a backup, either full or incremental, of a repository > > 2. using the backup, either full or incremental, to transfer the > history of the origin repository to any repository (including > itself) without needing any other connection between the two > repositories. > > Whether a full or an incremental, the resulting bundle file can be > used as an offline medium and then later extracted elsewhere, even > if there is no direct network connection between the origin > repository and the destination repository. But you can extract in > the origin repository as well. > > But that would require a bit more surgery to the presentation order > of the text, so I do not mind deferrring it to a later and separate > series. If we were to go that route, it would be helpful to have a > paragraph to describe how you use your "full backup" bundle to recover > lost data from, though. To those of us who know what is happening, > there is not much difference between the extraction side of the > sneaker-net example, but as we framed the use in two distinct cases, > it would be helpful to make each case stand on its own. Sure. I should be able to fit in a paragraph about using that backup bundle. >> +First let's consider a full backup of the repository. The following >> +command will take a full backup of the repository in the sense that all >> +refs are included in the bundle (except `refs/stash`, i.e. the stash): > > Are you sure the "except" part is factually correct? It was in my testing/to my recollection. Hmm but I must have managed to fool myself somehow. :P
