From: Junio C Hamano <gitster@pobox.com>
To: Eugene Sajine <euguess@gmail.com>
Cc: Alex Riesen <raa.lkml@gmail.com>, git@vger.kernel.org
Subject: Re: ident hash usage question
Date: Tue, 20 Oct 2009 13:43:05 -0700 [thread overview]
Message-ID: <7veioxn6ee.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <76c5b8580910201330r45cf625k3a41b5b9e24b3e01@mail.gmail.com> (Eugene Sajine's message of "Tue\, 20 Oct 2009 16\:30\:27 -0400")
Eugene Sajine <euguess@gmail.com> writes:
> One of my friends said that git is not working for their development
> model... C++ development with static linking across the board, where
> they need to see exactly which version of the file has got to the
> executable. Roughly, they are using CVS' keywords and revision numbers
> and a script wich matches them between two versions of the
> executables.
>
> I've got curious if Git can support it and how it can be done with
> minimal changes to workflow.
If the project is already arranged to be compiled with decent automation,
I do not think you need any change to the workflow.
You would have a version.cc file with
static char program_version[] = "My Program " VERSION_STRING;
in it, and teach the build procedure how to compile and link this file.
Something like:
version.o: version.cc
$(CXX) -o $@ -DVERSION_STRING=\""$(git describe HEAD)"\" $?
next prev parent reply other threads:[~2009-10-20 20:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 17:24 ident hash usage question Eugene Sajine
2009-10-20 18:16 ` Alex Riesen
2009-10-20 18:19 ` Alex Riesen
2009-10-20 18:59 ` Eugene Sajine
2009-10-20 19:19 ` Alex Riesen
2009-10-20 20:22 ` Johannes Sixt
2009-10-20 20:35 ` Alex Riesen
2009-10-20 20:30 ` Eugene Sajine
2009-10-20 20:43 ` Junio C Hamano [this message]
2009-10-20 22:14 ` Eugene Sajine
2009-10-20 22:30 ` Junio C Hamano
2009-10-20 23:49 ` Eugene Sajine
2009-10-21 5:35 ` Daniel Barkalow
2009-10-21 3:09 ` Nanako Shiraishi
2009-10-20 20:43 ` Alex Riesen
2009-10-20 22:19 ` Eugene Sajine
2009-10-21 6:25 ` Alex Riesen
2009-10-21 23:32 ` Eugene Sajine
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7veioxn6ee.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=euguess@gmail.com \
--cc=git@vger.kernel.org \
--cc=raa.lkml@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).