From: Felipe Contreras <felipe.contreras@gmail.com>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>,
Brandon Casey <drafnel@gmail.com>,
Jonathan Nieder <jrnieder@gmail.com>,
Ramkumar Ramachandra <artagnon@gmail.com>
Subject: Re: [PATCH 2/2] Move sequencer to builtin
Date: Sat, 8 Jun 2013 08:28:44 -0500 [thread overview]
Message-ID: <CAMP44s0EVESLfRUw7Aqz6VjXELcRG-6cETpcROTZXmPjU-Y8ig@mail.gmail.com> (raw)
In-Reply-To: <CACsJy8CQRWU0mFLVD6RrpzJiHBH=9zFwf5xDo7UhGW6A-OAzuw@mail.gmail.com>
On Sat, Jun 8, 2013 at 7:34 AM, Duy Nguyen <pclouds@gmail.com> wrote:
> On Sat, Jun 8, 2013 at 7:25 PM, Felipe Contreras
> <felipe.contreras@gmail.com> wrote:
>> On Sat, Jun 8, 2013 at 6:42 AM, Duy Nguyen <pclouds@gmail.com> wrote:
>>> On Sat, Jun 8, 2013 at 5:14 PM, Felipe Contreras
>>> <felipe.contreras@gmail.com> wrote:
>>>> On Fri, Jun 7, 2013 at 9:35 PM, Duy Nguyen <pclouds@gmail.com> wrote:
>>>>> On Sat, Jun 8, 2013 at 5:16 AM, Felipe Contreras
>>>>> <felipe.contreras@gmail.com> wrote:
>>>>>> This code is only useful for cherry-pick and revert built-ins, nothing
>>>>>> else, so let's make it a builtin object, but make sure 'git-sequencer'
>>>>>> is not generated.
>>>>>
>>>>> As you can see, the convention is builtin/foo.c corresponds to git-foo
>>>>> (and maybe more). Why make an exception for sequencer?
>>>>
>>>> Why not?
>>>
>>> And while we are at "why not", why don't you fork git?
>>
>> That's not an answer.
>
> Neither is "Why not?"
The answer is the rest of the e-mail.
>>> and not meant to be. If you aim something more organized,
>>> please show at least a roadmap what to move where.
>>
>> I already did that; we move code from libgit.a to builtin/*.o
>
> what code besides sequencer.c?
A roadmap doesn't require code. If you truly think that there's
nothing else that is specific to builtins; alias.c.
>> until libgit.a == libgit2. Done.
>
> Read up about the introduction of libgit2, why it was created in the
> first place instead of moving a few files around renaming libgit.a to
> libgit2.a. Unless you have a different definition of "==" than I do.
Are you being obtuse on purpose? It doesn't matter how different
libgit.a and libgit2 currently are, there's always a path from one
code-base to another. Unless libgit2 has code for builtin commands,
the first step would invariably be to move the code that is specific
for builtins to builtin/*.o.
--
Felipe Contreras
next prev parent reply other threads:[~2013-06-08 13:28 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 22:16 [PATCH 0/2] Move sequencer Felipe Contreras
2013-06-07 22:16 ` [PATCH 1/2] log-tree: remove dependency from sequencer Felipe Contreras
2013-06-07 22:16 ` [PATCH 2/2] Move sequencer to builtin Felipe Contreras
2013-06-08 2:35 ` Duy Nguyen
2013-06-08 10:14 ` Felipe Contreras
2013-06-08 11:42 ` Duy Nguyen
2013-06-08 12:25 ` Felipe Contreras
2013-06-08 12:34 ` Duy Nguyen
2013-06-08 12:55 ` Ramkumar Ramachandra
2013-06-08 13:15 ` Duy Nguyen
2013-06-08 13:32 ` Felipe Contreras
2013-06-08 13:34 ` Ramkumar Ramachandra
2013-06-08 14:10 ` Felipe Contreras
2013-06-08 14:10 ` Duy Nguyen
2013-06-08 14:20 ` Felipe Contreras
2013-06-09 4:34 ` Jeff King
2013-06-09 9:58 ` Ramkumar Ramachandra
2013-06-09 17:55 ` Jeff King
2013-06-09 18:06 ` Ramkumar Ramachandra
2013-06-09 18:11 ` Felipe Contreras
2013-06-09 18:22 ` Jeff King
2013-06-09 18:29 ` Felipe Contreras
2013-06-09 18:44 ` Ramkumar Ramachandra
2013-06-09 18:49 ` Jeff King
2013-06-09 18:54 ` Felipe Contreras
2013-06-09 18:07 ` Felipe Contreras
2013-06-09 12:09 ` Felipe Contreras
2013-06-08 13:28 ` Felipe Contreras [this message]
2013-06-08 16:49 ` Jonathan Nieder
2013-06-08 17:06 ` Felipe Contreras
2013-06-08 17:34 ` Jonathan Nieder
2013-06-08 17:44 ` Felipe Contreras
2013-06-08 19:15 ` Felipe Contreras
2013-06-09 1:40 ` Jonathan Nieder
2013-06-09 2:17 ` Felipe Contreras
2013-06-09 3:21 ` Jonathan Nieder
2013-06-09 3:34 ` Felipe Contreras
2013-06-09 5:26 ` Jeff King
2013-06-09 12:15 ` Felipe Contreras
2013-06-09 17:40 ` Jeff King
2013-06-09 18:01 ` Felipe Contreras
2013-06-09 18:10 ` Jeff King
2013-06-09 18:16 ` Felipe Contreras
2013-06-09 19:11 ` Johan Herland
2013-06-09 19:29 ` Felipe Contreras
2013-06-09 21:42 ` Michael Haggerty
2013-06-09 23:40 ` Stefano Lattarini
2013-06-10 5:15 ` Felipe Contreras
2013-06-10 9:05 ` Bad attitudes and problems in the Git community (was: Re: [PATCH 2/2] Move sequencer to builtin) Stefano Lattarini
2013-06-10 16:58 ` Felipe Contreras
2013-06-10 18:11 ` Martin von Zweigbergk
2013-06-10 18:33 ` Martin Langhoff
2013-06-10 18:40 ` Martin von Zweigbergk
2013-06-10 21:34 ` Felipe Contreras
2013-06-10 5:12 ` [PATCH 2/2] Move sequencer to builtin Felipe Contreras
2013-06-11 9:18 ` Andres Freund
2013-06-11 9:29 ` Felipe Contreras
2013-06-20 21:11 ` Thiago Farina
2013-06-09 17:53 ` Thomas Rast
2013-06-09 18:03 ` Felipe Contreras
2013-06-09 12:48 ` Ramkumar Ramachandra
2013-06-09 13:08 ` Felipe Contreras
2013-06-09 18:04 ` Jeff King
2013-06-09 18:32 ` Ramkumar Ramachandra
2013-06-09 18:45 ` Jeff King
2013-06-09 19:57 ` Jonathan Nieder
2013-06-09 20:07 ` Felipe Contreras
2013-06-09 20:34 ` Ramkumar Ramachandra
2013-06-09 21:39 ` Junio C Hamano
2013-06-10 5:06 ` Felipe Contreras
2013-06-10 8:32 ` Junio C Hamano
2013-06-10 16:53 ` Felipe Contreras
2013-06-10 16:55 ` Felipe Contreras
2013-06-10 17:34 ` Matthieu Moy
2013-06-10 18:09 ` Ramkumar Ramachandra
2013-06-10 21:43 ` Felipe Contreras
2013-06-09 18:48 ` Felipe Contreras
2013-06-09 19:25 ` Thomas Rast
2013-06-09 19:54 ` Ramkumar Ramachandra
2013-06-09 20:02 ` Felipe Contreras
2013-06-08 3:35 ` [PATCH 0/2] Move sequencer Ramkumar Ramachandra
2013-06-08 10:26 ` Felipe Contreras
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMP44s0EVESLfRUw7Aqz6VjXELcRG-6cETpcROTZXmPjU-Y8ig@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=artagnon@gmail.com \
--cc=drafnel@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=pclouds@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).