Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] pkg-autotools: search in the source directory for ltmain.sh
Date: Wed, 7 Dec 2016 09:27:43 +0100	[thread overview]
Message-ID: <20161207082743.GE8584@waldemar-brodkorb.de> (raw)
In-Reply-To: <20161207092228.1eb337c0@free-electrons.com>

Hi,
Thomas Petazzoni wrote,

> Hello,
> 
> On Wed, 7 Dec 2016 08:08:54 +0100, Waldemar Brodkorb wrote:
> > Fixes static linking of berkeleydb package, where ltmain.sh
> > is not in the sub-directory that contains configure.
> > Always search the complete source directory.
> > 
> > Fixes:
> >  http://autobuild.buildroot.net/results/f0a96f671644d9f9efcf245b354affdc84f7d7da
> > 
> > Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> 
> It should be your SoB here, since you appear as the author of this
> patch, unless you "git format --amend --author=...".

So should I resend with my SoB and mention you in the log or
what is the correct way in this case, because the analysis was made
by me and the patch by you. I really don't care ;)
 
> > Tested-by: Waldema Brodkorb <wbx@openadk.org>
> 
> Your first name has changed? :-)

I thought it might be good idea to have a shorter name ;)

Don't sent patches before first coffee ;)

best regards
 Waldemar

  reply	other threads:[~2016-12-07  8:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-07  7:08 [Buildroot] [PATCH] pkg-autotools: search in the source directory for ltmain.sh Waldemar Brodkorb
2016-12-07  8:22 ` Thomas Petazzoni
2016-12-07  8:27   ` Waldemar Brodkorb [this message]
2016-12-07  8:34     ` Thomas Petazzoni
  -- strict thread matches above, loose matches on Subject: below --
2016-12-07 18:41 Waldemar Brodkorb
2016-12-07 19:04 ` Peter Korsgaard

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=20161207082743.GE8584@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --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