All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: "Mestnik, Michael J - Eagan,
	MN - Contractor"  <Michael.J.Mestnik@usps.gov>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Using Format/export-subst Howto.
Date: Fri, 14 Sep 2012 15:03:49 +0200	[thread overview]
Message-ID: <50532B35.9050607@drmicha.warpmail.net> (raw)
In-Reply-To: <84EA18831601B6429E578236AE239B01A54807F242@EAGNMNSXMB07.usa.dce.usps.gov>

Mestnik, Michael J - Eagan, MN - Contractor venit, vidit, dixit
14.09.2012 14:20:
> I must have missed something reading through the documentation for this.  git version 1.7.11.3
> 
> $ git check-attr -a -- autorepair.d/AR02_new_rttest.sh
> autorepair.d/AR02_new_rttest.sh: ident: set
> autorepair.d/AR02_new_rttest.sh: export-subst: set
> 
>   echo "0..$_expected_tests"
>   diag 'Script Version: $Id: 1ca40f8395ea361cc07d2ec1a2961c3df749dc3c $'
>   diag 'By: $Format:%cn$ $Format:%ce$'
>   diag 'At: $Format:%cD$'
> 

'$Format:' is processed when creating an archive. It's mentioned with
export-subst only under the heading "create archive". So, that is as
described, I think.

> I also believe that the documentation could try and better explain under what conditions "$Id" will be processed, it doesn't seam to happen on commit and even after a checkout this is not updated.  It does seam to update during a pull and that's basically all I need.

"git replaces $Id$... upon checkout.  Any byte sequence that begins with
$Id: and ends with $ in the worktree file is replaced with $Id$ upon
check-in."

Now, the there are two problems after you add $Id$ and check-in (commit):

- commit does not check out, i.e. your work-tree copy is not updated
with expanded $Id$
- Not even "git checkout thatFile" updates your work-tree copy.

The first one could be considered OK, but at least the second one seems
to be a bug. Together they create the following problem: Say, you've
corrected that problem (rm that file and checkout) and then update your
file, add and commit. It will keeping having the old (now wrong) Id
expansion.

We should do something about this.

Michael

  reply	other threads:[~2012-09-14 13:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-14 12:20 Using Format/export-subst Howto Mestnik, Michael J - Eagan, MN - Contractor
2012-09-14 13:03 ` Michael J Gruber [this message]
2012-09-14 15:06   ` Johannes Sixt
2012-09-14 15:27     ` Mestnik, Michael J - Eagan, MN - Contractor
2012-09-14 15:39       ` Johannes Sixt
2012-09-14 16:05         ` Mestnik, Michael J - Eagan, MN - Contractor
2012-09-14 21:09         ` Michael J Gruber
2012-09-14 21:23           ` Junio C Hamano
2012-09-14 22:26             ` Junio C Hamano
2012-09-17 13:17               ` Michael J Gruber
2012-09-17 13:26                 ` Mestnik, Michael J - Eagan, MN - Contractor
2012-09-17 20:21                 ` Junio C Hamano
2012-09-18  8:24                   ` Michael J Gruber
2012-09-17 12:12             ` Mestnik, Michael J - Eagan, MN - Contractor
2012-09-17 13:45               ` Michael J Gruber
2012-09-17 14:08                 ` Mestnik, Michael J - Eagan, MN - Contractor
2012-09-17 14:21                   ` Michael J Gruber
2012-09-17 15:52                     ` Mestnik, Michael J - Eagan, MN - Contractor

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=50532B35.9050607@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=Michael.J.Mestnik@usps.gov \
    --cc=git@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.