git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Sorenson <frank@tuxrocks.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Junio C Hamano <junkio@cox.net>,
	Linus Torvalds <torvalds@osdl.org>,
	git@vger.kernel.org
Subject: Re: How do I...
Date: Fri, 06 May 2005 12:56:23 -0600	[thread overview]
Message-ID: <427BBDD7.90600@tuxrocks.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0505061321590.30848-100000@iabervon.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Daniel Barkalow wrote:
> On Fri, 6 May 2005, Frank Sorenson wrote:
> 
> 
>>Note that I could be just thinking about this all wrong, so my
>>terminology could be in left field.  Here, I'm mostly just interested in
>>the case where "Hey, something broke with drivers/char/i8k.c.  When was
>>this changed?  Who changed what?"
> 
> 
> The tricky thing is that you want to *not* see commits where somebody
> adopted somebody else's change to drivers/char/i8k.c; you want to ignore
> those commits in favor of the commits where the original author of the
> changes made the changes. Otherwise, you mostly see merges with people
> submitting lines where they didn't change that file.

True.  At least usually.  Sometimes, though, we'll want to see the
entire history of the file, so we can see when it went (for example)
into Greg K-H's tree, then when Linus pulls into his tree, etc.  I guess
that makes "just when the file itself has actually changed" a special
case of the entire history of a particular file.

Frank
- --
Frank Sorenson - KD7TZK
Systems Manager, Computer Science Department
Brigham Young University
frank@tuxrocks.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCe73XaI0dwg4A47wRAvxaAJ9E1mFepuHmTfvVfwr8zMwpqqcSZACgsz0M
NVAd1f2ZGzu+NPqD3zDQ3Yo=
=I3EA
-----END PGP SIGNATURE-----

  reply	other threads:[~2005-05-06 18:50 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-06  9:49 How do I Frank Sorenson
2005-05-06  9:59 ` Thomas Glanzmann
2005-05-06 10:03   ` Thomas Glanzmann
2005-05-06 14:37 ` Dave Kleikamp
2005-05-06 16:39   ` Frank Sorenson
2005-05-06 17:58     ` Dave Kleikamp
2005-05-06 19:07       ` Frank Sorenson
2005-05-06 16:13 ` Linus Torvalds
2005-05-06 16:35   ` Junio C Hamano
2005-05-06 16:47     ` Frank Sorenson
2005-05-06 17:31       ` Daniel Barkalow
2005-05-06 18:56         ` Frank Sorenson [this message]
2005-05-06 17:09     ` Linus Torvalds
2005-05-06 18:39       ` David Woodhouse
2005-05-06 18:59         ` Linus Torvalds
2005-05-06 19:10           ` David Woodhouse
2005-05-06 22:57             ` Linus Torvalds
2005-05-06 23:20               ` David Woodhouse
2005-05-06 23:54                 ` Linus Torvalds
2005-05-07  8:58                   ` David Woodhouse
2005-05-06 19:35           ` Thomas Kolejka
2005-05-06 16:36   ` David Woodhouse
2005-05-07  0:45     ` Benjamin Herrenschmidt
2005-05-06 18:58 ` Linus Torvalds

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=427BBDD7.90600@tuxrocks.com \
    --to=frank@tuxrocks.com \
    --cc=barkalow@iabervon.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=torvalds@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;
as well as URLs for NNTP newsgroup(s).