public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Christian Biesinger <cbiesinger@sourceware.org>
To: bfd-cvs@sourceware.org, gdb-cvs@sourceware.org
Subject: [binutils-gdb] gnulib: Fix path to import/Makefile{,.in}
Date: Wed, 13 Nov 2019 03:24:00 -0000	[thread overview]
Message-ID: <20191113032447.31470.qmail@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=17298d65f05d18f04b864f6e6d35fccc89c0d607

commit 17298d65f05d18f04b864f6e6d35fccc89c0d607
Author: Christian Biesinger <cbiesinger@google.com>
Date:   Tue Nov 12 20:11:37 2019 -0600

    gnulib: Fix path to import/Makefile{,.in}
    
    I don't know why this path is what it is but it is clearly wrong.
    
    gnulib/ChangeLog:
    
    2019-11-12  Christian Biesinger  <cbiesinger@google.com>
    
    	* Makefile.in: Fix path to say import/ instead of gnulib/.
    
    Change-Id: Ib7f6a319ee764d20072e38911766ca7032d6ca8e

Diff:
---
 gnulib/ChangeLog   | 4 ++++
 gnulib/Makefile.in | 4 ++--
 2 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/gnulib/ChangeLog b/gnulib/ChangeLog
index af12d75..67b8dfd 100644
--- a/gnulib/ChangeLog
+++ b/gnulib/ChangeLog
@@ -1,3 +1,7 @@
+2019-11-12  Christian Biesinger  <cbiesinger@google.com>
+
+	* Makefile.in: Fix path to say import/ instead of gnulib/.
+
 2019-11-06  Christian Biesinger  <cbiesinger@google.com>
 
 	* config.in: Regenerate.
diff --git a/gnulib/Makefile.in b/gnulib/Makefile.in
index c42bb23..a9879ed 100644
--- a/gnulib/Makefile.in
+++ b/gnulib/Makefile.in
@@ -180,8 +180,8 @@ Makefile: Makefile.in config.status
 	  CONFIG_HEADERS= \
 	  $(SHELL) config.status
 
-gnulib/Makefile: gnulib/Makefile.in config.status
-	CONFIG_FILES="gnulib/Makefile" \
+import/Makefile: import/Makefile.in config.status
+	CONFIG_FILES="import/Makefile" \
 	  CONFIG_COMMANDS="depfiles" \
 	  CONFIG_HEADERS= \
 	  CONFIG_LINKS= \


                 reply	other threads:[~2019-11-13  3:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20191113032447.31470.qmail@sourceware.org \
    --to=cbiesinger@sourceware.org \
    --cc=bfd-cvs@sourceware.org \
    --cc=gdb-cvs@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).