From: Derek Stevens <nilix@nilfm.cc>
To: Jamie Couture <jamie.couture@gmail.com>
Cc: cgit@lists.zx2c4.com
Subject: Re: patches: main as default branch, go gettable
Date: Sat, 8 Jan 2022 17:00:26 -0700 [thread overview]
Message-ID: <20220109000026.h2vnxbyjnczpha22@ksatrya.siroonian.local> (raw)
In-Reply-To: <CAH-DoZ74FOrn=H0A1EtoEj+f_z7UoRXL2Rq4+GcvEosPoQXrBQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1587 bytes --]
Thanks Jamie, I just sent them using that method.
As for the default branch name, I agree that using the default branch of the git-config and per-repo overrides would be preferrable, but I just changed the hardcoded fallback from "master" to "main" in case nothing else was found. I could probably do some legwork in the future to try and get it pulled from the actual git config as well...
Cheers!
Derek
------original message------
From: Jamie Couture <jamie.couture@gmail.com>
Date: Sat, Jan 08, 2022 at 03:46:33PM MST
>Hi Derek,
>
>Can you retry sending these using git send-email? Don't forget to add your
>sign-off to the commit log as well.
>
>https://git-scm.com/docs/git-send-email
>
>
>As for the default branch change, I suspect people may want this feature
>configurable based on their configuration. I'm thinking either derived from
>your git config file or granularly via an override in the repo-list
>configuration file. Ideally, obtain the default branch name from config of
>each repo.
>
>
>Thanks,
>
>On Sat, Jan 8, 2022 at 5:28 PM Derek Stevens <nilix@nilfm.cc> wrote:
>
>> Hello CGit folk!
>>
>> I use cgit for my own git server and have made some minor modifications
>> that might be of interest.
>>
>> The first is the trivial change to assume main as the default branch name,
>> as this is the new standard in git.
>>
>> The second and more interesting is to add a <meta> attribute to make a
>> repository go-gettable.
>>
>> Both patches are attached; Happy new year and happy hacking!
>>
>> Cheers,
>> Derek
>>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-01-09 0:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 22:28 Derek Stevens
[not found] ` <CAH-DoZ74FOrn=H0A1EtoEj+f_z7UoRXL2Rq4+GcvEosPoQXrBQ@mail.gmail.com>
2022-01-09 0:00 ` Derek Stevens [this message]
2022-01-09 16:13 ` Reto
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=20220109000026.h2vnxbyjnczpha22@ksatrya.siroonian.local \
--to=nilix@nilfm.cc \
--cc=cgit@lists.zx2c4.com \
--cc=jamie.couture@gmail.com \
/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).