Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Baruch Siach <baruch@tkos.co.il>
Cc: Maxim Kochetkov <fido_max@inbox.ru>,
	Julien Olivain <ju.o@free.fr>,
	"Yann E. MORIN" <yann.morin.1998@free.fr>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/postgresql: fix service runtime
Date: Sun, 04 Feb 2024 21:59:41 +0100	[thread overview]
Message-ID: <87o7cwoshu.fsf@48ers.dk> (raw)
In-Reply-To: <87il345jah.fsf@tarshish> (Baruch Siach's message of "Sun, 04 Feb 2024 17:40:14 +0200")

>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:

 > Hi Peter,
 > On Sun, Feb 04 2024, Peter Korsgaard wrote:

 >> > Applied to master, thanks.
 >> 
 >> Committed to 2023.11.x, thanks.

 > Not in 2023.11.x as of commit 7d35d445a1ae ("package/micropython: fix
 > building after dropping GIT_DIR=. workaround").

Ehh, I made a mistake - 2023.11.x doesn't have postgresql 16.x, so this
is not backported.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-02-04 20:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-17 21:07 [Buildroot] [PATCH 1/1] package/postgresql: fix service runtime Julien Olivain
2024-01-18  5:30 ` Maxim Kochetkov via buildroot
2024-01-18 18:08 ` Julien Olivain
2024-01-21  9:14 ` Yann E. MORIN
2024-02-04  9:06   ` Peter Korsgaard
2024-02-04 15:40     ` Baruch Siach via buildroot
2024-02-04 20:59       ` Peter Korsgaard [this message]
2024-02-04 20:51     ` Maxim Kochetkov via buildroot
     [not found] <20240117210756.265708-1-ju.o__23021.2395939574$1705525733$gmane$org@free.fr>
2024-01-20 15:30 ` Bernd Kuhls
2024-01-21  9:17   ` Yann E. MORIN

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=87o7cwoshu.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=baruch@tkos.co.il \
    --cc=buildroot@buildroot.org \
    --cc=fido_max@inbox.ru \
    --cc=ju.o@free.fr \
    --cc=yann.morin.1998@free.fr \
    /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