From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: meta@public-inbox.org
Subject: Re: RFE: default hooks for git repositories
Date: Thu, 7 Mar 2019 02:42:41 +0000
Message-ID: <20190307024241.lhlf65uqsbjywfv3@dcvr> (raw)
In-Reply-To: <20190306170302.GA21727@chatter.qube.local>
Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> Hello:
>
> Since V2 creates git shards automatically, I suggest there should be a way
> to tell it to install some set of default hooks in all new git repos it
> creates. The easiest would be by using a skel dir and specifying it in
> PI_CONFIG:
>
> [publicinbox]
> githooksskel=/usr/share/public-inbox/hooks
Seems reasonable. Though "gitInitTemplateDir" would probably be
easier-to-implement and cover hooks. This should let us avoid
creating needless "branches" directories and "info/exclude"
files, as well.
Curious, what hooks do you use? I've never used any.
> We currently do it via a cronjob, but unless we run it very frequently,
> there's a delay between when a new shard is created and when we add the
> hooks to it.
I've also been thinking of a way to get mirrors to automatically
know about new epochs, too. Maybe submodules can be used...
Note: I prefer the "epoch" term for the $N.git dirs over "shard"
to disambiguate it from the Xapian partitioning we do.
next prev parent reply other threads:[~2019-03-07 2:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 17:03 Konstantin Ryabitsev
2019-03-07 2:42 ` Eric Wong [this message]
2019-03-08 23:01 ` Eric Wong
2019-03-18 23:11 ` Eric Wong
2019-04-01 15:41 ` Konstantin Ryabitsev
2019-04-01 18:04 ` Eric Wong
2019-04-05 17:43 ` Konstantin Ryabitsev
2019-04-05 20:07 ` Eric Wong
2019-04-06 4:52 ` Eric Wong
2019-04-15 18:29 ` [PATCH] TODO: add an item for hooks support Eric Wong
2019-04-29 0:33 ` update on grokmirror integration [was: [PATCH] TODO: add an item for hooks support] Eric Wong
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190307024241.lhlf65uqsbjywfv3@dcvr \
--to=e@80x24.org \
--cc=konstantin@linuxfoundation.org \
--cc=meta@public-inbox.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
user/dev discussion of public-inbox itself
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://public-inbox.org/meta
git clone --mirror http://czquwvybam4bgbro.onion/meta
git clone --mirror http://hjrcffqmbrq6wope.onion/meta
git clone --mirror http://ou63pmih66umazou.onion/meta
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V1 meta meta/ https://public-inbox.org/meta \
meta@public-inbox.org
public-inbox-index meta
Example config snippet for mirrors.
Newsgroups are available over NNTP:
nntp://news.public-inbox.org/inbox.comp.mail.public-inbox.meta
nntp://ou63pmih66umazou.onion/inbox.comp.mail.public-inbox.meta
nntp://czquwvybam4bgbro.onion/inbox.comp.mail.public-inbox.meta
nntp://hjrcffqmbrq6wope.onion/inbox.comp.mail.public-inbox.meta
nntp://news.gmane.io/gmane.mail.public-inbox.general
note: .onion URLs require Tor: https://www.torproject.org/
code repositories for the project(s) associated with this inbox:
https://80x24.org/public-inbox.git
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git