standardize brace placement in struct definitions
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>
This commit is contained in:
committed by
Junio C Hamano
parent
c6c8d0b797
commit
9cba13ca5d
15
http-push.c
15
http-push.c
@ -82,8 +82,7 @@ static int helper_status;
|
||||
|
||||
static struct object_list *objects;
|
||||
|
||||
struct repo
|
||||
{
|
||||
struct repo {
|
||||
char *url;
|
||||
char *path;
|
||||
int path_len;
|
||||
@ -108,8 +107,7 @@ enum transfer_state {
|
||||
COMPLETE
|
||||
};
|
||||
|
||||
struct transfer_request
|
||||
{
|
||||
struct transfer_request {
|
||||
struct object *obj;
|
||||
char *url;
|
||||
char *dest;
|
||||
@ -127,8 +125,7 @@ struct transfer_request
|
||||
|
||||
static struct transfer_request *request_queue_head;
|
||||
|
||||
struct xml_ctx
|
||||
{
|
||||
struct xml_ctx {
|
||||
char *name;
|
||||
int len;
|
||||
char *cdata;
|
||||
@ -136,8 +133,7 @@ struct xml_ctx
|
||||
void *userData;
|
||||
};
|
||||
|
||||
struct remote_lock
|
||||
{
|
||||
struct remote_lock {
|
||||
char *url;
|
||||
char *owner;
|
||||
char *token;
|
||||
@ -156,8 +152,7 @@ struct remote_lock
|
||||
/* Flags that remote_ls passes to callback functions */
|
||||
#define IS_DIR (1u << 0)
|
||||
|
||||
struct remote_ls_ctx
|
||||
{
|
||||
struct remote_ls_ctx {
|
||||
char *path;
|
||||
void (*userFunc)(struct remote_ls_ctx *ls);
|
||||
void *userData;
|
||||
|
||||
Reference in New Issue
Block a user