From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH 0/3] "git notes remove" updates
Date: Wed, 18 May 2011 17:14:18 -0700 [thread overview]
Message-ID: <1305764061-21303-1-git-send-email-gitster@pobox.com> (raw)
I wanted to do a bit better than
for sha1 in ... list of old commit objects
do
git notes --ref refs/notes/amlog remove $sha1
done
to remove old entries in my "where did this commit come from" database.
Junio C Hamano (3):
notes remove: allow removing more than one
notes remove: --missing-ok
notes remove: --stdin reads from the standard input
Documentation/git-notes.txt | 16 ++++++++--
builtin/notes.c | 65 ++++++++++++++++++++++++++-------------
t/t3301-notes.sh | 71 +++++++++++++++++++++++++++++++++++++++++++
3 files changed, 127 insertions(+), 25 deletions(-)
--
1.7.5.1.414.gb4910
next reply other threads:[~2011-05-19 0:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 0:14 Junio C Hamano [this message]
2011-05-19 0:14 ` [PATCH 1/3] notes remove: allow removing more than one Junio C Hamano
2011-05-19 6:43 ` Michael J Gruber
2011-05-19 6:50 ` Junio C Hamano
2011-05-19 7:31 ` Michael J Gruber
2011-05-19 17:44 ` Junio C Hamano
2011-05-19 18:47 ` [PATCH 1/2] fixup! notes remove: --ignore-missing Michael J Gruber
2011-05-19 18:47 ` [PATCH 2/2] fixup! notes remove: --stdin reads from the standard input Michael J Gruber
2011-05-19 0:14 ` [PATCH 2/3] notes remove: --missing-ok Junio C Hamano
2011-05-19 2:00 ` Junio C Hamano
2011-05-19 0:14 ` [PATCH 3/3] notes remove: --stdin reads from the standard input Junio C Hamano
2011-05-19 6:50 ` Michael J Gruber
2011-05-19 10:50 ` Jeff King
2011-05-19 17:55 ` Junio C Hamano
2011-05-19 18:02 ` Jeff King
2011-05-19 2:03 ` [PATCH 4/3] show: --ignore-missing Junio C Hamano
2011-05-19 7:08 ` [PATCH 0/3] "git notes remove" updates Johan Herland
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=1305764061-21303-1-git-send-email-gitster@pobox.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.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 NNTP newsgroup(s).