From: Junio C Hamano <gitster@pobox•com>
To: David Turner <dturner@twopensource•com>
Cc: git@vger•kernel.org, mhagger@alum•mit.edu,
sunshine@sunshineco•com, philipoakley@iee•org
Subject: Re: [PATCH v2 0/5] pseudorefs
Date: Mon, 27 Jul 2015 15:04:27 -0700 [thread overview]
Message-ID: <xmqq8ua1gsus.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1438027720-23074-1-git-send-email-dturner@twopensource.com> (David Turner's message of "Mon, 27 Jul 2015 16:08:35 -0400")
David Turner <dturner@twopensource•com> writes:
> This version of the pseudorefs patch series is much simpler. Instead
> of forbidding update_ref and delete_ref from updating pseudorefs,
> these functions now just special-case pseudorefs. So we can use
> update_ref to write pseudorefs in a rebase and sequencer, and
> we don't need to rewrite so much code.
The resulting update_ref/delete_ref look quite straight-forward,
too. Thanks.
> In addition, I made typo fixes suggested by Eric Sunshine and Philip
> Oakley.
prev parent reply other threads:[~2015-07-27 22:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 20:08 [PATCH v2 0/5] pseudorefs David Turner
2015-07-27 20:08 ` [PATCH 1/5] refs: Introduce pseudoref and per-worktree ref concepts David Turner
2015-07-28 17:13 ` Eric Sunshine
2015-07-27 20:08 ` [PATCH 2/5] notes: replace pseudorefs with real refs David Turner
2015-07-27 20:08 ` [PATCH 3/5] pseudorefs: create and use pseudoref update and delete functions David Turner
2015-07-28 0:49 ` David Turner
2015-07-27 20:08 ` [PATCH 4/5] rebase: use update_ref David Turner
2015-07-28 18:18 ` Junio C Hamano
2015-07-28 18:53 ` David Turner
2015-07-27 20:08 ` [PATCH 5/5] sequencer: replace write_cherry_pick_head with update_ref David Turner
2015-07-27 22:04 ` Junio C Hamano [this message]
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=xmqq8ua1gsus.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=dturner@twopensource$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=mhagger@alum$(echo .)mit.edu \
--cc=philipoakley@iee$(echo .)org \
--cc=sunshine@sunshineco$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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