git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 4/5] rebase: use update_ref

From
David Turner <dturner@twopensource.com>
Date
Jul 28, 2015, 18:53 UTC
Message-ID
<1438109626.18134.13.camel@twopensource.com>
In-Reply-To
<xmqq4mkof8nq.fsf@gitster.dls.corp.google.com>
On Tue, 2015-07-28 at 11:18 -0700, Junio C Hamano wrote:
Show 13 quoted lines
> David Turner <dturner@twopensource.com> writes:
> 
> > Instead of manually writing a pseudoref (in one case) and shelling out
> > to git update-ref (in another), use the update_ref function.  This
> > is much simpler.
> >
> > Signed-off-by: David Turner <dturner@twopensource.com>
> > ---
> >  bisect.c | 37 ++++++++-----------------------------
> >  1 file changed, 8 insertions(+), 29 deletions(-)
> 
> Mistitled?  I can do s/rebase/bisect/ at my end if that is all
> needed.
Apparently, yes.  Thanks.
Previous: Junio C HamanoNext: David Turner
Message 9 of 11 in “pseudorefs”
  1. 0/5 pseudorefsDavid Turner, Jul 27, 2015
  2. 1/5 refs: Introduce pseudoref and per-worktree ref conceptsDavid Turner, Jul 27, 2015
  3. Eric SunshineJul 28, 2015
  4. 2/5 notes: replace pseudorefs with real refsDavid Turner, Jul 27, 2015
  5. 3/5 pseudorefs: create and use pseudoref update and delete functionsDavid Turner, Jul 27, 2015
  6. David TurnerJul 28, 2015
  7. 4/5 rebase: use update_refDavid Turner, Jul 27, 2015
  8. Junio C HamanoJul 28, 2015
  9. David TurnerJul 28, 2015
  10. 5/5 sequencer: replace write_cherry_pick_head with update_refDavid Turner, Jul 27, 2015
  11. Junio C HamanoJul 27, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.