From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: git repositories for cygwin packaging - please test
Date: Tue, 17 Nov 2020 20:21:21 +0100 [thread overview]
Message-ID: <875z63u6vi.fsf@Rainer.invalid> (raw)
In-Reply-To: <a2af9a8e-6ad7-6b81-f1e7-443e5703a09d@SystematicSw.ab.ca> (Brian Inglis's message of "Mon, 16 Nov 2020 14:54:38 -0700")
Brian Inglis writes:
> Could anyone please check and advise if the attached .git/config will
> allow me to push to the playground repo and later branch for testing,
> or demo the appropriate .git/config entries or git config commands to
> do so properly?
I usually define my own repo schemes in the global (user) Git config:
--8<---------------cut here---------------start------------->8---
[url "ssh://sourceware.org/git/"]
pushInsteadOf = cygwin:
[url "ssh://cygwin@cygwin.com"]
pushInsteadOf = git://cygwin.com
[url "git://cygwin.com/git/cygwin-packages"]
InsteadOf = cygpack:
[url "ssh://cygwin@cygwin.com/git/cygwin-packages"]
pushInsteadOf = cygpack:
--8<---------------cut here---------------end--------------->8---
which then enables me to address the repo like this (each package is a
submodule in an umbrella repository:
--8<---------------cut here---------------start------------->8---
[submodule "perl"]
url = cygpack:/perl
active = true
--8<---------------cut here---------------end--------------->8---
THis also works on the command line, so if I ever want to check out
something quickly it is a lot easier to type. I never configure the
playground as a local branch, I've posted how to push to that branch and
remove it if and when you need it earlier.
> Is there any way to move tags to a later commit once pushed?
A tag is just a special commit, so as with all things Git: no, unless
you can rewrite history, i.e. force-push. Just do not tag things you
haven't published.
> Finally are there other CI jobs.cgi?params=... other than id,
> e.g. jobs.cgi?by=Brian+Inglis?
Yes, that database is now large enough that filtering would be helpful.
Probably a case of SHTDI, PTC… :-)
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2020-11-17 19:21 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-04 20:08 Jon Turney
2019-08-05 2:03 ` Ken Brown
2019-08-08 13:47 ` Andrew Schulman via cygwin-apps
2019-08-08 14:04 ` Andrew Schulman via cygwin-apps
2019-08-08 17:09 ` Ken Brown
2019-08-09 16:12 ` Jon Turney
2019-08-09 19:12 ` Ken Brown
2019-08-13 11:55 ` Jon Turney
2019-08-09 16:00 ` Jon Turney
2019-08-09 20:58 ` Brian Inglis
2019-08-13 11:55 ` Jon Turney
2019-08-19 18:36 ` Achim Gratz
2020-05-27 22:27 ` Jon Turney
2020-05-28 11:51 ` szgyg
2020-06-04 16:01 ` Ken Brown
2020-06-04 20:33 ` Brian Inglis
2020-06-09 13:26 ` Jon Turney
2020-06-09 22:44 ` Brian Inglis
2020-08-06 20:20 ` Jon Turney
2020-08-06 21:04 ` Ken Brown
2020-08-07 19:42 ` Achim Gratz
2020-08-07 22:05 ` Ken Brown
2020-08-08 4:26 ` ASSI
2020-08-16 18:05 ` Jon Turney
2020-08-23 21:01 ` Jon Turney
2020-08-26 22:00 ` Ken Brown
2020-08-30 15:00 ` Jon Turney
2020-08-30 15:22 ` Ken Brown
2020-08-30 15:46 ` Jon Turney
2020-08-30 17:25 ` Ken Brown
2020-08-30 20:06 ` Jon Turney
2020-11-12 21:30 ` Jon Turney
2020-08-30 16:44 ` ASSI
2020-08-30 20:08 ` Jon Turney
2020-10-04 10:26 ` Achim Gratz
2020-10-25 18:10 ` Jon Turney
2021-05-09 14:39 ` Jon Turney
2021-06-22 19:52 ` Jon Turney
2021-06-23 4:22 ` Brian Inglis
2022-07-05 13:12 ` Jon Turney
2023-02-18 16:21 ` Jon Turney
2023-02-18 17:43 ` Ken Brown
2023-02-18 18:40 ` Jon Turney
2020-11-16 21:54 ` Brian Inglis
2020-11-16 22:16 ` Jon Turney
2020-11-16 22:54 ` Brian Inglis
2020-11-17 19:21 ` Achim Gratz [this message]
2020-05-29 14:40 ` Alexey Sokolov
2020-06-07 15:06 ` Hamish McIntyre-Bhatty
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=875z63u6vi.fsf@Rainer.invalid \
--to=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).