On Sun, 07 Oct 2018 08:44:20 +0900
Junio C Hamano wrote:
> Stefan Beller writes:
>
> >> static int module_config(int argc, const char **argv, const char *prefix)
> >> {
> >> + enum {
> >> + CHECK_WRITEABLE = 1
> >> + } command = 0;
> >
> > Can we have the default
Stefan Beller writes:
>> static int module_config(int argc, const char **argv, const char *prefix)
>> {
>> + enum {
>> + CHECK_WRITEABLE = 1
>> + } command = 0;
>
> Can we have the default named? Then we would only use states
> from within the enum?
Why? Do we use a
On Fri, 5 Oct 2018 16:50:10 -0700
Stefan Beller wrote:
> > static int module_config(int argc, const char **argv, const char *prefix)
> > {
> > + enum {
> > + CHECK_WRITEABLE = 1
> > + } command = 0;
>
> Can we have the default named? Then we would only use states
>
> static int module_config(int argc, const char **argv, const char *prefix)
> {
> + enum {
> + CHECK_WRITEABLE = 1
> + } command = 0;
Can we have the default named? Then we would only use states
from within the enum?
Introduce a helper function named is_writing_gitmodules_ok() to verify
that the .gitmodules file is safe to write.
The function name follows the scheme of is_staging_gitmodules_ok().
The two symbolic constants GITMODULES_INDEX and GITMODULES_HEAD are used
to get help from the C preprocessor in
5 matches
Mail list logo
