mbox series

[0/4] Documentation/git-bundle.txt: promote --all for full backup

Message ID cover.1729451376.git.code@khaugsbakk.name (mailing list archive)
Headers show
Series Documentation/git-bundle.txt: promote --all for full backup | expand

Message

Kristoffer Haugsbakk Oct. 20, 2024, 7:14 p.m. UTC
From: Kristoffer Haugsbakk <code@khaugsbakk.name>

The documentation for git-bundle(1) now properly covers `--all`, the
option that can be used to package all refs.  A "Discussions" section
has also been added to address the naive backup strategy of copying a
Git repository manually.

---

The part above was for the-topic-summary.

And that about summarizes it.

Okay well.  I was prompted by SO questions like this one:

    https://stackoverflow.com/questions/5578270/fully-backup-a-git-repo

I then compared VonC’s answer to the man page.  The first thing I
noticed was that `--all` wasn’t in the synopsis.  Then one patch lead to
another.

+Cc is just `./contrib/contacts/git-contacts` minus Junio.

Cheers

Kristoffer Haugsbakk (4):
  Documentation/git-bundle.txt: mention --all in Synopsis
  Documentation/git-bundle.txt: mention full backup example
  Documentation/git-bundle.txt: mention --all in spec. refs
  Documentation/git-bundle.txt: discuss naïve backups

 Documentation/git-bundle.txt | 21 +++++++++++++++++++--
 builtin/bundle.c             |  2 +-
 2 files changed, 20 insertions(+), 3 deletions(-)


base-commit: 34b6ce9b30747131b6e781ff718a45328aa887d0

Comments

Taylor Blau Oct. 21, 2024, 9:36 p.m. UTC | #1
On Sun, Oct 20, 2024 at 09:14:58PM +0200, kristofferhaugsbakk@fastmail.com wrote:
> +Cc is just `./contrib/contacts/git-contacts` minus Junio.

Ævar, who you CC'd here is currently inactive[^1], so it may be unlikely
that we receive a response from him.

> Kristoffer Haugsbakk (4):
>   Documentation/git-bundle.txt: mention --all in Synopsis
>   Documentation/git-bundle.txt: mention full backup example
>   Documentation/git-bundle.txt: mention --all in spec. refs
>   Documentation/git-bundle.txt: discuss naïve backups

As you suggested elsewhere in the thread, I dropped the first patch from
this series, but the other three look good. I had a small note on the
second patch (first after dropping), but let me know if you plan to
address it or not.

Thanks,
Taylor

[^1]: ...and missed. It would be nice to see you back sometime, Ævar.
Taylor Blau Oct. 22, 2024, 5:29 p.m. UTC | #2
On Sun, Oct 20, 2024 at 09:14:58PM +0200, kristofferhaugsbakk@fastmail.com wrote:
> From: Kristoffer Haugsbakk <code@khaugsbakk.name>
>
> The documentation for git-bundle(1) now properly covers `--all`, the
> option that can be used to package all refs.  A "Discussions" section
> has also been added to address the naive backup strategy of copying a
> Git repository manually.

When applying to 'seen' last night, it looks like this topic caused some
breakage here:

    https://github.com/git/git/actions/runs/11449483611/job/31855169149#step:4:144

Would you mind taking a look, Kristoffer?

Thanks,
Taylor
Kristoffer Haugsbakk Oct. 22, 2024, 9:22 p.m. UTC | #3
On Tue, Oct 22, 2024, at 19:29, Taylor Blau wrote:
> On Sun, Oct 20, 2024 at 09:14:58PM +0200,
> kristofferhaugsbakk@fastmail.com wrote:
>> From: Kristoffer Haugsbakk <code@khaugsbakk.name>
>>
>> The documentation for git-bundle(1) now properly covers `--all`, the
>> option that can be used to package all refs.  A "Discussions" section
>> has also been added to address the naive backup strategy of copying a
>> Git repository manually.
>
> When applying to 'seen' last night, it looks like this topic caused some
> breakage here:
>
>
> https://github.com/git/git/actions/runs/11449483611/job/31855169149#step:4:144
>
> Would you mind taking a look, Kristoffer?

Ah, thanks for the heads up.  I’ll take a look at it.

(’Tis a shame when we neglect to run five-second-run linters before
sending out)