Re: A basic question
- From
Enrico Weigelt <enrico.weigelt@vnc.biz>
- Date
- Oct 11, 2012, 18:51 UTC
- Message-ID
- <d89615b8-d153-41c9-963d-127a614321cb@zcs>
- In-Reply-To
- <002801cda7d7$4792c260$d6b84720$@com>
Show 5 quoted lines
> 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