From: Frank Sorenson <frank@tuxrocks.com>
To: git@vger.kernel.org
Subject: How do I...
Date: Fri, 06 May 2005 03:49:39 -0600	[thread overview]
Message-ID: <427B3DB3.4000507@tuxrocks.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Okay, I've got some "How can I?" questions.  I hope I'm not the only one
still working to "git it".
How can I git a list of commits that have modified a particular file?
For example, I'd like to do something like this:
# git-file-revs Makefile
f7eb55878f11575281add2a5726e483aed5e45bb
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
...
How can I output a list of the filename(s) modified by a particular
commit? (for example)
# git-commit-info files 6741f3a7f9922391cd02b3ca1329e669497dc22f
Makefile
file1
arch/file2
Can I use cg-log to output just the information about a particular
commit?  (I don't need all the commits, just the one I'm interested in).
After doing a cg-update, can I cg-log just the changes since the last
update?  Alternatively, how can I tell cg-log I'm caught up, and don't
need anything historical?
Can I do these with git/cogito, or will I need to start diving deeper
into the code?
Thanks,
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
iD8DBQFCez2zaI0dwg4A47wRAuNAAJ0QsBkwwHFbFQshRGSDCLv/pEaZXQCfeZj6
rqC9ZoVAYNeMwKqppbyXx9o=
=pJDl
-----END PGP SIGNATURE-----
next             reply	other threads:[~2005-05-06  9:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-06  9:49 Frank Sorenson [this message]
2005-05-06  9:59 ` How do I 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
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=427B3DB3.4000507@tuxrocks.com \
    --to=frank@tuxrocks.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.
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).