2009-10-19 20:38:32 +08:00
|
|
|
#ifndef SUBMODULE_H
|
|
|
|
#define SUBMODULE_H
|
|
|
|
|
2017-06-23 02:43:45 +08:00
|
|
|
struct repository;
|
2010-06-25 22:56:47 +08:00
|
|
|
struct diff_options;
|
2012-09-01 23:27:06 +08:00
|
|
|
struct argv_array;
|
2017-03-31 09:40:00 +08:00
|
|
|
struct oid_array;
|
2017-04-06 01:47:19 +08:00
|
|
|
struct remote;
|
2010-06-25 22:56:47 +08:00
|
|
|
|
2011-03-07 06:10:46 +08:00
|
|
|
enum {
|
2016-12-20 02:25:32 +08:00
|
|
|
RECURSE_SUBMODULES_ONLY = -5,
|
2015-11-17 19:05:56 +08:00
|
|
|
RECURSE_SUBMODULES_CHECK = -4,
|
2015-08-18 08:22:00 +08:00
|
|
|
RECURSE_SUBMODULES_ERROR = -3,
|
2015-08-18 08:21:57 +08:00
|
|
|
RECURSE_SUBMODULES_NONE = -2,
|
2011-03-07 06:10:46 +08:00
|
|
|
RECURSE_SUBMODULES_ON_DEMAND = -1,
|
|
|
|
RECURSE_SUBMODULES_OFF = 0,
|
|
|
|
RECURSE_SUBMODULES_DEFAULT = 1,
|
|
|
|
RECURSE_SUBMODULES_ON = 2
|
|
|
|
};
|
|
|
|
|
2016-03-01 10:07:11 +08:00
|
|
|
enum submodule_update_type {
|
|
|
|
SM_UPDATE_UNSPECIFIED = 0,
|
|
|
|
SM_UPDATE_CHECKOUT,
|
|
|
|
SM_UPDATE_REBASE,
|
|
|
|
SM_UPDATE_MERGE,
|
|
|
|
SM_UPDATE_NONE,
|
|
|
|
SM_UPDATE_COMMAND
|
|
|
|
};
|
|
|
|
|
|
|
|
struct submodule_update_strategy {
|
|
|
|
enum submodule_update_type type;
|
|
|
|
const char *command;
|
|
|
|
};
|
2016-03-01 10:07:13 +08:00
|
|
|
#define SUBMODULE_UPDATE_STRATEGY_INIT {SM_UPDATE_UNSPECIFIED, NULL}
|
2016-03-01 10:07:11 +08:00
|
|
|
|
2017-08-03 03:49:21 +08:00
|
|
|
extern int is_gitmodules_unmerged(const struct index_state *istate);
|
2017-12-13 03:53:51 +08:00
|
|
|
extern int is_staging_gitmodules_ok(struct index_state *istate);
|
2016-12-21 07:20:09 +08:00
|
|
|
extern int update_path_in_gitmodules(const char *oldpath, const char *newpath);
|
|
|
|
extern int remove_path_from_gitmodules(const char *path);
|
2017-12-13 03:53:50 +08:00
|
|
|
extern void stage_updated_gitmodules(struct index_state *istate);
|
2016-12-21 07:20:09 +08:00
|
|
|
extern void set_diffopt_flags_from_submodule_config(struct diff_options *,
|
2010-08-06 06:39:25 +08:00
|
|
|
const char *path);
|
2017-06-01 08:30:47 +08:00
|
|
|
extern int git_default_submodule_config(const char *var, const char *value, void *cb);
|
2017-05-27 03:10:12 +08:00
|
|
|
|
|
|
|
struct option;
|
|
|
|
int option_parse_recurse_submodules_worktree_updater(const struct option *opt,
|
|
|
|
const char *arg, int unset);
|
2017-06-23 02:43:46 +08:00
|
|
|
extern int is_submodule_active(struct repository *repo, const char *path);
|
2017-03-15 05:46:31 +08:00
|
|
|
/*
|
|
|
|
* Determine if a submodule has been populated at a given 'path' by checking if
|
|
|
|
* the <path>/.git resolves to a valid git repository.
|
|
|
|
* If return_error_code is NULL, die on error.
|
|
|
|
* Otherwise the return error code is the same as of resolve_gitdir_gently.
|
|
|
|
*/
|
|
|
|
extern int is_submodule_populated_gently(const char *path, int *return_error_code);
|
2017-05-10 03:17:59 +08:00
|
|
|
extern void die_in_unpopulated_submodule(const struct index_state *istate,
|
|
|
|
const char *prefix);
|
2017-05-12 06:04:24 +08:00
|
|
|
extern void die_path_inside_submodule(const struct index_state *istate,
|
|
|
|
const struct pathspec *ps);
|
2017-08-04 02:19:50 +08:00
|
|
|
extern enum submodule_update_type parse_submodule_update_type(const char *value);
|
2016-12-21 07:20:09 +08:00
|
|
|
extern int parse_submodule_update_strategy(const char *value,
|
2016-03-01 10:07:11 +08:00
|
|
|
struct submodule_update_strategy *dst);
|
2016-12-21 07:20:09 +08:00
|
|
|
extern const char *submodule_strategy_to_string(const struct submodule_update_strategy *s);
|
|
|
|
extern void handle_ignore_submodules_arg(struct diff_options *, const char *);
|
2017-06-30 08:07:00 +08:00
|
|
|
extern void show_submodule_summary(struct diff_options *o, const char *path,
|
2016-09-01 07:27:23 +08:00
|
|
|
struct object_id *one, struct object_id *two,
|
2017-06-30 08:07:00 +08:00
|
|
|
unsigned dirty_submodule);
|
|
|
|
extern void show_submodule_inline_diff(struct diff_options *o, const char *path,
|
2016-09-01 07:27:25 +08:00
|
|
|
struct object_id *one, struct object_id *two,
|
2017-06-30 08:07:00 +08:00
|
|
|
unsigned dirty_submodule);
|
2017-03-15 05:46:34 +08:00
|
|
|
/* Check if we want to update any submodule.*/
|
|
|
|
extern int should_update_submodules(void);
|
|
|
|
/*
|
|
|
|
* Returns the submodule struct if the given ce entry is a submodule
|
|
|
|
* and it should be updated. Returns NULL otherwise.
|
|
|
|
*/
|
|
|
|
extern const struct submodule *submodule_from_ce(const struct cache_entry *ce);
|
2017-03-27 00:01:35 +08:00
|
|
|
extern void check_for_new_submodule_commits(struct object_id *oid);
|
2017-12-13 03:53:52 +08:00
|
|
|
extern int fetch_populated_submodules(struct repository *r,
|
|
|
|
const struct argv_array *options,
|
|
|
|
const char *prefix,
|
|
|
|
int command_line_option,
|
|
|
|
int default_option,
|
|
|
|
int quiet, int max_parallel_jobs);
|
2016-12-21 07:20:09 +08:00
|
|
|
extern unsigned is_submodule_modified(const char *path, int ignore_untracked);
|
|
|
|
extern int submodule_uses_gitfile(const char *path);
|
2016-12-21 07:20:11 +08:00
|
|
|
|
|
|
|
#define SUBMODULE_REMOVAL_DIE_ON_ERROR (1<<0)
|
|
|
|
#define SUBMODULE_REMOVAL_IGNORE_UNTRACKED (1<<1)
|
|
|
|
#define SUBMODULE_REMOVAL_IGNORE_IGNORED_UNTRACKED (1<<2)
|
|
|
|
extern int bad_to_remove_submodule(const char *path, unsigned flags);
|
2018-05-16 04:00:28 +08:00
|
|
|
|
|
|
|
int add_submodule_odb(const char *path);
|
pull: optionally rebase submodules (remote submodule changes only)
Teach pull to optionally update submodules when '--recurse-submodules'
is provided. This will teach pull to run 'submodule update --rebase'
when the '--recurse-submodules' and '--rebase' flags are given under
specific circumstances.
On a rebase workflow:
=====================
1. Both sides change the submodule
------------------------------
Let's assume the following history in a submodule:
H---I---J---K---L local branch
\
M---N---O---P remote branch
and the following in the superproject (recorded submodule in parens):
A(H)---B(I)---F(K)---G(L) local branch
\
C(N)---D(N)---E(P) remote branch
In an ideal world this would rebase the submodule and rewrite
the submodule pointers that the superproject points at such that
the superproject looks like
A(H)---B(I) F(K')---G(L') rebased branch
\ /
C(N)---D(N)---E(P) remote branch
and the submodule as:
J---K---L (old dangeling tip)
/
H---I J'---K'---L' rebased branch
\ /
M---N---O---P remote branch
And if a conflict arises in the submodule the superproject rebase
would stop at that commit at which the submodule conflict occurs.
Currently a "pull --rebase" in the superproject produces
a merge conflict as the submodule pointer changes are
conflicting and cannot be resolved.
2. Local submodule changes only
-----------------------
Assuming histories as above, except that the remote branch
would not contain submodule changes, then a result as
A(H)---B(I) F(K)---G(L) rebased branch
\ /
C(I)---D(I)---E(I) remote branch
is desire-able. This is what currently happens in rebase.
If the recursive flag is given, the ideal git would
produce a superproject as:
A(H)---B(I) F(K')---G(L') rebased branch (incl. sub rebase!)
\ /
C(I)---D(I)---E(I) remote branch
and the submodule as:
J---K---L (old dangeling tip)
/
H---I J'---K'---L' locally rebased branch
\ /
M---N---O---P advanced branch
This patch doesn't address this issue, however
a test is added that this fails up front.
3. Remote submodule changes only
----------------------
Assuming histories as in (1) except that the local superproject branch
would not have touched the submodule the rebase already works out in the
superproject with no conflicts:
A(H)---B(I) F(P)---G(P) rebased branch (no sub changes)
\ /
C(N)---D(N)---E(P) remote branch
The recurse flag as presented in this patch would additionally
update the submodule as:
H---I J'---K'---L' rebased branch
\ /
M---N---O---P remote branch
As neither J, K, L nor J', K', L' are referred to from the superproject,
no rewriting of the superproject commits is required.
Conclusion for 'pull --rebase --recursive'
-----------------------------------------
If there are no local superproject changes it is sufficient to call
"submodule update --rebase" as this produces the desired results. In case
of conflicts, the behavior is the same as in 'submodule update --recursive'
which is assumed to be sane.
This patch implements (3) only.
On a merge workflow:
====================
We'll start off with the same underlying DAG as in (1) in the rebase
workflow. So in an ideal world a 'pull --merge --recursive' would
produce this:
H---I---J---K---L----X
\ /
M---N---O---P
with X as the new merge-commit in the submodule and the superproject
as:
A(H)---B(I)---F(K)---G(L)---Y(X)
\ /
C(N)---D(N)---E(P)
However modifying the submodules on the fly is not supported in git-merge
such that Y(X) is not easy to produce in a single patch. In fact git-merge
doesn't know about submodules at all.
However when at least one side does not contain commits touching the
submodule at all, then we do not need to perform the merge for the
submodule but a fast-forward can be done via checking out either L or P
in the submodule. This strategy is implemented in 68d03e4a6e (Implement
automatic fast-forward merge for submodules, 2010-07-07) already, so
to align with the rebase behavior we need to also update the worktree
of the submodule.
Signed-off-by: Brandon Williams <bmwill@google.com>
Signed-off-by: Stefan Beller <sbeller@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2017-06-24 03:13:02 +08:00
|
|
|
|
2018-05-25 04:47:29 +08:00
|
|
|
/*
|
|
|
|
* Checks if there are submodule changes in a..b. If a is the null OID,
|
|
|
|
* checks b and all its ancestors instead.
|
|
|
|
*/
|
pull: optionally rebase submodules (remote submodule changes only)
Teach pull to optionally update submodules when '--recurse-submodules'
is provided. This will teach pull to run 'submodule update --rebase'
when the '--recurse-submodules' and '--rebase' flags are given under
specific circumstances.
On a rebase workflow:
=====================
1. Both sides change the submodule
------------------------------
Let's assume the following history in a submodule:
H---I---J---K---L local branch
\
M---N---O---P remote branch
and the following in the superproject (recorded submodule in parens):
A(H)---B(I)---F(K)---G(L) local branch
\
C(N)---D(N)---E(P) remote branch
In an ideal world this would rebase the submodule and rewrite
the submodule pointers that the superproject points at such that
the superproject looks like
A(H)---B(I) F(K')---G(L') rebased branch
\ /
C(N)---D(N)---E(P) remote branch
and the submodule as:
J---K---L (old dangeling tip)
/
H---I J'---K'---L' rebased branch
\ /
M---N---O---P remote branch
And if a conflict arises in the submodule the superproject rebase
would stop at that commit at which the submodule conflict occurs.
Currently a "pull --rebase" in the superproject produces
a merge conflict as the submodule pointer changes are
conflicting and cannot be resolved.
2. Local submodule changes only
-----------------------
Assuming histories as above, except that the remote branch
would not contain submodule changes, then a result as
A(H)---B(I) F(K)---G(L) rebased branch
\ /
C(I)---D(I)---E(I) remote branch
is desire-able. This is what currently happens in rebase.
If the recursive flag is given, the ideal git would
produce a superproject as:
A(H)---B(I) F(K')---G(L') rebased branch (incl. sub rebase!)
\ /
C(I)---D(I)---E(I) remote branch
and the submodule as:
J---K---L (old dangeling tip)
/
H---I J'---K'---L' locally rebased branch
\ /
M---N---O---P advanced branch
This patch doesn't address this issue, however
a test is added that this fails up front.
3. Remote submodule changes only
----------------------
Assuming histories as in (1) except that the local superproject branch
would not have touched the submodule the rebase already works out in the
superproject with no conflicts:
A(H)---B(I) F(P)---G(P) rebased branch (no sub changes)
\ /
C(N)---D(N)---E(P) remote branch
The recurse flag as presented in this patch would additionally
update the submodule as:
H---I J'---K'---L' rebased branch
\ /
M---N---O---P remote branch
As neither J, K, L nor J', K', L' are referred to from the superproject,
no rewriting of the superproject commits is required.
Conclusion for 'pull --rebase --recursive'
-----------------------------------------
If there are no local superproject changes it is sufficient to call
"submodule update --rebase" as this produces the desired results. In case
of conflicts, the behavior is the same as in 'submodule update --recursive'
which is assumed to be sane.
This patch implements (3) only.
On a merge workflow:
====================
We'll start off with the same underlying DAG as in (1) in the rebase
workflow. So in an ideal world a 'pull --merge --recursive' would
produce this:
H---I---J---K---L----X
\ /
M---N---O---P
with X as the new merge-commit in the submodule and the superproject
as:
A(H)---B(I)---F(K)---G(L)---Y(X)
\ /
C(N)---D(N)---E(P)
However modifying the submodules on the fly is not supported in git-merge
such that Y(X) is not easy to produce in a single patch. In fact git-merge
doesn't know about submodules at all.
However when at least one side does not contain commits touching the
submodule at all, then we do not need to perform the merge for the
submodule but a fast-forward can be done via checking out either L or P
in the submodule. This strategy is implemented in 68d03e4a6e (Implement
automatic fast-forward merge for submodules, 2010-07-07) already, so
to align with the rebase behavior we need to also update the worktree
of the submodule.
Signed-off-by: Brandon Williams <bmwill@google.com>
Signed-off-by: Stefan Beller <sbeller@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2017-06-24 03:13:02 +08:00
|
|
|
extern int submodule_touches_in_range(struct object_id *a,
|
|
|
|
struct object_id *b);
|
2017-03-31 09:40:00 +08:00
|
|
|
extern int find_unpushed_submodules(struct oid_array *commits,
|
2016-12-21 07:20:09 +08:00
|
|
|
const char *remotes_name,
|
|
|
|
struct string_list *needs_pushing);
|
2018-05-17 06:58:23 +08:00
|
|
|
struct refspec;
|
2017-03-31 09:40:00 +08:00
|
|
|
extern int push_unpushed_submodules(struct oid_array *commits,
|
2017-04-06 01:47:19 +08:00
|
|
|
const struct remote *remote,
|
2018-05-17 06:58:23 +08:00
|
|
|
const struct refspec *rs,
|
2017-04-06 01:47:16 +08:00
|
|
|
const struct string_list *push_options,
|
2016-11-18 02:46:04 +08:00
|
|
|
int dry_run);
|
2017-03-26 10:42:30 +08:00
|
|
|
/*
|
|
|
|
* Given a submodule path (as in the index), return the repository
|
|
|
|
* path of that submodule in 'buf'. Return -1 on error or when the
|
|
|
|
* submodule is not initialized.
|
|
|
|
*/
|
|
|
|
int submodule_to_gitdir(struct strbuf *buf, const char *submodule);
|
2009-10-19 20:38:32 +08:00
|
|
|
|
2017-03-15 05:46:37 +08:00
|
|
|
#define SUBMODULE_MOVE_HEAD_DRY_RUN (1<<0)
|
|
|
|
#define SUBMODULE_MOVE_HEAD_FORCE (1<<1)
|
|
|
|
extern int submodule_move_head(const char *path,
|
|
|
|
const char *old,
|
2018-02-15 02:59:49 +08:00
|
|
|
const char *new_head,
|
2017-03-15 05:46:37 +08:00
|
|
|
unsigned flags);
|
|
|
|
|
2016-04-28 21:38:20 +08:00
|
|
|
/*
|
|
|
|
* Prepare the "env_array" parameter of a "struct child_process" for executing
|
2017-09-21 20:43:37 +08:00
|
|
|
* a submodule by clearing any repo-specific environment variables, but
|
submodule: stop sanitizing config options
The point of having a whitelist of command-line config
options to pass to submodules was two-fold:
1. It prevented obvious nonsense like using core.worktree
for multiple repos.
2. It could prevent surprise when the user did not mean
for the options to leak to the submodules (e.g.,
http.sslverify=false).
For case 1, the answer is mostly "if it hurts, don't do
that". For case 2, we can note that any such example has a
matching inverted surprise (e.g., a user who meant
http.sslverify=true to apply everywhere, but it didn't).
So this whitelist is probably not giving us any benefit, and
is already creating a hassle as people propose things to put
on it. Let's just drop it entirely.
Note that we still need to keep a special code path for
"prepare the submodule environment", because we still have
to take care to pass through $GIT_CONFIG_PARAMETERS (and
block the rest of the repo-specific environment variables).
We can do this easily from within the submodule shell
script, which lets us drop the submodule--helper option
entirely (and it's OK to do so because as a "--" program, it
is entirely a private implementation detail).
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2016-05-05 09:22:19 +08:00
|
|
|
* retaining any config in the environment.
|
2016-04-28 21:38:20 +08:00
|
|
|
*/
|
2016-12-21 07:20:09 +08:00
|
|
|
extern void prepare_submodule_repo_env(struct argv_array *out);
|
2016-04-28 21:38:20 +08:00
|
|
|
|
2016-12-13 03:04:35 +08:00
|
|
|
#define ABSORB_GITDIR_RECURSE_SUBMODULES (1<<0)
|
|
|
|
extern void absorb_git_dir_into_superproject(const char *prefix,
|
|
|
|
const char *path,
|
|
|
|
unsigned flags);
|
2017-03-09 07:07:42 +08:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Return the absolute path of the working tree of the superproject, which this
|
|
|
|
* project is a submodule of. If this repository is not a submodule of
|
|
|
|
* another repository, return NULL.
|
|
|
|
*/
|
|
|
|
extern const char *get_superproject_working_tree(void);
|
|
|
|
|
2009-10-19 20:38:32 +08:00
|
|
|
#endif
|