From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package/glibc: switch to using the maintenance branch
Date: Sat, 28 Oct 2017 15:22:10 +0200 [thread overview]
Message-ID: <20171028132210.GC3280@scaer> (raw)
In-Reply-To: <20171028151814.2c1b716e@windsurf>
Thomas, Romain, All,
On 2017-10-28 15:18 +0200, Thomas Petazzoni spake thusly:
> On Sat, 28 Oct 2017 12:58:18 +0200, Romain Naour wrote:
> > > I would also add something like:
> > >
> > > Before bumping the version, first verify that the sha1 really
> > > exists on the official git tree.
> >
> > You meant "the sha1 really exists on the git mirror tree" I guess :)
>
> No, I think Yann really meant "in the official tree". The idea is that
> we shouldn't use a git hash from a "random" github mirror if this git
> hash doesn't exist in the official Git repository of the project.
Exactly, yes.
Regards,
Yann E. MORIN.
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2017-10-28 13:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 14:30 [Buildroot] [PATCH v2] package/glibc: switch to using the maintenance branch Romain Naour
2017-10-28 9:55 ` Yann E. MORIN
2017-10-28 10:58 ` Romain Naour
2017-10-28 13:18 ` Thomas Petazzoni
2017-10-28 13:22 ` Yann E. MORIN [this message]
2017-10-28 10:06 ` Yann E. MORIN
2017-10-28 11:16 ` Romain Naour
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=20171028132210.GC3280@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.