From: Christian Couder <christian.couder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git <git@vger.kernel.org>, "Jeff King" <peff@peff.net>,
"Ævar Arnfjörð" <avarab@gmail.com>,
"Karsten Blees" <karsten.blees@gmail.com>,
"Nguyen Thai Ngoc Duy" <pclouds@gmail.com>,
"Stefan Beller" <sbeller@google.com>,
"Matthieu Moy" <Matthieu.Moy@grenoble-inp.fr>,
"Eric Sunshine" <sunshine@sunshineco.com>,
"Ramsay Jones" <ramsay@ramsayjones.plus.com>,
"Johannes Sixt" <j6t@kdbg.org>, "René Scharfe" <l.s.r@web.de>,
"Christian Couder" <chriscool@tuxfamily.org>
Subject: Re: [PATCH v7 01/40] apply: move 'struct apply_state' to apply.h
Date: Tue, 14 Jun 2016 13:07:35 +0200 [thread overview]
Message-ID: <CAP8UFD2uoQy9eNvMiBXvfk0g0kA_Nn6ekoRxEWCRwKbMSwDMsA@mail.gmail.com> (raw)
In-Reply-To: <xmqq7fdsbt6z.fsf@gitster.mtv.corp.google.com>
On Tue, Jun 14, 2016 at 12:49 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Christian Couder <christian.couder@gmail.com> writes:
>
>> To libify `git apply` functionality we must make 'struct apply_state'
>> usable outside "builtin/apply.c".
>>
>> Let's do that by creating a new "apply.h" and moving
>> 'struct apply_state' there.
>>
>> Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
>> ---
>> apply.h | 100 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> builtin/apply.c | 98 +-----------------------------------------------------
>> 2 files changed, 101 insertions(+), 97 deletions(-)
>> create mode 100644 apply.h
>>
>> diff --git a/apply.h b/apply.h
>> new file mode 100644
>> index 0000000..9a98eae
>> --- /dev/null
>> +++ b/apply.h
>> @@ -0,0 +1,100 @@
>> +#ifndef APPLY_H
>> +#define APPLY_H
>> +
>> +enum ws_error_action {
>> + nowarn_ws_error,
>> + warn_on_ws_error,
>> + die_on_ws_error,
>> + correct_ws_error
>> +};
>> +
>> +enum ws_ignore {
>> + ignore_ws_none,
>> + ignore_ws_change
>> +};
>> +
>> +/*
>> + * We need to keep track of how symlinks in the preimage are
>> + * manipulated by the patches. A patch to add a/b/c where a/b
>> + * is a symlink should not be allowed to affect the directory
>> + * the symlink points at, but if the same patch removes a/b,
>> + * it is perfectly fine, as the patch removes a/b to make room
>> + * to create a directory a/b so that a/b/c can be created.
>> + *
>> + * See also "struct string_list symlink_changes" in "struct
>> + * apply_state".
>> + */
>> +#define SYMLINK_GOES_AWAY 01
>> +#define SYMLINK_IN_RESULT 02
>
> Everything below is agreeable, but all the names that are made
> public above by this change do not sound specific enough to "apply".
> I wonder if they should get "apply" somewhere in their names to
> avoid confusion coming from the namespace contamination...
Yeah, I will add "apply" in the names.
Thanks,
Christian.
next prev parent reply other threads:[~2016-06-14 11:07 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 16:09 [PATCH v7 00/40] libify apply and use lib in am, part 2 Christian Couder
2016-06-13 16:09 ` [PATCH v7 01/40] apply: move 'struct apply_state' to apply.h Christian Couder
2016-06-13 22:49 ` Junio C Hamano
2016-06-14 11:07 ` Christian Couder [this message]
2016-06-13 16:09 ` [PATCH v7 02/40] builtin/apply: make apply_patch() return -1 instead of die()ing Christian Couder
2016-06-13 22:55 ` Junio C Hamano
2016-06-14 11:06 ` Christian Couder
2016-06-14 17:50 ` Junio C Hamano
2016-06-13 16:09 ` [PATCH v7 03/40] builtin/apply: read_patch_file() " Christian Couder
2016-06-13 16:09 ` [PATCH v7 04/40] builtin/apply: make find_header() " Christian Couder
2016-06-13 16:09 ` [PATCH v7 05/40] builtin/apply: make parse_chunk() return a negative integer on error Christian Couder
2016-06-13 16:09 ` [PATCH v7 06/40] builtin/apply: make parse_single_patch() return -1 " Christian Couder
2016-06-13 16:09 ` [PATCH v7 07/40] builtin/apply: make parse_whitespace_option() return -1 instead of die()ing Christian Couder
2016-06-13 16:09 ` [PATCH v7 08/40] builtin/apply: make parse_ignorewhitespace_option() " Christian Couder
2016-06-13 16:09 ` [PATCH v7 09/40] builtin/apply: move init_apply_state() to apply.c Christian Couder
2016-06-13 16:09 ` [PATCH v7 10/40] apply: make init_apply_state() return -1 instead of exit()ing Christian Couder
2016-06-13 16:09 ` [PATCH v7 11/40] builtin/apply: make check_apply_state() return -1 instead of die()ing Christian Couder
2016-06-13 16:09 ` [PATCH v7 12/40] builtin/apply: move check_apply_state() to apply.c Christian Couder
2016-06-13 16:09 ` [PATCH v7 13/40] builtin/apply: make apply_all_patches() return -1 on error Christian Couder
2016-06-13 16:09 ` [PATCH v7 14/40] builtin/apply: make parse_traditional_patch() " Christian Couder
2016-06-13 16:09 ` [PATCH v7 15/40] builtin/apply: make gitdiff_*() return 1 at end of header Christian Couder
2016-06-13 16:09 ` [PATCH v7 16/40] builtin/apply: make gitdiff_*() return -1 on error Christian Couder
2016-06-13 16:09 ` [PATCH v7 17/40] builtin/apply: change die_on_unsafe_path() to check_unsafe_path() Christian Couder
2016-06-13 16:09 ` [PATCH v7 18/40] builtin/apply: make build_fake_ancestor() return -1 on error Christian Couder
2016-06-13 16:09 ` [PATCH v7 19/40] builtin/apply: make remove_file() " Christian Couder
2016-06-13 16:09 ` [PATCH v7 20/40] builtin/apply: make add_conflicted_stages_file() " Christian Couder
2016-06-13 16:09 ` [PATCH v7 21/40] builtin/apply: make add_index_file() " Christian Couder
2016-06-13 16:09 ` [PATCH v7 22/40] builtin/apply: make create_file() " Christian Couder
2016-06-13 16:09 ` [PATCH v7 23/40] builtin/apply: make write_out_one_result() " Christian Couder
2016-06-13 16:09 ` [PATCH v7 24/40] builtin/apply: make write_out_results() " Christian Couder
2016-06-13 16:09 ` [PATCH v7 25/40] builtin/apply: make try_create_file() " Christian Couder
2016-06-13 16:09 ` [PATCH v7 26/40] builtin/apply: make create_one_file() " Christian Couder
2016-06-13 16:09 ` [PATCH v7 27/40] builtin/apply: rename option parsing functions Christian Couder
2016-06-13 16:09 ` [PATCH v7 28/40] apply: rename and move opt constants to apply.h Christian Couder
2016-06-13 16:09 ` [PATCH v7 30/40] apply: make some parsing functions static again Christian Couder
2016-06-13 16:09 ` [PATCH v7 31/40] environment: add set_index_file() Christian Couder
2016-06-13 16:09 ` [PATCH v7 32/40] write_or_die: use warning() instead of fprintf(stderr, ...) Christian Couder
2016-06-13 16:09 ` [PATCH v7 33/40] apply: add 'be_silent' variable to 'struct apply_state' Christian Couder
2016-06-13 16:09 ` [PATCH v7 34/40] apply: make 'be_silent' incompatible with 'apply_verbosely' Christian Couder
2016-06-13 16:09 ` [PATCH v7 35/40] apply: don't print on stdout when be_silent is set Christian Couder
2016-06-13 16:09 ` [PATCH v7 36/40] usage: add set_warn_routine() Christian Couder
2016-06-13 16:09 ` [PATCH v7 37/40] usage: add get_error_routine() and get_warn_routine() Christian Couder
2016-06-13 16:09 ` [PATCH v7 38/40] apply: change error_routine when be_silent is set Christian Couder
2016-06-13 16:09 ` [PATCH v7 39/40] builtin/am: use apply api in run_apply() Christian Couder
2016-06-13 16:09 ` [PATCH v7 40/40] apply: use error_errno() where possible Christian Couder
2016-06-13 16:16 ` [PATCH v7 00/40] libify apply and use lib in am, part 2 Christian Couder
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=CAP8UFD2uoQy9eNvMiBXvfk0g0kA_Nn6ekoRxEWCRwKbMSwDMsA@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=avarab@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=karsten.blees@gmail.com \
--cc=l.s.r@web.de \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=ramsay@ramsayjones.plus.com \
--cc=sbeller@google.com \
--cc=sunshine@sunshineco.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).