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

Re: [PATCH/RFC 1/3] send-pack: track errors for each ref

From
Alex Riesen <raa.lkml@gmail.com>
Date
Nov 13, 2007, 19:04 UTC
Message-ID
<20071113190447.GB3268@steel.home>
In-Reply-To
<20071113102709.GA2905@sigill.intra.peff.net>
Jeff King, Tue, Nov 13, 2007 11:27:09 +0100:
Show 13 quoted lines
> diff --git a/cache.h b/cache.h
> index 5f40e12..ca5d96d 100644
> --- a/cache.h
> +++ b/cache.h
> @@ -499,8 +499,17 @@ struct ref {
>  	struct ref *next;
>  	unsigned char old_sha1[20];
>  	unsigned char new_sha1[20];
> -	unsigned char force;
> -	unsigned char merge;
> +	unsigned char force : 1;
> +	unsigned char merge : 1;
> +	unsigned char nonff : 1;
        unsigned char fastforward : 1; ? ffwd?
Show 5 quoted lines
> +	unsigned char deletion : 1;
> +	enum {
> +		REF_STATUS_NONE = 0,
> +		REF_STATUS_OK,
> +		REF_STATUS_NONFF,
isn't it a duplication of nonff?
Previous: Jeff KingNext: Jeff King
Message 4 of 20 in “tracking per-ref errors on push”
  1. 0/3 tracking per-ref errors on pushJeff King, Nov 13, 2007
  2. 1/3 send-pack: track errors for each refJeff King, Nov 13, 2007
  3. Jeff KingNov 13, 2007
  4. Alex RiesenNov 13, 2007
  5. Jeff KingNov 13, 2007
  6. Alex RiesenNov 13, 2007
  7. 2/3 send-pack: check ref->status before updating tracking refsJeff King, Nov 13, 2007
  8. 3/3 send-pack: assign remote errors to each refJeff King, Nov 13, 2007
  9. Jeff KingNov 13, 2007
  10. Jeff KingNov 13, 2007
  11. 1/3 send-pack: track errors for each refJeff King, Nov 13, 2007
  12. 2/3 send-pack: check ref->status before updating tracking refsJeff King, Nov 13, 2007
  13. 3/3 send-pack: assign remote errors to each refJeff King, Nov 13, 2007
  14. Junio C HamanoNov 14, 2007
  15. Junio C HamanoNov 14, 2007
  16. Johannes SchindelinNov 14, 2007
  17. Junio C HamanoNov 14, 2007
  18. Jeff KingNov 15, 2007
  19. Junio C HamanoNov 16, 2007
  20. Jeff KingNov 15, 2007

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.