All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>
Cc: Neal Kreitzinger <neal@rsss.com>, git@vger.kernel.org
Subject: Re: scan entire repo for changes to file
Date: Thu, 11 Nov 2010 19:44:34 -0600	[thread overview]
Message-ID: <20101112014434.GA10679@burratino> (raw)
In-Reply-To: <AANLkTi=uKhrvAS6ApnmCZnfbFboYU77rNcKDpaSBn1id@mail.gmail.com>

Martin von Zweigbergk wrote:
> On Thu, Nov 11, 2010 at 8:28 PM, Neal Kreitzinger <neal@rsss.com> wrote:

>> Is there a way to scan my entire repo (many unmerged branches) for any
>> changes to a file?
>> e.g.
>> $ git log * -- somepath/myblob
>> would return all commits in the repo that changed myblob.
>
> Might replacing '*' by '--all' give you what are looking for?

Probably with --full-history if you want to know what happened on
historic branches, too.

  reply	other threads:[~2010-11-12  1:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-12  1:28 scan entire repo for changes to file Neal Kreitzinger
2010-11-12  1:35 ` Martin von Zweigbergk
2010-11-12  1:44   ` Jonathan Nieder [this message]
2010-11-16 17:48     ` Junio C Hamano
2010-11-16 18:20       ` Jonathan Nieder
2010-11-18  0:47         ` Neal Kreitzinger

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=20101112014434.GA10679@burratino \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=martin.von.zweigbergk@gmail.com \
    --cc=neal@rsss.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.