mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Andrew Morton <akpm@osdl.org>,
	Andries Brouwer <Andries.Brouwer@cwi.nl>,
	chrisw@osdl.org, aebr@win.tue.nl,
	"Randy.Dunlap" <rddunlap@osdl.org>, Greg KH <greg@kroah.com>,
	joecool1029@gmail.com,
	SCSI Mailing List <linux-scsi@vger.kernel.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Empty partition nodes not created (was device node issues with recent mm's and udev)
Date: Fri, 06 May 2005 15:26:59 +0100	[thread overview]
Message-ID: <1115389619.16187.222.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <1115388767.4989.2.camel@mulgrave>

On Fri, 2005-05-06 at 09:12 -0500, James Bottomley wrote:
> Well, moving offtopic, but it is of relevance to people who use git.
> The answer is that the information exists (we can use the commit tree
> to reconstruct the file data) but that no-one has yet come up with a
> file history viewing tool.  I think David Woodhouse is the closest to
> producing one of these, David?

I posted a script which produces output along the lines of rev-tree's,
but which lists only commits relevant to a given file. However it lacked
correct information about the _branchpoint_ when branches were taken.
You could track the merges but not the full graph.

To do it properly would involve a modified version of rev-tree which
marks the 'interesting' commits and then prunes the uninteresting parts
before dumping what's left. I haven't got as far as _implementing_ that
yet.

-- 
dwmw2


  reply	other threads:[~2005-05-06 14:27 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-03  2:51 Joe
2005-05-03  3:14 ` Greg KH
2005-05-03  3:26   ` Randy.Dunlap
2005-05-03  4:18     ` Joe
2005-05-03  5:16       ` Randy.Dunlap
2005-05-06  8:04       ` Andries Brouwer
2005-05-06 16:43         ` Bryan Henderson
2005-05-03 10:55     ` Paulo Marques
2005-05-03 23:34       ` Joe
2005-05-06  8:00     ` Andries Brouwer
2005-05-06  8:10       ` Chris Wright
2005-05-06  8:43         ` Andries Brouwer
2005-05-06  9:05           ` Andrew Morton
2005-05-06 14:12             ` James Bottomley
2005-05-06 14:26               ` David Woodhouse [this message]
2005-05-06 14:34               ` Kay Sievers
2005-05-06 14:18             ` Kay Sievers
2005-05-06 15:50         ` Greg KH
2005-05-06  7:58   ` Andries Brouwer
2005-05-06  7:57 ` Andries Brouwer
     [not found] <3ZVNP-5cq-7@gated-at.bofh.it>
2005-05-04  3:36 ` Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>
2005-05-04  3:49   ` Joe
2005-05-04  4:47     ` Grant Coady
2005-05-04 11:42     ` Bodo Eggert

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=1115389619.16187.222.camel@hades.cambridge.redhat.com \
    --to=dwmw2@infradead.org \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=James.Bottomley@SteelEye.com \
    --cc=aebr@win.tue.nl \
    --cc=akpm@osdl.org \
    --cc=chrisw@osdl.org \
    --cc=greg@kroah.com \
    --cc=joecool1029@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rddunlap@osdl.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®