From: Yuri D'Elia <wavexx@thregr.org>
To: git@vger.kernel.org
Subject: [ANNOUNCE] git-assembler 1.4 released
Date: Thu, 18 May 2023 13:05:52 +0200 [thread overview]
Message-ID: <877ct5uc6b.fsf@wavexx.thregr.org> (raw)
git-assembler 1.4 was just released. This version brings full worktree
support. Checked-out branches are correctly updated/rebuilt from any
tree when referenced in the current assembly. This allows the developer
to use worktrees as automated "patch testing ground" across multiple
mainlines, either for local use or CI.
git-assembler can perform automatic merge and rebase operations
following a simple declarative script. Like "make", but for branches.
You can use git-assembler to create a branch which is a combination of
patches using various strategies and keep it always updated.
Documentation and links are available at:
https://www.thregr.org/~wavexx/software/git-assembler/
The source itself:
https://gitlab.com/wavexx/git-assembler
reply other threads:[~2023-05-18 11:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=877ct5uc6b.fsf@wavexx.thregr.org \
--to=wavexx@thregr.org \
--cc=git@vger.kernel.org \
/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).