From: Lars Noschinski <lars-2008-1@usenet.noschinski.de>
To: "H.Merijn Brand" <h.m.brand@xs4all.nl>
Cc: git@vger.kernel.org
Subject: Re: Feature suggestion: git-hist
Date: Wed, 30 Jul 2008 15:33:34 +0200 [thread overview]
Message-ID: <20080730133334.GB31192@lars.home.noschinski.de> (raw)
In-Reply-To: <20080730133859.368bbd92@pc09.procura.nl>
* H.Merijn Brand <h.m.brand@xs4all.nl> [08-07-30 13:38]:
> I can ask them what version they have, and I can then check if
> the complaint was already addressed in an update that was
> already released. In SCCS this was easy: they tell me the output
> of the what command, I check if the bug was fixed in a newer
> version and the answer is present. No such luck in git, as the
> stamps are (non-sequitive) SHA id's. As we moved to git, we now
> have to update those id's by hand, as the customers are used to
> it. (At least we can now use readable date formats)
Hm, what about "git-describe --contains $SHA_OF_BUGFIX"?
next prev parent reply other threads:[~2008-07-30 13:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 11:38 Feature suggestion: git-hist H.Merijn Brand
2008-07-30 12:03 ` Pieter de Bie
2008-07-30 12:14 ` H.Merijn Brand
2008-07-30 13:33 ` Lars Noschinski [this message]
2008-07-30 13:58 ` H.Merijn Brand
2008-07-30 14:55 ` Miklos Vajna
2008-07-30 15:03 ` H.Merijn Brand
2008-07-30 15:23 ` Santi Béjar
2008-07-30 15:58 ` Avery Pennarun
2008-07-30 16:34 ` Lars Noschinski
2008-07-30 15:18 ` Santi Béjar
2008-07-30 15:29 ` H.Merijn Brand
[not found] ` <FA2D570A-B2B1-4994-AA6A-9C0C55E69900@silverinsanity.com>
2008-07-30 16:26 ` Merging submodules (was Re: Feature suggestion: git-hist) H.Merijn Brand
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=20080730133334.GB31192@lars.home.noschinski.de \
--to=lars-2008-1@usenet.noschinski.de \
--cc=git@vger.kernel.org \
--cc=h.m.brand@xs4all.nl \
/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).