git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Denton Liu <liu.denton@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH v2 0/2] Lib-ify functions in builtin.h
Date: Mon, 23 Mar 2020 21:07:50 -0400	[thread overview]
Message-ID: <cover.1585011949.git.liu.denton@gmail.com> (raw)
In-Reply-To: <cover.1584786523.git.liu.denton@gmail.com>

Since the last revision, I tried to rewrite the commit messages to be
more subjective but I was also having some trouble with it.

In builtin.h, there exist a couple of functions that are very "lib-ish".
These functions can currently only be called by built-in commands but,
unlike all of the other functions in the header, it does not make sense
to impose this restriction as their functionality can be logically reused
in libgit.

Extract these functions into their own files which should make more
organizational sense.

Changes since v1:

* Rewrite commit messages to be less subjective

Denton Liu (2):
  Lib-ify fmt-merge-msg
  Lib-ify prune-packed

 Makefile                |   2 +
 builtin.h               |  16 -
 builtin/fmt-merge-msg.c | 655 +---------------------------------------
 builtin/prune-packed.c  |  44 +--
 builtin/prune.c         |   1 +
 builtin/repack.c        |   1 +
 fmt-merge-msg.c         | 653 +++++++++++++++++++++++++++++++++++++++
 fmt-merge-msg.h         |  13 +
 prune-packed.c          |  43 +++
 prune-packed.h          |   9 +
 10 files changed, 724 insertions(+), 713 deletions(-)
 create mode 100644 fmt-merge-msg.c
 create mode 100644 prune-packed.c
 create mode 100644 prune-packed.h

Range-diff against v1:
1:  d989ab8b08 ! 1:  fe76d79aa7 Lib-ify fmt-merge-msg
    @@ Metadata
      ## Commit message ##
         Lib-ify fmt-merge-msg
     
    -    In builtin.h, there exists the distinctly lib-ish function
    -    fmt_merge_msg(). Extract this function into fmt-merge-msg.c so that
    -    related definitions can exist clearly in their own header file.
    +    In builtin.h, there exists the distinctly "lib-ish" function
    +    fmt_merge_msg(). This function can currently only be called by built-in
    +    commands but, unlike most of the other functions in the header, it does
    +    not make sense to impose this restriction as the functionality can be
    +    logically reused in libgit.
    +
    +    Extract this function into fmt-merge-msg.c so that related definitions
    +    can exist clearly in their own header file.
     
         While we're at it, clean up #includes that are unused.
     
2:  249dbb9420 ! 2:  c6a80ce882 Lib-ify prune-packed
    @@ Commit message
         Lib-ify prune-packed
     
         In builtin.h, there exists the distinctly lib-ish function
    -    prune_packed_objects(). Extract this function into prune-packed.c so that
    -    related definitions can exist clearly in their own header file.
    +    prune_packed_objects(). This function can currently only be called by
    +    built-in commands but, unlike all of the other functions in the header,
    +    it does not make sense to impose this restriction as the functionality
    +    can be logically reused in libgit.
    +
    +    Extract this function into prune-packed.c so that related definitions
    +    can exist clearly in their own header file.
     
         While we're at it, clean up #includes that are unused.
     
-- 
2.25.0.114.g5b0ca878e0


  parent reply	other threads:[~2020-03-24  1:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-21 10:29 [PATCH 0/2] Lib-ify functions in builtin.h Denton Liu
2020-03-21 10:29 ` [PATCH 1/2] Lib-ify fmt-merge-msg Denton Liu
2020-03-21 10:29 ` [PATCH 2/2] Lib-ify prune-packed Denton Liu
2020-03-21 19:24 ` [PATCH 0/2] Lib-ify functions in builtin.h Junio C Hamano
2020-03-24  1:07 ` Denton Liu [this message]
2020-03-24  1:07   ` [PATCH v2 1/2] Lib-ify fmt-merge-msg Denton Liu
2020-03-24  1:07   ` [PATCH v2 2/2] Lib-ify prune-packed Denton Liu

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=cover.1585011949.git.liu.denton@gmail.com \
    --to=liu.denton@gmail.com \
    --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).