2006-04-21 19:27:34 +02:00
|
|
|
#ifndef BUILTIN_H
|
|
|
|
|
#define BUILTIN_H
|
|
|
|
|
|
|
|
|
|
#ifndef PATH_MAX
|
|
|
|
|
# define PATH_MAX 4096
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
extern const char git_version_string[];
|
|
|
|
|
|
|
|
|
|
void cmd_usage(int show_all, const char *exec_path, const char *fmt, ...)
|
|
|
|
|
#ifdef __GNUC__
|
|
|
|
|
__attribute__((__format__(__printf__, 3, 4), __noreturn__))
|
|
|
|
|
#endif
|
|
|
|
|
;
|
|
|
|
|
|
|
|
|
|
extern int cmd_help(int argc, const char **argv, char **envp);
|
|
|
|
|
extern int cmd_version(int argc, const char **argv, char **envp);
|
|
|
|
|
|
|
|
|
|
extern int cmd_whatchanged(int argc, const char **argv, char **envp);
|
|
|
|
|
extern int cmd_show(int argc, const char **argv, char **envp);
|
|
|
|
|
extern int cmd_log(int argc, const char **argv, char **envp);
|
2006-04-29 08:20:52 +02:00
|
|
|
extern int cmd_diff(int argc, const char **argv, char **envp);
|
2006-04-21 22:19:58 +02:00
|
|
|
extern int cmd_format_patch(int argc, const char **argv, char **envp);
|
2006-04-28 00:37:18 +02:00
|
|
|
extern int cmd_count_objects(int argc, const char **argv, char **envp);
|
2006-04-21 19:27:34 +02:00
|
|
|
|
git builtin "push"
This adds a builtin "push" command, which is largely just a C'ification of
the "git-push.sh" script.
Now, the reason I did it as a built-in is partly because it's yet another
step on relying less on shell, but it's actually mostly because I've
wanted to be able to push to _multiple_ repositories, and the most obvious
and simplest interface for that would seem be to just have a "remotes"
file that has multiple URL entries.
(For "pull", having multiple entries should either just select the first
one, or you could fall back on the others on failure - your choice).
And quite frankly, it just became too damn messy to do that in shell.
Besides, we actually have a fair amount of infrastructure in C, so it just
wasn't that hard to do.
Of course, this is almost totally untested. It probably doesn't work for
anything but the one trial I threw at it. "Simple" doesn't necessarily
mean "obviously correct".
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Signed-off-by: Junio C Hamano <junkio@cox.net>
2006-04-30 06:22:49 +02:00
|
|
|
extern int cmd_push(int argc, const char **argv, char **envp);
|
2006-05-01 08:28:15 +02:00
|
|
|
extern int cmd_grep(int argc, const char **argv, char **envp);
|
Add builtin "git rm" command
This changes semantics very subtly, because it adds a new atomicity
guarantee.
In particular, if you "git rm" several files, it will now do all or
nothing. The old shell-script really looped over the removed files one by
one, and would basically randomly fail in the middle if "-f" was used and
one of the files didn't exist in the working directory.
This C builtin one will not re-write the index after each remove, but
instead remove all files at once. However, that means that if "-f" is used
(to also force removal of the file from the working directory), and some
files have already been removed from the workspace, it won't stop in the
middle in some half-way state like the old one did.
So what happens is that if the _first_ file fails to be removed with "-f",
we abort the whole "git rm". But once we've started removing, we don't
leave anything half done. If some of the other files don't exist, we'll
just ignore errors of removal from the working tree.
This is only an issue with "-f", of course.
I think the new behaviour is strictly an improvement, but perhaps more
importantly, it is _different_. As a special case, the semantics are
identical for the single-file case (which is the only one our test-suite
seems to test).
The other question is what to do with leading directories. The old "git
rm" script didn't do anything, which is somewhat inconsistent. This one
will actually clean up directories that have become empty as a result of
removing the last file, but maybe we want to have a flag to decide the
behaviour?
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Signed-off-by: Junio C Hamano <junkio@cox.net>
2006-05-20 01:19:34 +02:00
|
|
|
extern int cmd_rm(int argc, const char **argv, char **envp);
|
2006-05-17 18:33:32 +02:00
|
|
|
extern int cmd_add(int argc, const char **argv, char **envp);
|
2006-05-18 23:19:20 +02:00
|
|
|
extern int cmd_rev_list(int argc, const char **argv, char **envp);
|
2006-05-18 14:15:55 +02:00
|
|
|
extern int cmd_check_ref_format(int argc, const char **argv, char **envp);
|
2006-05-19 12:03:57 +02:00
|
|
|
extern int cmd_init_db(int argc, const char **argv, char **envp);
|
2006-05-19 03:46:44 +02:00
|
|
|
extern int cmd_tar_tree(int argc, const char **argv, char **envp);
|
|
|
|
|
extern int cmd_upload_tar(int argc, const char **argv, char **envp);
|
git builtin "push"
This adds a builtin "push" command, which is largely just a C'ification of
the "git-push.sh" script.
Now, the reason I did it as a built-in is partly because it's yet another
step on relying less on shell, but it's actually mostly because I've
wanted to be able to push to _multiple_ repositories, and the most obvious
and simplest interface for that would seem be to just have a "remotes"
file that has multiple URL entries.
(For "pull", having multiple entries should either just select the first
one, or you could fall back on the others on failure - your choice).
And quite frankly, it just became too damn messy to do that in shell.
Besides, we actually have a fair amount of infrastructure in C, so it just
wasn't that hard to do.
Of course, this is almost totally untested. It probably doesn't work for
anything but the one trial I threw at it. "Simple" doesn't necessarily
mean "obviously correct".
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Signed-off-by: Junio C Hamano <junkio@cox.net>
2006-04-30 06:22:49 +02:00
|
|
|
|
2006-04-21 19:27:34 +02:00
|
|
|
#endif
|