From: David Turner <dturner@twopensource.com>
To: Ronnie Sahlberg <sahlberg@google.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 17/22] refs.c: add a backend method structure with transaction functions
Date: Fri, 08 Aug 2014 14:17:52 -0400 [thread overview]
Message-ID: <1407521872.26542.21.camel@leckie> (raw)
In-Reply-To: <1407516309-27989-18-git-send-email-sahlberg@google.com>
On Fri, 2014-08-08 at 09:45 -0700, Ronnie Sahlberg wrote:
> +struct ref_be refs_files = {
> + .transaction_begin = files_transaction_begin,
> + .transaction_update_sha1 = files_transaction_update_sha1,
> + .transaction_create_sha1 = files_transaction_create_sha1,
> + .transaction_delete_sha1 = files_transaction_delete_sha1,
> + .transaction_update_reflog = files_transaction_update_reflog,
> + .transaction_commit = files_transaction_commit,
> + .transaction_free = files_transaction_free,
> +};
C99 designated initializers are unfortunately forbidden by
CodingGuidelines.
next prev parent reply other threads:[~2014-08-08 18:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 16:44 [PATCH 00/22] backend-struct-db Ronnie Sahlberg
2014-08-08 16:44 ` [PATCH 01/22] refs.c: create a public function for is_refname_available Ronnie Sahlberg
2014-08-08 17:27 ` David Turner
2014-08-11 15:00 ` Ronnie Sahlberg
2014-08-08 16:44 ` [PATCH 02/22] refs-common.c: create a file to host all common refs code Ronnie Sahlberg
2014-08-08 16:44 ` [PATCH 03/22] refs-common.c: move update_ref to refs-common.c Ronnie Sahlberg
2014-08-08 16:44 ` [PATCH 04/22] refs-common.c: move delete_ref to the common code Ronnie Sahlberg
2014-08-08 16:44 ` [PATCH 05/22] refs-common.c: move rename_ref " Ronnie Sahlberg
2014-08-08 16:44 ` [PATCH 06/22] refs-common.c: move read_ref_at to the refs common file Ronnie Sahlberg
2014-08-08 16:44 ` [PATCH 07/22] refs-common.c: move the hidden refs functions to the common code Ronnie Sahlberg
2014-08-08 16:44 ` [PATCH 08/22] refs-common.c: move dwim and friend functions to refs common Ronnie Sahlberg
2014-08-08 16:44 ` [PATCH 09/22] refs-common.c: move warn_if_dangling_symref* to refs-common Ronnie Sahlberg
2014-08-08 16:44 ` [PATCH 10/22] refs-common.c: move read_ref, read_ref_full and ref_exists to common Ronnie Sahlberg
2014-08-08 16:44 ` [PATCH 11/22] refs-common.c: move resolve_refdup " Ronnie Sahlberg
2014-08-08 16:44 ` [PATCH 12/22] refs-common.c: move check_refname_component to the common code Ronnie Sahlberg
2014-08-08 16:45 ` [PATCH 13/22] refs-common.c: move is_branch " Ronnie Sahlberg
2014-08-08 16:45 ` [PATCH 14/22] refs-common.c: move names_conflict " Ronnie Sahlberg
2014-08-08 16:45 ` [PATCH 15/22] refs-common.c: move prettify_refname " Ronnie Sahlberg
2014-08-08 16:45 ` [PATCH 16/22] refs-common.c: move ref iterators " Ronnie Sahlberg
2014-08-08 16:45 ` [PATCH 17/22] refs.c: add a backend method structure with transaction functions Ronnie Sahlberg
2014-08-08 18:17 ` David Turner [this message]
2014-08-11 14:56 ` Ronnie Sahlberg
2014-08-08 16:45 ` [PATCH 18/22] refs.c: add reflog backend methods Ronnie Sahlberg
2014-08-08 16:45 ` [PATCH 19/22] refs.c: add methods for misc ref operations Ronnie Sahlberg
2014-08-08 16:45 ` [PATCH 20/22] refs.c: add methods for head_ref* Ronnie Sahlberg
2014-08-08 16:45 ` [PATCH 21/22] refs.c: add methods for the ref iterators Ronnie Sahlberg
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=1407521872.26542.21.camel@leckie \
--to=dturner@twopensource.com \
--cc=git@vger.kernel.org \
--cc=sahlberg@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).