From: Naga Malleswari <nagamalli@riseup.net>
To: Jonathan Brielmaier <jonathan.brielmaier@web.de>, 40356@debbugs.gnu.org
Cc: "Danny Milosavljevic" <dannym@scratchpost.org>,
"Gábor Boskovits" <boskovits@gmail.com>
Subject: [bug#40356] Update meson package Description in build-tools.scm
Date: Wed, 1 Apr 2020 11:24:09 +0530 [thread overview]
Message-ID: <5d69d873-3380-9779-143b-e8fbfcc1f1b8@riseup.net> (raw)
In-Reply-To: <3b9eae2e-9f13-0eb6-9d52-fae632b6e39b@web.de>
Hi
On 01/04/20 4:13 am, Jonathan Brielmaier wrote:
> On 31.03.20 22:10, Naga Malleswari wrote:
>> Hi
>>
>>
>> I guess i am following the correct method.
> Hello Naga,
>
> yes, you are following the correct method for submitting patches.
> Although we already have meson at version 0.53.2, just not in the master
> branch yet.
>
> It is only in the core-updates branch:
> https://git.savannah.gnu.org/cgit/guix.git/commit/?h=core-updates&id=275f874958ddbbb68ddce93be2cb65bec7ac1bd4
Thank you.
I understood the process. I realize that i have done the same changes
like the patch you have given as well.
This means i can go ahead with similar process to update any packages on
the basis of the manual you shared below.
I suppose i cannot update Polari in gnome.scm as well until the
core-updates branch merges with master.
>
> This is due to the fact that many (some thousand) packages depend on
> meson. So if we update meson, we have to rebuild all those packages.
> This should not happen on the master branch. For more information see
> point 8 at
> http://guix.gnu.org/manual/en/html_node/Submitting-Patches.html#Submitting-Patches
I now understood why this happened. Ealier when i went through this
manual i couldnt get the essence of it.
Do I have to close this issue as it is no longer relavent.
>
> Good night
> Jonathan
>
>
--
Regards
NagaMalli
next prev parent reply other threads:[~2020-04-01 5:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 20:10 [bug#40356] Update meson package Description in build-tools.scm Naga Malleswari
2020-03-31 22:43 ` Jonathan Brielmaier
2020-04-01 5:54 ` Naga Malleswari [this message]
2020-11-21 9:50 ` bug#40356: " Christopher Baines
2020-05-15 8:31 ` [bug#40356] " Jonathan Brielmaier
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5d69d873-3380-9779-143b-e8fbfcc1f1b8@riseup.net \
--to=nagamalli@riseup.net \
--cc=40356@debbugs.gnu.org \
--cc=boskovits@gmail.com \
--cc=dannym@scratchpost.org \
--cc=jonathan.brielmaier@web.de \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).