git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: sithglan@stud.uni-erlangen.de, seanlkml@sympatico.ca,
	sam@ravnborg.org, git@vger.kernel.org
Subject: Re: cogito - how do I ???
Date: Mon, 23 May 2005 20:05:24 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0505232000400.2307@ppc970.osdl.org> (raw)
In-Reply-To: <E1DaP7k-0007ar-00@gondolin.me.apana.org.au>



On Tue, 24 May 2005, Herbert Xu wrote:
> 
> Yes please.  Can we also have a rev-* command that outputs parent
> relations instead of a simple list? That is,
> 
> <tree-1> <parent-1>
> <tree-1> <parent-2>
> <tree-2> <parent-3>

That's not <tree-n>, it's <commit-n>.

I think that would be "git-rev-list --parents" or something - that 
wouldn't impact any existing users.

Patches welcome.

As to git-rev-tree, that's likely used by scripts in various places 
(cogito, gitk, gitweb etc), so changing that is nastier, but at least the 
output could be _sorted_ better.

Of course, I really think that the bigger problem with git-rev-tree
currently is that global reachability analysis, which is just not
acceptable performance-wise.

		Linus

  reply	other threads:[~2005-05-24  3:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-21 21:47 cogito - how do I ??? Sam Ravnborg
2005-05-21 22:06 ` Sean
2005-05-21 23:41   ` Linus Torvalds
2005-05-22  7:14     ` Sam Ravnborg
2005-05-22 16:23       ` Linus Torvalds
2005-05-23  7:19     ` Thomas Glanzmann
2005-05-23  7:40       ` Junio C Hamano
2005-05-23  8:02         ` Thomas Glanzmann
2005-05-23 14:35       ` Linus Torvalds
2005-05-23 16:34         ` Junio C Hamano
2005-05-24  2:26         ` Herbert Xu
2005-05-24  3:05           ` Linus Torvalds [this message]
2005-05-22  5:27   ` Frank Sorenson

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=Pine.LNX.4.58.0505232000400.2307@ppc970.osdl.org \
    --to=torvalds@osdl.org \
    --cc=git@vger.kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=sam@ravnborg.org \
    --cc=seanlkml@sympatico.ca \
    --cc=sithglan@stud.uni-erlangen.de \
    /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).