Github messages for mblaze
 help / color / mirror / Atom feed
From: mblaze-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] Automatically update VERSION file on release
Date: Sat, 01 Feb 2020 16:48:23 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-170@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 314 bytes --]

There is a new pull request by 0leynikov against master on the mblaze repository

https://github.com/0leynikov/mblaze version-bump
https://github.com/leahneukirchen/mblaze/pull/170

Automatically update VERSION file on release


A patch file from https://github.com/leahneukirchen/mblaze/pull/170.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-version-bump-170.patch --]
[-- Type: text/x-diff, Size: 758 bytes --]

From dd796deb842af478aee6164973b8d589e7d89f00 Mon Sep 17 00:00:00 2001
From: Alexander Oleynikov <oleynikov@posteo.li>
Date: Sat, 1 Feb 2020 15:45:17 +0000
Subject: [PATCH] GNUmakefile: update VERSION on release

---
 GNUmakefile | 1 +
 VERSION     | 2 +-
 2 files changed, 2 insertions(+), 1 deletion(-)

diff --git a/GNUmakefile b/GNUmakefile
index 8ce7370..96412a5 100644
--- a/GNUmakefile
+++ b/GNUmakefile
@@ -68,6 +68,7 @@ install: FRC all
 
 release:
 	VERSION=$$(git describe --tags | sed 's/^v//;s/-[^.]*$$//') && \
+	printf "$$VERSION\n" > VERSION && \
 	git archive --prefix=mblaze-$$VERSION/ -o mblaze-$$VERSION.tar.gz HEAD
 
 sign:
diff --git a/VERSION b/VERSION
index 4b9fcbe..5a2a580 100644
--- a/VERSION
+++ b/VERSION
@@ -1 +1 @@
-0.5.1
+0.6

             reply	other threads:[~2020-02-01 15:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-01 15:48 mblaze-github [this message]
2020-02-02 13:18 ` mblaze-github
2020-02-02 14:53 ` [PR PATCH] [Closed]: " mblaze-github
2020-02-02 14:53 ` mblaze-github
2020-02-02 16:49 ` mblaze-github

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=gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-170@inbox.vuxu.org \
    --to=mblaze-github@inbox.vuxu.org \
    --cc=ml@inbox.vuxu.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 NNTP newsgroup(s).