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 this list
On Thu, Oct 11, 2012 at 10:38 AM, Jim Vahl 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 for files
On Thu, Oct 11, 2012 at 11:08 PM, Jim Vahl 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 don't
> 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 o
s "No", then what is the normal way
> for a programming shop which is using git to extract/assemble the list of
> approved files for building a release?
>
> Thank you.
>
> Jim Vahl
>
> -----Original Message-
> From: Drew Northup [mailto:drew.nort...@maine.edu]
>
On 10/11/2012 1:38 PM, Jim Vahl wrote:
For the sake of argument, I'll assume that a committing a change implies
that the file has passed the testing process. So my questions are:
You should not assume this. You / your developers should commit far
more frequently than you test and release vers
, 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, something which
> we have not used previously. I have a ve
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 repository
> can
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 repository
can be a mixture of files which are under development, staged or c
9 matches
Mail list logo