Re: A basic question
- From
PJ Weisberg <pj@irregularexpressions.net>
- Date
- Oct 12, 2012, 01:08 UTC
- Message-ID
- <CAJsNXTm3k6YYFLhM9WZo2ZwKQjxWUHKbbbWvVYO_sKvCxsKD6w@mail.gmail.com>
- In-Reply-To
- <002801cda7d7$4792c260$d6b84720$@com>
On Thu, Oct 11, 2012 at 10:38 AM, Jim Vahl <jv@wmdb.com> wrote:
Show 6 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? 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.
I feel like I'm missing the point of your questions. Why do you think your central repository would contain anything that hadn't been committed?
-PJ
Gehm's Corollary to Clark's Law: Any technology distinguishable from magic is insufficiently advanced.