From: Junio C Hamano <gitster@pobox•com>
To: Duy Nguyen <pclouds@gmail•com>
Cc: git@vger•kernel.org
Subject: Re: [RFC] Code reorgnization
Date: Thu, 17 Mar 2016 09:21:02 -0700 [thread overview]
Message-ID: <xmqqbn6d13f5.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160317111136.GA21745@lanh> (Duy Nguyen's message of "Thu, 17 Mar 2016 18:11:36 +0700")
Duy Nguyen <pclouds@gmail•com> writes:
> Good? Bad? Ugly?
Too fine-grained to induce confusion for things that have to work as
a bridge between two categories (e.g. odb & index). In short, bad
and ugly.
I am OK with a looser classification e.g. (1) things that can be
used without Git at all like strbuf, string-list vs (2) things that
are Git but shared across different subcommands like read-cache,
sha1_file, vs (3) command implementations (e.g. builtin/ and also
standalone).
next prev parent reply other threads:[~2016-03-17 16:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 11:11 [RFC] Code reorgnization Duy Nguyen
2016-03-17 13:32 ` Johannes Schindelin
2016-03-17 13:35 ` Duy Nguyen
2016-03-17 16:21 ` Junio C Hamano [this message]
2016-03-17 17:00 ` Thomas Adam
2016-03-17 17:48 ` Junio C Hamano
2016-03-17 18:37 ` Stefan Beller
2016-03-17 19:10 ` Junio C Hamano
2016-03-17 21:03 ` Pranit Bauva
2016-03-17 21:43 ` John Keeping
2016-03-17 21:49 ` Junio C Hamano
2016-03-18 0:28 ` Duy Nguyen
2016-03-18 5:24 ` Jeff King
2016-03-18 5:59 ` Duy Nguyen
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=xmqqbn6d13f5.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=pclouds@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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