From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] cmake-3.18.0-1 and related packages
Date: Sat, 18 Jul 2020 09:01:20 +0200 [thread overview]
Message-ID: <871rl9488v.fsf@Rainer.invalid> (raw)
In-Reply-To: <63c93722-d155-0e82-ce04-2dcdddedb861@gmail.com> (Marco Atzeri via Cygwin-apps's message of "Sat, 18 Jul 2020 08:29:25 +0200")
Marco Atzeri via Cygwin-apps writes:
> I know, but it take times, specially as I will hate to lose
> the history if I port only last version
You can rewrite the git repo with filter-branch to keep the history. I
did that with my packages since I also had them in a single repo. I now
have them as submodules in a new repo, although the submodules wouldn't
strictly be necessary.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2020-07-18 7:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 20:14 Lemures Lemniscati
2020-07-17 21:13 ` Marco Atzeri
2020-07-18 1:00 ` Lemures Lemniscati
2020-07-18 6:12 ` Achim Gratz
2020-07-18 6:29 ` Marco Atzeri
2020-07-18 7:01 ` Achim Gratz [this message]
2020-07-18 8:13 ` Achim Gratz
2020-07-18 10:09 ` Lemures Lemniscati
2020-08-07 16:06 ` cmake upstream has merged cygwin patches Lemures Lemniscati
2020-08-07 19:51 ` Marco Atzeri
2020-08-08 0:47 ` Lemures Lemniscati
2020-08-10 8:17 ` Marco Atzeri
2020-08-10 13:12 ` Lemures Lemniscati
2020-11-19 22:45 ` cmake-3.19.0-1 and related packages Lemures Lemniscati
2020-11-25 22:11 ` cmake-3.19.1-1 " Lemures Lemniscati
2020-12-17 21:30 ` cmake-3.19.2-1 " Lemures Lemniscati
2021-03-27 15:58 ` Marco Atzeri
2021-03-27 22:02 ` Lemures Lemniscati
2021-03-28 2:45 ` Lemures Lemniscati
2021-03-28 7:00 ` Marco Atzeri
2021-03-28 0:12 ` Lemures Lemniscati
2021-03-28 7:02 ` Marco Atzeri
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=871rl9488v.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).