Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] Signal-Desktop: update to 5.0.0
Date: Tue, 27 Apr 2021 04:23:19 +0200	[thread overview]
Message-ID: <20210427022319.gmvhDYpTLFgaoQC1oBfjS9h2pESKRKalYEKGVD3d0hw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30505@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 777 bytes --]

New review comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/pull/30505#discussion_r620800327

Comment:
Man page says

```
DESCRIPTION
Perform the following actions to ensure that Git LFS is setup properly:

○
    Set up the clean and smudge filters under the name "lfs" in the global Git config.
○
    Install a pre-push hook to run git-lfs-pre-push(1) for the current repository, if run from inside one. If "core.hooksPath" is configured in any Git configuration (and supported, i.e., the installed Git version is at least 2.9.0), then the pre-push hook will be installed to that directory instead.
```

@void-linux/pkg-committers is this ok or should we change the position of the git config directory or something?

  parent reply	other threads:[~2021-04-27  2:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-26  3:21 [PR PATCH] " ScrelliCopter
2021-04-26 19:20 ` [PR REVIEW] " ericonr
2021-04-26 23:56 ` ScrelliCopter
2021-04-27  2:23 ` ericonr [this message]
2021-04-27  2:23 ` ericonr
2021-04-27  2:41 ` q66
2021-04-27  5:28 ` [PR PATCH] [Updated] " ScrelliCopter
2021-05-02 23:13 ` kwshi
2021-06-24 22:34 ` ScrelliCopter
2021-06-24 22:34 ` [PR PATCH] [Closed]: " ScrelliCopter
2021-05-05 17:52 [PR PATCH] " lane-brain
2021-05-05 19:13 ` [PR REVIEW] " ericonr
2021-05-05 19:27 ` lane-brain
2021-05-05 19:46 ` lane-brain

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=20210427022319.gmvhDYpTLFgaoQC1oBfjS9h2pESKRKalYEKGVD3d0hw@z \
    --to=ericonr@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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).