git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Sajine <euguess@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Alex Riesen <raa.lkml@gmail.com>,
	git@vger.kernel.org, Eugene Sajine <euguess@gmail.com>
Subject: Re: ident hash usage question
Date: Tue, 20 Oct 2009 19:49:48 -0400	[thread overview]
Message-ID: <76c5b8580910201649i76d14f8bod9a84afa6ea6bbb0@mail.gmail.com> (raw)
In-Reply-To: <7vbpk1lmvl.fsf@alter.siamese.dyndns.org>

> I am not sure what you mean by "static linking" anymore.  Usually the word
> means that everything you tell the linker to link to the executable is
> linked, together with objects from libraries.  The resulting executable is
> usable on its own and it does not change behaviour regardless of which
> version of dynamic libraries you depend on happen to be installed on the
> target system (because by definition a statically linked executable does
> not depend on dynamic libraries---that is the whole point of static
> linking).
>

There seems to be no misunderstanding in the static linking - i meant
the same thing. But let me put an example:

I have a program.exe

This program.exe is built basing on two statically linked libraries
lib1.lib and lib2.lib

I'm not developing any of those libraries, but only my own code of the
program.exe

Now, somebody changed 2 files in lib1.lib and 5 files in lib2.lib. But
i don't know that they are changed because it is different CVS module
or because I'm building against latest released libs or for whatever
reason...

When i rebuild my program the build supposed to pick up changes from
the libraries I'm using and relink, that will include 7 changed obj
files.

How can i say which exactly files are changed in my new version of
executable comparing to the previous version?

Currently they can take a look at the revision number of every
particular file included into the executable, which is put there by
CVS and compare it with the production. If the version is different,
then you know which files are changed and you can get diffs on them...
They also have file path and date and other stuff expanded...

Please note, my personal goal is *to prove that git can do that
better*, with less intrusion into the code sources, not other way
around.So, while keeping the info they want to have they might get
some benefits of git. Although, i understand that there might be no
cure for this state already, you can tell me that and I will close the
topic, but I just keep hoping;)


Thanks a lot,
Eugene

  reply	other threads:[~2009-10-20 23:49 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
2009-10-20 22:14             ` Eugene Sajine
2009-10-20 22:30               ` Junio C Hamano
2009-10-20 23:49                 ` Eugene Sajine [this message]
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=76c5b8580910201649i76d14f8bod9a84afa6ea6bbb0@mail.gmail.com \
    --to=euguess@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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).