Remove warning that repack only works on non-promisor packfiles

[TaoK]

The git-repack doc clearly states that it does operate on promisor packfiles (in a separate partition), with "-a" specified. Presumably the statements here are outdated, as they feature from the first doc in 2017 (and the repack support was added in 2018)

cc: Taylor Blau me@ttaylorr.com
cc: Jonathan Tan jonathantanmy@google.com

[gitgitgadget]

Welcome to GitGitGadget

Hi @TaoK, and welcome to GitGitGadget, the GitHub App to send patch series to the Git mailing list from GitHub Pull Requests.

Please make sure that your Pull Request has a good description, as it will be used as cover letter.

Also, it is a good idea to review the commit messages one last time, as the Git project expects them in a quite specific form:

• the lines should not exceed 76 columns,
• the first line should be like a header and typically start with a prefix like "tests:" or "revisions:" to state which subsystem the change is about, and
• the commit messages' body should be describing the "why?" of the change.
• Finally, the commit messages should end in a Signed-off-by: line matching the commits' author.

It is in general a good idea to await the automated test ("Checks") in this Pull Request before contributing the patches, e.g. to avoid trivial issues such as unportable code.

Contributing the patches

Before you can contribute the patches, your GitHub username needs to be added to the list of permitted users. Any already-permitted user can do that, by adding a comment to your PR of the form /allow. A good way to find other contributors is to locate recent pull requests where someone has been /allowed:

• Search: is:pr is:open "/allow"

Both the person who commented /allow and the PR author are able to /allow you.

An alternative is the channel #git-devel on the Libera Chat IRC network:

<newcontributor> I've just created my first PR, could someone please /allow me? https://github.com/gitgitgadget/git/pull/12345
<veteran> newcontributor: it is done
<newcontributor> thanks!

Once on the list of permitted usernames, you can contribute the patches to the Git mailing list by adding a PR comment /submit.

If you want to see what email(s) would be sent for a /submit request, add a PR comment /preview to have the email(s) sent to you. You must have a public GitHub email address for this.

After you submit, GitGitGadget will respond with another comment that contains the link to the cover letter mail in the Git mailing list archive. Please make sure to monitor the discussion in that thread and to address comments and suggestions (while the comments and suggestions will be mirrored into the PR by GitGitGadget, you will still want to reply via mail).

If you do not want to subscribe to the Git mailing list just to be able to respond to a mail, you can download the mbox from the Git mailing list archive (click the (raw) link), then import it into your mail program. If you use GMail, you can do this via:

curl -g --user "<EMailAddress>:<Password>" \
    --url "imaps://imap.gmail.com/INBOX" -T /path/to/raw.txt

To iterate on your change, i.e. send a revised patch or patch series, you will first want to (force-)push to the same branch. You probably also want to modify your Pull Request description (or title). It is a good idea to summarize the revision by adding something like this to the cover letter (read: by editing the first comment on the PR, i.e. the PR description):

Changes since v1:
- Fixed a typo in the commit message (found by ...)
- Added a code comment to ... as suggested by ...
...

To send a new iteration, just add another PR comment with the contents: /submit.

Need help?

New contributors who want advice are encouraged to join git-mentoring@googlegroups.com, where volunteers who regularly contribute to Git are willing to answer newbie questions, give advice, or otherwise provide mentoring to interested contributors. You must join in order to post or view messages, but anyone can join.

You may also be able to find help in real time in the developer IRC channel, #git-devel on Libera Chat. Remember that IRC does not support offline messaging, so if you send someone a private message and log out, they cannot respond to you. The scrollback of #git-devel is archived, though.

[gitgitgadget]

There are issues in commit 70c4979:
First line of commit message is too long (> 76 columns): Remove warning that repack only works on non-promisor packfiles, and corresponding future work entry
Commit not signed off

[dscho]

/allow

[gitgitgadget]

User TaoK is now allowed to use GitGitGadget.

WARNING: TaoK has no public email address set on GitHub

[gitgitgadget]

User TaoK already allowed to use GitGitGadget.

[TaoK]

/preview

[gitgitgadget]

Error: Could not determine public email of TaoK

[TaoK]

/submit

[gitgitgadget]

Submitted as pull.968.git.1622634446643.gitgitgadget@gmail.com

To fetch this version into FETCH_HEAD:

git fetch https://github.com/gitgitgadget/git pr-968/TaoK/patch-1-v1

To fetch this version to local tag pr-968/TaoK/patch-1-v1:

git fetch --no-tags https://github.com/gitgitgadget/git tag pr-968/TaoK/patch-1-v1

[gitgitgadget]

On the Git mailing list, Taylor Blau wrote (reply to this):

On Wed, Jun 02, 2021 at 11:47:26AM +0000, Tao Klerks via GitGitGadget wrote:
> From: Tao Klerks <tao@klerks.biz>
>
> The git-repack doc clearly states that it *does* operate on promisor
> packfiles (in a separate partition), with "-a" specified. Presumably
> the statements here are outdated, as they feature from the first doc
> in 2017 (and the repack support was added in 2018)

Yeah, this all originally comes from Jeff H.'s design document in
637fc4467e (partial-clone: design doc, 2017-12-14), but probably should
have been updated in 5d19e8138d (repack: repack promisor objects if -a
or -A is set, 2018-08-08).

This looks good to me, but I'll add Jonathan Tan to the CC list to
double check.

  Reviewed-by: Taylor Blau <me@ttaylorr.com>

Thanks,
Taylor

[gitgitgadget]

User Taylor Blau <me@ttaylorr.com> has been added to the cc: list.

[gitgitgadget]

On the Git mailing list, Jonathan Tan wrote (reply to this):

> On Wed, Jun 02, 2021 at 11:47:26AM +0000, Tao Klerks via GitGitGadget wrote:
> > From: Tao Klerks <tao@klerks.biz>
> >
> > The git-repack doc clearly states that it *does* operate on promisor
> > packfiles (in a separate partition), with "-a" specified. Presumably
> > the statements here are outdated, as they feature from the first doc
> > in 2017 (and the repack support was added in 2018)
> 
> Yeah, this all originally comes from Jeff H.'s design document in
> 637fc4467e (partial-clone: design doc, 2017-12-14), but probably should
> have been updated in 5d19e8138d (repack: repack promisor objects if -a
> or -A is set, 2018-08-08).
> 
> This looks good to me, but I'll add Jonathan Tan to the CC list to
> double check.
> 
>   Reviewed-by: Taylor Blau <me@ttaylorr.com>

Thanks, Taylor. Yes, the patch is correct.

[gitgitgadget]

User Jonathan Tan <jonathantanmy@google.com> has been added to the cc: list.

[gitgitgadget]

On the Git mailing list, Junio C Hamano wrote (reply to this):

Jonathan Tan <jonathantanmy@google.com> writes:

>> On Wed, Jun 02, 2021 at 11:47:26AM +0000, Tao Klerks via GitGitGadget wrote:
>> > From: Tao Klerks <tao@klerks.biz>
>> >
>> > The git-repack doc clearly states that it *does* operate on promisor
>> > packfiles (in a separate partition), with "-a" specified. Presumably
>> > the statements here are outdated, as they feature from the first doc
>> > in 2017 (and the repack support was added in 2018)
>> 
>> Yeah, this all originally comes from Jeff H.'s design document in
>> 637fc4467e (partial-clone: design doc, 2017-12-14), but probably should
>> have been updated in 5d19e8138d (repack: repack promisor objects if -a
>> or -A is set, 2018-08-08).
>> 
>> This looks good to me, but I'll add Jonathan Tan to the CC list to
>> double check.
>> 
>>   Reviewed-by: Taylor Blau <me@ttaylorr.com>
>
> Thanks, Taylor. Yes, the patch is correct.

Thanks, all of you.  Will queue.

[gitgitgadget]

This branch is now known as tk/partial-clone-repack-doc.

[gitgitgadget]

This patch series was integrated into seen via git@e5c5e7f.

[gitgitgadget]

This patch series was integrated into seen via git@136b5e5.

[gitgitgadget]

This patch series was integrated into seen via git@c0b28ff.

[gitgitgadget]

This patch series was integrated into seen via git@b37494b.

[gitgitgadget]

This patch series was integrated into seen via git@2315a6d.

[gitgitgadget]

There was a status update in the "New Topics" section about the branch tk/partial-clone-repack-doc on the Git mailing list:

Docfix.

Will merge to 'next'.

[gitgitgadget]

There was a status update in the "Cooking" section about the branch tk/partial-clone-repack-doc on the Git mailing list:

Docfix.

Will merge to 'next'.

[gitgitgadget]

This patch series was integrated into seen via git@9395082.

[gitgitgadget]

There was a status update in the "Cooking" section about the branch tk/partial-clone-repack-doc on the Git mailing list:

Docfix.

Will merge to 'next'.

[gitgitgadget]

This patch series was integrated into seen via git@9893011.

[gitgitgadget]

There was a status update in the "Cooking" section about the branch tk/partial-clone-repack-doc on the Git mailing list:

Docfix.

Will merge to 'next'.

[gitgitgadget]

This patch series was integrated into seen via git@1e0fd98.

[gitgitgadget]

There was a status update in the "Cooking" section about the branch tk/partial-clone-repack-doc on the Git mailing list:

Docfix.

Will merge to 'next'.

[gitgitgadget]

This patch series was integrated into seen via git@e160ae3.

[gitgitgadget]

There was a status update in the "Cooking" section about the branch tk/partial-clone-repack-doc on the Git mailing list:

Docfix.

Will merge to 'next'.

[gitgitgadget]

This patch series was integrated into seen via git@fe4c628.

[gitgitgadget]

This patch series was integrated into next via git@fe4c628.

[gitgitgadget]

There was a status update in the "Cooking" section about the branch tk/partial-clone-repack-doc on the Git mailing list:

Docfix.

Will merge to 'master'.

[gitgitgadget]

This patch series was integrated into seen via git@0fff937.

[gitgitgadget]

This patch series was integrated into seen via git@4009809.

[gitgitgadget]

This patch series was integrated into next via git@4009809.

[gitgitgadget]

This patch series was integrated into master via git@4009809.

[gitgitgadget]

Closed via 4009809.