Git development
 help / color / mirror / Atom feed
From: Michal Nazarewicz <mina86@tlen.pl>
To: git@vger.kernel.org
Subject: Re: Something like $Id$, $Revision$ or $Date$?
Date: Mon, 10 Nov 2008 16:48:48 +0100	[thread overview]
Message-ID: <871vxjoa3j.fsf@erwin.mina86.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0811101319570.30769@pacific.mpi-cbg.de> (Johannes Schindelin's message of "Mon, 10 Nov 2008 13:25:14 +0100 (CET)")

[-- Attachment #1: Type: text/plain, Size: 1489 bytes --]

> On Mon, 10 Nov 2008, Michal Nazarewicz wrote:
>> I would like the "$Id$" sequences to be updated automatically after a 
>> commit (ie. without the need to check out).  (Besides I would prefer 
>> $Date$ more but I can live with $Id$ I guess ;) ).

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> No, you don't.
>
> At least most likely you do not want that behavior.  Typically, you have 
> the $Id$ stuff in released versions to indicate what revision that version 
> came from even if the files are no longer in a Git repository.
>
> And you can have that without ever committing anything in-between, by 
> using the export-subst attributes with git-archive.  Have a look at 
> Documentation/gitattributes.txt (I agree it is underdocumented in 
> git-archive.txt).

The thing is that for some repositories I don't distinguish anything
like a "release version" of files.  For instance, I have a repository
with my configuration files, and I want to be able to do

  scp emacs system-where-git-is-not-installed:.emacs

or attaching the file in an email without worrying about anything.
Instead, what you're describing would force me to do some voodoo magic
priory to sending the file.

-- 
Best regards,                                         _     _
 .o. | Liege of Serenly Enlightened Majesty of      o' \,=./ `o
 ..o | Computer Science,  Michal "mina86" Nazarewicz   (o o)
 ooo +--<mina86*tlen.pl>--<jid:mina86*jabber.org>--ooO--(_)--Ooo--

[-- Attachment #2: Type: application/pgp-signature, Size: 196 bytes --]

  parent reply	other threads:[~2008-11-10 15:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-10  0:22 Something like $Id$, $Revision$ or $Date$? Michal Nazarewicz
2008-11-10  0:43 ` Sverre Rabbelier
2008-11-10  1:16   ` Michal Nazarewicz
2008-11-10  3:43     ` dhruva
2008-11-10  9:49       ` Michal Nazarewicz
2008-11-10  7:26     ` Johannes Sixt
2008-11-10 12:25     ` Johannes Schindelin
2008-11-10 14:05       ` dhruva
2008-11-10 15:48       ` Michal Nazarewicz [this message]
2008-11-10 15:58         ` Francis Galiegue
2008-11-10 15:59 ` Jakub Narebski
2008-11-10 17:38   ` Michal Nazarewicz
2008-11-10 18:03     ` Jakub Narebski
2008-11-10 20:00       ` Michal Nazarewicz
2008-11-10 20:17         ` Jakub Narebski
2008-11-10 20:24           ` Francis Galiegue
2008-11-10 20:32             ` Jakub Narebski
2008-11-10 20:58               ` Brian Gernhardt

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=871vxjoa3j.fsf@erwin.mina86.com \
    --to=mina86@tlen.pl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox