git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Alangi Derick <alangiderick@gmail.com>
To: git@vger.kernel.org
Subject: Re: Suggestion to add a new command(git print-tree)
Date: Mon, 25 May 2015 17:25:46 +0100	[thread overview]
Message-ID: <CAKB+oNtV44hoGzVE6F6=wu_JGy0N2C6B9S06nn92CYo6mGth0g@mail.gmail.com> (raw)
In-Reply-To: <CAKB+oNtOXJO39QR2ZukMVM8juceBrBeiWLz92eVEOteVO99brA@mail.gmail.com>

Regards
Alangi Derick Ndimnain


On Mon, May 25, 2015 at 5:21 PM, Alangi Derick <alangiderick@gmail.com> wrote:
> With discussions i have on the irc channel(#git) i just noticed there
> is the git ls-tree command but it doesn't format the tree so it will
> be a good thing for the tree to be formatted. I will like to embark on
> the project.
> Regards
> Alangi Derick Ndimnain
>
>
> On Mon, May 25, 2015 at 5:17 PM, Alangi Derick <alangiderick@gmail.com> wrote:
>> Hello everyone,
>>      I will like us to discuss on this topic to add a new command into
>> git that will enable us to print the entire working tree in a git
>> repository. Something similar to work happens when you run the linux
>> command: "pstree".
>>      This is important in searching and also more that i will be
>> discussing while talking about the idea. Thanks and if there is
>> anything to say about this, feel free to comment.
>>
>> Regards
>> Alangi Derick Ndimnain

Sorry for topping post, i forgot. Just like i said above, it will be
good that commands like; git ls-tree, git ls-files and more commands
of git that list directories to do them in a tree-like manner.

      reply	other threads:[~2015-05-25 16:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-25 16:17 Suggestion to add a new command(git print-tree) Alangi Derick
2015-05-25 16:21 ` Alangi Derick
2015-05-25 16:25   ` Alangi Derick [this message]

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='CAKB+oNtV44hoGzVE6F6=wu_JGy0N2C6B9S06nn92CYo6mGth0g@mail.gmail.com' \
    --to=alangiderick@gmail.com \
    --cc=git@vger.kernel.org \
    /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).