From: "Abimbola via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Abimbola Olaitan <craftwordltd@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
Abimbola <craftwordltd@gmail.com>
Subject: [PATCH 5/5] fix unproper comment in Makefile
Date: Sun, 03 Nov 2019 03:51:54 +0000 [thread overview]
Message-ID: <58035fc61390d42bc97697de54d44f328f110acd.1572753114.git.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.442.git.1572753114.gitgitgadget@gmail.com>
From: Abimbola <craftwordltd@gmail.com>
Signed-off-by: Abimbola <craftwordltd@gmail.com>
---
Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/Makefile b/Makefile
index a632505ad9..41f0fcb78f 100644
--- a/Makefile
+++ b/Makefile
@@ -1033,7 +1033,6 @@ LIB_OBJS += zlib.o
BUILTIN_OBJS += builtin/add.o
BUILTIN_OBJS += builtin/am.o
-// BUILTIN_OBJS += builtin/annotate.o
BUILTIN_OBJS += builtin/apply.o
BUILTIN_OBJS += builtin/archive.o
BUILTIN_OBJS += builtin/bisect--helper.o
--
gitgitgadget
next prev parent reply other threads:[~2019-11-03 3:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-03 3:51 [PATCH 0/5] Teach git annotate to use parse option instead of its own argv Abimbola Olaitan via GitGitGadget
2019-11-03 3:51 ` [PATCH 1/5] remove-annotate: change cmd_annotate to cmd_blame Abimbola via GitGitGadget
2019-11-03 19:59 ` Jakub Narebski
2019-11-04 4:04 ` Junio C Hamano
2019-11-03 3:51 ` [PATCH 2/5] edit the makefile Abimbola via GitGitGadget
2019-11-03 3:51 ` [PATCH 3/5] remove-annotate: comment out annotate BUILDIN_OBJS Abimbola via GitGitGadget
2019-11-03 3:51 ` [PATCH 4/5] remove-annotate: delete builtin annotate file Abimbola via GitGitGadget
2019-11-03 3:51 ` Abimbola via GitGitGadget [this message]
2019-11-04 4:13 ` [PATCH 5/5] fix unproper comment in Makefile Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=58035fc61390d42bc97697de54d44f328f110acd.1572753114.git.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=craftwordltd@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).