git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Memory overrun in http-push.c
Date: Fri, 02 Mar 2007 15:38:01 +0100	[thread overview]
Message-ID: <es9cnt$egh$1@sea.gmane.org> (raw)
In-Reply-To: 20070301120042.GD63606@codelabs.ru

Eygene Ryabinkin wrote:

> By the way, I am missing one thing: the Id keyword in the file. The
> problem is that when some user is telling me: there is a bug in the
> function a() that is inside the file b.c, then I can ask him to
> give me the $Id$ tag of the file and I will have the full information
> about the file version. Can I have it with git if user has just the
> sources without any signs of the file versions? I've glanced over
> the git manual, but was unable to find anything usable.
 
First, keyword expansion on checkout (CVS-like) is an abomination;
the proper way is to do it on _build_ time, like git and Linux kernel
do, so "git version" (or "git --version") and "uname -a" gives us
the version which can be used with git to go to it.

Second, there were some work on git mailing list to create git command
which given a blob (or sha1 of a blob object) would list all commits
(in date order) which have this exact version of a file (of a blob).

Third, tar files generated by git-acrhive have version embedded as
a comment in them.
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

  parent reply	other threads:[~2007-03-02 14:43 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-28 15:15 Memory overrun in http-push.c Eygene Ryabinkin
2007-02-28 15:41 ` Andy Parkins
2007-02-28 15:42   ` Johannes Schindelin
2007-03-01  5:13   ` Eygene Ryabinkin
2007-03-01  8:15     ` Alex Riesen
2007-03-01  9:11       ` Eygene Ryabinkin
2007-03-01  9:21         ` Alex Riesen
2007-03-01 11:26           ` Eygene Ryabinkin
2007-03-01  9:32       ` Junio C Hamano
2007-03-01 10:04         ` Alex Riesen
2007-03-01 10:40         ` Andy Parkins
2007-03-01 12:00     ` Eygene Ryabinkin
2007-03-01 12:08       ` Junio C Hamano
2007-03-01 13:20         ` Eygene Ryabinkin
2007-03-01 17:11       ` Johannes Schindelin
2007-03-01 18:31         ` Andy Parkins
2007-03-01 18:41           ` Johannes Schindelin
2007-03-01 19:31             ` Andy Parkins
2007-03-01 20:43               ` Johannes Schindelin
2007-03-02 10:05                 ` Andy Parkins
2007-03-02 14:46                   ` Jakub Narebski
2007-03-02 15:22                     ` Andy Parkins
2007-03-02 19:16                   ` Johannes Schindelin
2007-03-02 19:42                     ` Andy Parkins
2007-03-04  8:17                   ` Daniel Barkalow
2007-03-04  8:31                     ` Junio C Hamano
2007-03-04  9:18                       ` Daniel Barkalow
2007-03-01 21:43         ` Alex Riesen
2007-03-01 21:54           ` Shawn O. Pearce
2007-03-01 17:52       ` Uwe Kleine-König
2007-03-02 14:38       ` Jakub Narebski [this message]
2007-03-02 15:17         ` Johannes Schindelin
2007-03-02 22:52           ` identifying blobs (was Re: Memory overrun in http-push.c) Junio C Hamano
2007-03-02 23:10             ` Linus Torvalds
2007-03-02 15:23         ` Memory overrun in http-push.c Andy Parkins
2007-03-02 15:30           ` Matthieu Moy
2007-03-02 15:48             ` Andy Parkins
2007-02-28 16:36 ` Florian Weimer
2007-03-01  5:19   ` Eygene Ryabinkin

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='es9cnt$egh$1@sea.gmane.org' \
    --to=jnareb@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).