Fellow developers,
Thanks to all who responded to my “basic question”. I now have a much better
idea (actually 2) of how releases can be documented when using git for version
control. I appreciate your taking the time to help me on the learning path.
Jim Vahl
--
To unsubscribe from
: A basic question
On Wed, 2012-10-10 at 11:03 -0700, Jim Vahl wrote:
All,
Our company is researching version control software, something which
we have not used previously. I have a very basic question about git
which I have not been able to answer from reading. As I understand
it, a git
-
From: Drew Northup [mailto:drew.nort...@maine.edu]
Sent: Wednesday, October 10, 2012 12:37 PM
To: Jim Vahl
Cc: git@vger.kernel.org; 'Skot Davis'
Subject: Re: A basic question
On Wed, 2012-10-10 at 11:03 -0700, Jim Vahl wrote:
All,
Our company is researching version control software
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
On Thu, Oct 11, 2012 at 11:08 PM, Jim Vahl j...@wmdb.com wrote:
Drew,
Thanks for responding to my email!
Yes, I did read most of the Book, although I admit that I skimmed over some
of the more technical parts. There is still a key part of how git is used
in a commercial environment which I
On Thu, Oct 11, 2012 at 10:38 AM, Jim Vahl j...@wmdb.com wrote:
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
6 matches
Mail list logo
