From: Stephan Beyer <s-beyer@gmx.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] editor.c: Libify launch_editor()
Date: Thu, 24 Jul 2008 03:48:14 +0200 [thread overview]
Message-ID: <20080724014814.GA8730@leksak.fem-net> (raw)
In-Reply-To: <20080723230923.GA12754@leksak.fem-net>
Stephan Beyer wrote:
> Well, I've seen that *a lot* of lib code (15 functions, see below) is in
> the builtins.
>
> Cleaning that up seems to be good to have a real separation between
> libgit and builtins, but I guess such a change would not find its way
> into 1.6.0, would it?
>
> Regards,
> Stephan
>
> PS: I've spontaneously decided to make a list:
>
> defined-in func-name - used in builtin-\1.c
Of course my list was not complete.
(My regex was too simple.)
I add some:
> builtin-add.c:
> add_files_to_cache() - add, checkout, commit
> interactive_add() - add, commit
>
> builtin-archive.c:
> parse_pathspec_arg() - archive, upload-archive
parse_treeish_arg() - archive, upload-archive
parse_archive_args() - archive, upload-archive
builtin-commit-tree.c:
commit_tree() - commit-tree, merge
builtin-fetch-pack.c:
fetch_pack() - also used in transport.c
> builtin-init-db.c:
> init_db() - init-db, clone
>
> builtin-ls-files.c:
> overlay_tree_on_cache() - ls-files, commit
> report_path_error() - ls-files, checkout, commit
pathspec_match() - ls-files, checkout, commit
> builtin-mailsplit.c:
> read_line_with_nul() - mailsplit, mailinfo
>
> builtin-merge-recursive.c:
> write_tree_from_memory() - merge-recursive, checkout
merge_trees() - merge-recursive, checkout
merge_recursive() - merge-recursive (used nowhere else)
> builtin-prune-packed.c:
> prune_packed_objects() - prune-packed, prune
builtin-send-pack.c:
send_pack() - also used in transport.c
> builtin-shortlog.c:
> shortlog_add_commit() - shortlog, log
> shortlog_init() - shortlog, log
> shortlog_output() - shortlog, log
> shortlog_init() - shortlog, log
>
> builtin-stripspace.c:
> stripspace() - stripspace, commit, tag
>
> And launch_editor() that is handled by the patch in this thread.
So keep everything or is it worth splitting that somehow up?
Regards.
--
Stephan Beyer <s-beyer@gmx.net>, PGP 0x6EDDD207FCC5040F
next prev parent reply other threads:[~2008-07-24 1:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 0:36 [PATCH] Move launch_editor() from builtin-tag.c to editor.c Stephan Beyer
2008-07-18 1:14 ` Johannes Schindelin
2008-07-18 1:26 ` Stephan Beyer
2008-07-18 11:26 ` [PATCH] editor.c: Libify launch_editor() Stephan Beyer
2008-07-18 12:07 ` Johannes Schindelin
2008-07-18 12:35 ` [PATCH v2] " Stephan Beyer
2008-07-23 23:09 ` [PATCH] " Stephan Beyer
2008-07-24 1:48 ` Stephan Beyer [this message]
2008-07-25 8:36 ` Junio C Hamano
2008-07-25 10:28 ` Johannes Schindelin
2008-07-25 14:15 ` Stephan Beyer
2008-07-25 14:36 ` Johannes Schindelin
2008-07-25 16:28 ` [PATCH 1/2] Move launch_editor() from builtin-tag.c to editor.c Stephan Beyer
2008-07-25 16:28 ` [PATCH 2/2] editor.c: Libify launch_editor() Stephan Beyer
2008-07-25 17:16 ` Stephan Beyer
2008-07-26 3:00 ` [PATCH 1/2] Move launch_editor() from builtin-tag.c to editor.c Johannes Schindelin
2008-07-26 3:14 ` Stephan Beyer
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=20080724014814.GA8730@leksak.fem-net \
--to=s-beyer@gmx.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).