A general strategy for this type of problem is to add this information to the
files during the build or deploy phase - i.e. at the point where the file
leaves the repository to venture out into the wild.
I use, for example "hg log -v -l 1" to replace a tag in my files when I deploy
something
On Thu, Aug 23, 2018 at 09:34:04AM -0700, Michael Brininstool wrote:
> Wow! How condescending of you! In my 35 years of programming and system
> administration, tagging a script or config file with a label that
> identifies which "version" it is, is essential. When you deploy these
> files
Wow! How condescending of you! In my 35 years of programming and system
administration, tagging a script or config file with a label that
identifies which "version" it is, is essential. When you deploy these
files to 10's of thousand of servers, and problems crop up over the years,
being
On 15/05/2014 23:39, Magnus Therning wrote:
On Thu, May 15, 2014 at 11:21:25PM +0100, Andy Hardy wrote:
On 15/05/2014 22:48, Magnus Therning wrote:
- version: doesn't make sense in git, would it be the hash?
what does that tell me?
I find an identifier useful when investigating problems
On Friday, May 16, 2014 12:52:44 AM UTC+2, Magnus Therning wrote:
I must say though that your example might constitute another argument
*against* having keywords, that sort of deployment process quickly
leads to a mess ;)
Yeah, the fallacy was that it was easier to deploy one file than to
On Fri, May 16, 2014 at 8:22 AM, Andy Hardy a...@hardyfamily.org.uk wrote:
On 15/05/2014 23:39, Magnus Therning wrote:
On Thu, May 15, 2014 at 11:21:25PM +0100, Andy Hardy wrote:
On 15/05/2014 22:48, Magnus Therning wrote:
- version: doesn't make sense in git, would it be the hash?
what does
On Friday, May 16, 2014 8:22:30 AM UTC+2, Andy wrote:
For a 'release' we'd send the customer a complete set of files, but
often a fix only requires one or two files to be modified which we ask
the customer to install. When a dealing with a later fault, we'd like to
have a method of knowing
On Friday, May 16, 2014 10:45:10 AM UTC+2, Thomas Ferris Nicolaisen wrote:
On Friday, May 16, 2014 8:22:30 AM UTC+2, Andy wrote:
For a 'release' we'd send the customer a complete set of files, but
often a fix only requires one or two files to be modified which we ask
the customer to
On Thu, May 15, 2014 at 01:21:26PM -0700, Alain wrote:
Hi,
i would like to know if it is possible (and if yes, how to do it) to
retrieve for example tag information or file version from GIT in
order to automatically generate/append a file header to each file in
order to allow traceability.
On 15/05/2014 22:48, Magnus Therning wrote:
- version: doesn't make sense in git, would it be the hash? what does
that tell me?
I find an identifier useful when investigating problems and wanting to
confirm what files are involved.
--
You received this message because you are
On Thursday, May 15, 2014 11:48:17 PM UTC+2, Magnus Therning wrote:
I'd be very interested in hearing your use case for having that info
in the file. I'd love to be convinced that all those other VCSs
haven't wasted effort on implementing a rather useless feature :)
This is not my
On Thu, May 15, 2014 at 11:21:25PM +0100, Andy Hardy wrote:
On 15/05/2014 22:48, Magnus Therning wrote:
- version: doesn't make sense in git, would it be the hash? what does
that tell me?
I find an identifier useful when investigating problems and wanting
to confirm what files are
12 matches
Mail list logo
