From: Enrico Weigelt <enrico.weigelt@vnc.biz>
To: Jim Vahl <jv@wmdb.com>
Cc: Skot Davis <skotd122@gmail.com>,
git@vger.kernel.org, Drew Northup <drew.northup@maine.edu>
Subject: Re: A basic question
Date: Thu, 11 Oct 2012 20:51:45 +0200 (CEST) [thread overview]
Message-ID: <d89615b8-d153-41c9-963d-127a614321cb@zcs> (raw)
In-Reply-To: <002801cda7d7$4792c260$d6b84720$@com>
> 1) Does git have a built-in way to get a list of all of the "most
> recently
> committed" files only at a given point in time, thus automatically
> recording
> the revisions of all of the component files of a release?
There is no concept of per-file revisions in git.
But you can check which ones are changed in multiple ways, eg:
* per commit, commit-range or per-branch level -> see git-log manpage
* between arbitratry commints -> see git-diff manpage
> This implies that for files which are being modified or which have
> been staged but not committed, that git would go back to find the
> "predecessor" file which had been committed.
Forget about the staging issue (index) at this point - it's just
existing in the _local_ clone (eg of some individual developer),
for your usecase you're only interested in what's actually committed
to certain branch(es).
cu
--
Mit freundlichen Grüßen / Kind regards
Enrico Weigelt
VNC - Virtual Network Consult GmbH
Head Of Development
Pariser Platz 4a, D-10117 Berlin
Tel.: +49 (30) 3464615-20
Fax: +49 (30) 3464615-59
enrico.weigelt@vnc.biz; www.vnc.de
next prev parent reply other threads:[~2012-10-11 18:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 18:03 A basic question Jim Vahl
2012-10-10 19:36 ` Drew Northup
2012-10-11 17:38 ` Jim Vahl
2012-10-11 18:40 ` James Nylen
2012-10-11 18:51 ` Enrico Weigelt [this message]
2012-10-12 0:58 ` Sitaram Chamarty
2012-10-12 1:08 ` PJ Weisberg
[not found] ` <CA++fsGFruWFauX3XkynwcRLqK9H16frW86of3Y3ScgzGFmz=dg@mail.gmail.com>
2012-10-11 18:46 ` Dov Grobgeld
2012-10-12 15:56 ` A basic question - Thanks to all responders Jim Vahl
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=d89615b8-d153-41c9-963d-127a614321cb@zcs \
--to=enrico.weigelt@vnc.biz \
--cc=drew.northup@maine.edu \
--cc=git@vger.kernel.org \
--cc=jv@wmdb.com \
--cc=skotd122@gmail.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.
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).