From mboxrd@z Thu Jan 1 00:00:00 1970 From: Holger Brunck Date: Mon, 19 Dec 2011 11:37:08 +0100 Subject: [U-Boot] [PATCH] km/common: add toolchain variable In-Reply-To: <20111219085720.C3DF8135A9A2@gemini.denx.de> References: <1323879110-8404-1-git-send-email-holger.brunck@keymile.com> <20111217204908.102C21ECC61@gemini.denx.de> <4EEEF0D3.5040302@keymile.com> <20111219085720.C3DF8135A9A2@gemini.denx.de> Message-ID: <4EEF13D4.5020304@keymile.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Wolfgang, On 12/19/2011 09:57 AM, Wolfgang Denk wrote: > In message <4EEEF0D3.5040302@keymile.com> you wrote: >> >>>> +Last change: 24.11.2011 >>> >>> Does this really make any sense? Which date are you recording here/ >>> When you (think) you last edited the file? When you applied the patch >>> to your local tree? When you submitted it for mainline? When it >>> actually got applied? >> >> What I want to record is to track the version of the scripts and this makes >> sense for me. In the end the scripts are copied into /tftpboot on each >> developers machine and is therefore not under git control. It is an easy >> indication wether the scripts are uptodate or not, without starting a diff tool >> and compare them with the latest git tree. Inside the git tree the information >> is useless, I agree. > > You can insert such information when you export the files from git, > say by adding a line like: > > Last commit date: $Format:%H %cD$ > > That would IMO make much more sense. > > See what we do with "snapshot.commit" in U-Boot [see also the entry > in .git/info/attributes]. > After reading the doc I don't know how it could be used in my usecase. Please correct me if I am wrong, but this does only work in combination with the "git archive" command. And I don't want to do an archive, I want to export/copy some files out of the git tree into /tftpboot. Best regards Holger