From: Hamish McIntyre-Bhatty <cygwin@hamishmb.com>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: Moving my packaging repos to gitlab
Date: Thu, 4 Aug 2022 14:44:15 +0100 [thread overview]
Message-ID: <dd3f5082-4da5-75cf-a017-db56a55a353d@hamishmb.com> (raw)
In-Reply-To: <127f12b6-f067-d7be-eadd-d64ee8cc9b2e@hamishmb.com>
On 04/08/2022 14:30, Hamish McIntyre-Bhatty wrote:
> On 04/08/2022 13:50, Adam Dinwoodie wrote:
>> On Thu, 4 Aug 2022 at 11:13, Hamish McIntyre-Bhatty
>> <cygwin-ltj9jUse+BtWk0Htik3J/w@public.gmane.org> wrote:
>>> I'm considering moving my Cygwin packaging repos over to gitlab, as I
>>> find it easier to organise and use. Are there any potential
>>> problems/lost features from me doing this?
>>
>> Where are your repos currently stored?
>>
>> Personally, I keep repos for all the projects I maintain on GitHub; I
>> mirror them to https://cygwin.com/git-cygwin-packages/ whenever I
>> create a release, in the name of helping other folks find the
>> packaging code, but the repos I actually work with day-to-day are the
>> GitHub ones.
>>
>
> I have them at: https://cygwin.com/git-cygwin-packages/ currently.
>
> Good idea, I'll just mirror to https://cygwin.com/git-cygwin-packages/
> and no discoverability or potentially-useful features are lost.
>
> Hamish
>
Also, for the sake of consistency between repos, I now use "main" as my
default branch. Can I somehow change this for the cygwin.com git for my
repos too?
Hamish
prev parent reply other threads:[~2022-08-04 13:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 10:12 Hamish McIntyre-Bhatty
2022-08-04 12:50 ` Adam Dinwoodie
2022-08-04 13:30 ` Hamish McIntyre-Bhatty
2022-08-04 13:44 ` Hamish McIntyre-Bhatty [this message]
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=dd3f5082-4da5-75cf-a017-db56a55a353d@hamishmb.com \
--to=cygwin@hamishmb.com \
--cc=cygwin-apps@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).