From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] parted: fix minor()/major() build failure due to glibc 2.28
Date: Mon, 10 Sep 2018 14:08:23 +0200 [thread overview]
Message-ID: <20180910140823.2794d1da@windsurf> (raw)
In-Reply-To: <CAGm1_ktVLoCsxUou+ax6qEc0y8mbOj7FBhid4_vjz9AtHaueqA@mail.gmail.com>
Hello,
On Mon, 10 Sep 2018 13:46:07 +0200, Yegor Yefremov wrote:
> > I still can't find upstream commits in general, I think I don't know
> > enough some tool you use or I don't know the best way to find them.
> > Can you point me some hint for this?
> > Maybe using git in certain way, or checking open PR on various git in a
> > certain way in repositories etc.
>
> Install "tig" and invoke:
>
> tig blame libparted/arch/linux.c
What I typically do is just:
git log -p <file>
and then use the search to find if there is a commit that looks
relevant.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-09-10 12:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-09 17:29 [Buildroot] [PATCH] parted: fix minor()/major() build failure due to glibc 2.28 Giulio Benetti
2018-09-10 7:25 ` Thomas Petazzoni
2018-09-10 10:49 ` Giulio Benetti
2018-09-10 11:46 ` Yegor Yefremov
2018-09-10 12:08 ` Thomas Petazzoni [this message]
2018-09-10 13:48 ` Giulio Benetti
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=20180910140823.2794d1da@windsurf \
--to=thomas.petazzoni@bootlin.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox