Re: 'git maintenance' won't work on bare repos
- From
- Clement Moyroud <clement.moyroud@gmail.com>
- Date
- Feb 23, 2021, 15:31 UTC
- Message-ID
- <CABXAcUwdpJa1osz=9xarVgbP9wFK82rbx8J1vk-EZEA5x25ffQ@mail.gmail.com>
- In-Reply-To
- <CAPig+cSvYLMtML5ya4GR30-nfNNt19okLjchkkdhdzAEB19H4g@mail.gmail.com>
On Mon, Feb 22, 2021 at 9:03 PM Eric Sunshine <sunshine@sunshineco.com> wrote:
Show 13 quoted lines
> > 1. 'git config --global --get maintenance.repo' returns '.' > > 2. There are no Crontab entries inserted. > > I can confirm that problem 1 is a bug. However, I am unable to > reproduce problem 2. > > Note that the crontab entry won't be created until you run `git > maintenance start`. Is it possible that you are forgetting that step? > (Be aware that `git maintenance start` will show a misleading "no > crontab for <user>" message if you don't already have a crontab file, > but the crontab entry will be created nevertheless, as evidenced by > `crontab -l`.) >
My bad. I misread the manpage, and didn't try to run 'git maintenance start' on the bare repo, since the first step did not look right.
> I have a patch which fixes the problem with the bare repo path being > incorrectly registered as ".", but I still need to create a regression > test for it.
I saw the patch, thanks for the quick fix!