In a struct definitions, unlike functions, the prevailing style is for
the opening brace to go on the same line as the struct name, like so:
 struct foo {
	int bar;
	char *baz;
 };
Indeed, grepping for 'struct [a-z_]* {$' yields about 5 times as many
matches as 'struct [a-z_]*$'.
Linus sayeth:
 Heretic people all over the world have claimed that this inconsistency
 is ...  well ...  inconsistent, but all right-thinking people know that
 (a) K&R are _right_ and (b) K&R are right.
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
		
	
		
			
				
	
	
		
			28 lines
		
	
	
		
			479 B
		
	
	
	
		
			C
		
	
	
	
	
	
			
		
		
	
	
			28 lines
		
	
	
		
			479 B
		
	
	
	
		
			C
		
	
	
	
	
	
#ifndef FETCH_PACK_H
 | 
						|
#define FETCH_PACK_H
 | 
						|
 | 
						|
struct fetch_pack_args {
 | 
						|
	const char *uploadpack;
 | 
						|
	int unpacklimit;
 | 
						|
	int depth;
 | 
						|
	unsigned quiet:1,
 | 
						|
		keep_pack:1,
 | 
						|
		lock_pack:1,
 | 
						|
		use_thin_pack:1,
 | 
						|
		fetch_all:1,
 | 
						|
		verbose:1,
 | 
						|
		no_progress:1,
 | 
						|
		include_tag:1,
 | 
						|
		stateless_rpc:1;
 | 
						|
};
 | 
						|
 | 
						|
struct ref *fetch_pack(struct fetch_pack_args *args,
 | 
						|
		int fd[], struct child_process *conn,
 | 
						|
		const struct ref *ref,
 | 
						|
		const char *dest,
 | 
						|
		int nr_heads,
 | 
						|
		char **heads,
 | 
						|
		char **pack_lockfile);
 | 
						|
 | 
						|
#endif
 |