From: Erwin Waterlander <waterlan@xs4all.nl>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: cygwin-apps@cygwin.com
Subject: Re: How to create am initial cygwin package git repo?
Date: Sun, 18 Oct 2020 16:31:59 +0200 [thread overview]
Message-ID: <f1b6a859c0cf2fc9e9cb3acf65144c31@xs4all.nl> (raw)
In-Reply-To: <87lfg37m39.fsf@Rainer.invalid>
Achim Gratz schreef op 2020-10-18 14:30:
> Erwin Waterlander writes:
>> The text on https://cygwin.com/packaging/repos.html is unclear. The
>> page says that the repo is lazily created on the first push. It should
>> say that you first clone it with this command:
>>
>> git clone
>> ssh://cygwin-rDBXBDvO6BXQT0dZR+AlfA@public.gmane.org/git/cygwin-packages/packagename.git
>>
>> and then do a first push
>
> It shouldn't say that, because it works just as well when doing a git
> init locally (or using an existing local repo) and then pushing to the
> remote (which you also need to explicitly specify the first time you
> use
> it). In fact that's the sane way to do it when you already have local
> history.
>
> For your packages, please check
>
> https://cygwin.com/cgi-bin2/jobs.cgi
>
> and add the necessary BUILD_REQUIRES to make them build on the CI.
> It's
> recommended to iterate on the playground branch, which you can
> force-push to (i.e. you can throw away commits that have not worked
> out)
> and delete if no longer needed after having pushed the cleaned-up
> version to the master branch.
Thanks!
This information should be in the Cygwin Package Contributor's Guide.
best regards,
Erwin
next prev parent reply other threads:[~2020-10-18 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-18 10:03 Erwin Waterlander
2020-10-18 11:39 ` Erwin Waterlander
2020-10-18 12:30 ` Achim Gratz
2020-10-18 14:31 ` Erwin Waterlander [this message]
2020-10-25 16:09 ` Jon Turney
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=f1b6a859c0cf2fc9e9cb3acf65144c31@xs4all.nl \
--to=waterlan@xs4all.nl \
--cc=Stromeko@nexgo.de \
--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).