From: Daniel Barkalow <barkalow@iabervon.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: [PATCH 7/9] Export create_branch() from builtin-branch.c
Date: Mon, 4 Feb 2008 13:36:02 -0500 (EST) [thread overview]
Message-ID: <alpine.LNX.1.00.0802041336010.13593@iabervon.org> (raw)
You can also create branches, in exactly the same way, with checkout -b.
Signed-off-by: Daniel Barkalow <barkalow@iabervon.org>
---
builtin-branch.c | 4 ++--
cache.h | 4 ++++
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/builtin-branch.c b/builtin-branch.c
index 089cae5..04e377d 100644
--- a/builtin-branch.c
+++ b/builtin-branch.c
@@ -422,8 +422,8 @@ static int setup_tracking(const char *new_ref, const char *orig_ref)
return 0;
}
-static void create_branch(const char *name, const char *start_name,
- int force, int reflog, int track)
+void create_branch(const char *name, const char *start_name,
+ int force, int reflog, int track)
{
struct ref_lock *lock;
struct commit *commit;
diff --git a/cache.h b/cache.h
index e4aeff0..97edbf1 100644
--- a/cache.h
+++ b/cache.h
@@ -680,6 +680,10 @@ extern int convert_to_working_tree(const char *path, const char *src, size_t len
/* add */
void add_files_to_cache(int verbose, const char *prefix, const char **pathspec);
+/* branch */
+void create_branch(const char *name, const char *start_name,
+ int force, int reflog, int track);
+
/* diff.c */
extern int diff_auto_refresh_index;
--
1.5.4
next reply other threads:[~2008-02-04 18:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 18:36 Daniel Barkalow [this message]
2008-02-05 1:38 ` [PATCH 7/9] Export create_branch() from builtin-branch.c Johannes Schindelin
2008-02-05 20:39 ` Daniel Barkalow
-- strict thread matches above, loose matches on Subject: below --
2008-01-25 23:25 Daniel Barkalow
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=alpine.LNX.1.00.0802041336010.13593@iabervon.org \
--to=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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