delta/libgit2.git/src/refdb.h, branch ethomson/git_ref github.com: libgit2/libgit2.git Make sure to always include "common.h" first 2017-07-03T08:51:48+00:00 Patrick Steinhardt ps@pks.im 2017-06-30T11:39:01+00:00 0c7f49dd4316b332f30b4ea72a657bace41e1245 Next to including several files, our "common.h" header also declares various macros which are then used throughout the project. As such, we have to make sure to always include this file first in all implementation files. Otherwise, we might encounter problems or even silent behavioural differences due to macros or defines not being defined as they should be. So in fact, our header and implementation files should make sure to always include "common.h" first. This commit does so by establishing a common include pattern. Header files inside of "src" will now always include "common.h" as its first other file, separated by a newline from all the other includes to make it stand out as special. There are two cases for the implementation files. If they do have a matching header file, they will always include this one first, leading to "common.h" being transitively included as first file. If they do not have a matching header file, they instead include "common.h" as first file themselves. This fixes the outlined problems and will become our standard practice for header and source files inside of the "src/" from now on. 
Next to including several files, our "common.h" header also declares
various macros which are then used throughout the project. As such, we
have to make sure to always include this file first in all
implementation files. Otherwise, we might encounter problems or even
silent behavioural differences due to macros or defines not being
defined as they should be. So in fact, our header and implementation
files should make sure to always include "common.h" first.

This commit does so by establishing a common include pattern. Header
files inside of "src" will now always include "common.h" as its first
other file, separated by a newline from all the other includes to make
it stand out as special. There are two cases for the implementation
files. If they do have a matching header file, they will always include
this one first, leading to "common.h" being transitively included as
first file. If they do not have a matching header file, they instead
include "common.h" as first file themselves.

This fixes the outlined problems and will become our standard practice
for header and source files inside of the "src/" from now on.
Introduce reference transactions 2014-09-30T13:44:32+00:00 Carlos Martín Nieto cmn@dwim.me 2014-06-28T04:39:38+00:00 ab8d9242f54e2c570f86a45a509b9420911a4d44 A transaction allows you to lock multiple references and set up changes for them before applying the changes all at once (or as close as the backend supports). This can be used for replication purposes, or for making sure some operations run when the reference is locked and thus cannot be changed. 
A transaction allows you to lock multiple references and set up changes
for them before applying the changes all at once (or as close as the
backend supports).

This can be used for replication purposes, or for making sure some
operations run when the reference is locked and thus cannot be changed.
refs: placeholder conditional delete 2014-02-05T11:07:57+00:00 Carlos Martín Nieto cmn@dwim.me 2014-02-05T10:07:34+00:00 7ee8c7e6776a3c5b3a45cfd10ccf205eebb3f3fe We don't actually pass the old value yet. 
We don't actually pass the old value yet.
refdb: add conditional symbolic updates 2014-02-05T11:07:56+00:00 Carlos Martín Nieto cmn@dwim.me 2014-02-04T21:04:00+00:00 911236619b5d774e33dd9f3de92a7c86c2befb26 Add a parameter to the backend to allow checking for the old symbolic target. 
Add a parameter to the backend to allow checking for the old symbolic
target.
refs: conditional ref updates 2014-02-05T11:07:56+00:00 Carlos Martín Nieto cmn@dwim.me 2013-12-18T18:58:16+00:00 9b148098e6802f9dd797471fc4f20cfc58a846b4 Allow updating references if the old value matches the given one. 
Allow updating references if the old value matches the given one.
refs: expose has_log() on the backend 2013-12-09T14:55:11+00:00 Carlos Martín Nieto cmn@dwim.me 2013-11-23T13:39:53+00:00 f21051297cc698644ea0dc9c7122ec944dba2863 The frontend used to look at the file directly, but that's obviously not the right thing to do. Expose it on the backend and use that function instead. 
The frontend used to look at the file directly, but that's obviously not
the right thing to do. Expose it on the backend and use that function
instead.
refs: expose a way to ensure a ref has a log 2013-12-09T14:55:11+00:00 Carlos Martín Nieto cmn@dwim.me 2013-11-23T13:13:01+00:00 8d5ec9106afbca346a8def84ef20de0a7ba2240a Sometimes (e.g. stash) we want to make sure that a log will be written, even if it's not in one of the standard locations. Let's make that easier. 
Sometimes (e.g. stash) we want to make sure that a log will be written,
even if it's not in one of the standard locations. Let's make that
easier.
reflog: integrate into the ref writing 2013-11-23T13:55:02+00:00 Carlos Martín Nieto cmn@dwim.me 2013-11-13T17:15:20+00:00 a57dd3b7a46c9a2f87f203f1ab372fa28e10e571 Whenever a reference is created or updated, we need to write to the reflog regardless of whether the user gave us a message, so we shouldn't leave that to the ref frontend, but integrate it into the backend. This also eliminates the race between ref update and writing to the reflog, as we protect the reflog with the ref lock. As an additional benefit, this reflog append on the backend happens by appending to the file instead of parsing and rewriting it. 
Whenever a reference is created or updated, we need to write to the
reflog regardless of whether the user gave us a message, so we shouldn't
leave that to the ref frontend, but integrate it into the backend.

This also eliminates the race between ref update and writing to the
reflog, as we protect the reflog with the ref lock.

As an additional benefit, this reflog append on the backend happens by
appending to the file instead of parsing and rewriting it.
refdb: add a `message` parameter for appending to the log 2013-11-23T12:35:53+00:00 Carlos Martín Nieto cmn@dwim.me 2013-11-13T12:36:37+00:00 110df89317b56267b956574216d6611637860446 This is as yet unused. 
This is as yet unused.
reflog: move the reflog implementation into refdb_fs 2013-10-02T04:53:24+00:00 Carlos Martín Nieto cmn@dwim.me 2013-08-19T11:01:49+00:00 b976f3c2c228413d124be8fea3280a44bd5e3136 References and their logs are logically coupled, let's make it so in the code by moving the fs-based reflog implementation to live next to the fs-based refs one. As part of the change, make the function take names rather than references, as only the names are relevant when looking up and handling reflogs. 
References and their logs are logically coupled, let's make it so in
the code by moving the fs-based reflog implementation to live next to
the fs-based refs one.

As part of the change, make the function take names rather than
references, as only the names are relevant when looking up and
handling reflogs.