From: "Karl Hasselström" <kha@treskal.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: [PATCH v2 0/2] Make old sha1 optional with git update-ref -d
Date: Tue, 03 Jun 2008 01:34:42 +0200 [thread overview]
Message-ID: <20080602233244.26087.51827.stgit@yoghurt> (raw)
In-Reply-To: <20080525193213.GB5674@diana.vm.bytemark.co.uk>
This series makes the old ref value optional for update-ref -d (it's
already optional for update-ref without -d).
---
Patch 1/2 updated after comments from Junio.
Karl Hasselström (2):
Make old sha1 optional with git update-ref -d
Clean up builtin-update-ref's option parsing
Documentation/git-update-ref.txt | 2 +-
builtin-update-ref.c | 36 ++++++++++++++++++++----------------
t/t1400-update-ref.sh | 8 ++++++++
3 files changed, 29 insertions(+), 17 deletions(-)
--
Karl Hasselström, kha@treskal.com
www.treskal.com/kalle
next prev parent reply other threads:[~2008-06-02 23:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-25 16:14 [PATCH 0/3] Make old sha1 optional with git update-ref -d Karl Hasselström
2008-05-25 16:14 ` [PATCH 1/3] Add some tests for " Karl Hasselström
2008-05-25 16:14 ` [PATCH 2/3] Clean up builtin-update-ref's option parsing Karl Hasselström
2008-05-25 18:40 ` Junio C Hamano
2008-05-25 19:32 ` Karl Hasselström
2008-06-02 23:34 ` Karl Hasselström [this message]
2008-06-02 23:34 ` [PATCH v2 1/2] " Karl Hasselström
2008-06-02 23:34 ` [PATCH v2 2/2] Make old sha1 optional with git update-ref -d Karl Hasselström
2008-06-03 5:51 ` Junio C Hamano
2008-06-03 6:49 ` Karl Hasselström
2008-06-03 19:39 ` Junio C Hamano
2008-05-25 16:14 ` [PATCH 3/3] " Karl Hasselström
2008-05-26 10:51 ` Johannes Schindelin
2008-05-26 14:09 ` Karl Hasselström
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=20080602233244.26087.51827.stgit@yoghurt \
--to=kha@treskal.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.