From: Michael J Gruber <git@drmicha.warpmail.net>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: Jakub Narebski <jnareb@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2011, #04; Wed, 16)
Date: Mon, 21 Feb 2011 10:33:52 +0100 [thread overview]
Message-ID: <4D623180.4030407@drmicha.warpmail.net> (raw)
In-Reply-To: <AANLkTinC0zB0bTRtaERBMNHnuU2kQVxz0oF+Rw3KFDvY@mail.gmail.com>
Sverre Rabbelier venit, vidit, dixit 20.02.2011 12:54:
> Heya,
>
> On Thu, Feb 17, 2011 at 13:20, Michael J Gruber
> <git@drmicha.warpmail.net> wrote:
>> How would you even know they are different, since you neither read the
>> commit messages nor looked up the thread? Thomas Rast's work makes the
>> latter even simpler these days.
>
> What work is that? I think I'm missing something useful here :P
>
Well, first of all, some people's mail or news clients are so feature
bloated that you can even search/grep/filter for post titles such as the
ones listed readily in Junio's "What's cooking" posts.
For commits in git.git (with pu!), Thomas provides a notes based mapping
from commits to message ids. With
[remote "trast"]
url = git://repo.or.cz/git/trast.git
fetch = +refs/heads/notes/*:refs/notes/remotes/trast/*
git log --show-notes=remotes/trast/full
will give something like below. Neat, eh? (Even neater when not broken
by a MUA).
Kudos, Thomas!
Michael
commit 3b0d24053b50d8da76de28ea5f0d3947fa3d2194
Author: Michael J Gruber <git@drmicha.warpmail.net>
Date: Thu Feb 17 08:48:06 2011 +0100
Make <identifier> lowercase in Documentation
Leaving uppercase abbreviations (e.g. URL) and an identifier named after
an upercase env variable (CVSROOT) in place, this adjusts the few
remaining cases and fixes an unidentified identifier along the way.
Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Notes (remotes/trast/full):
From: Michael J Gruber <git@drmicha.warpmail.net>
Subject: [PATCH] Make <identifier> lowercase in Documentation
Message-Id:
<d8246b3c2afe48505db13da63e01c0084346ade9.1297928789.git.git@drmicha.warpmail.net>
Date: Thu Feb 17 08:48:06 2011
In-Reply-To: <7vbp2birzi.fsf@alter.siamese.dyndns.org>
Archived-At:
<http://permalink.gmane.org/gmane.comp.version-control.git/167053>
prev parent reply other threads:[~2011-02-21 9:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 23:23 What's cooking in git.git (Feb 2011, #04; Wed, 16) Junio C Hamano
2011-02-17 12:06 ` Jakub Narebski
2011-02-17 12:20 ` Michael J Gruber
2011-02-20 11:54 ` Sverre Rabbelier
2011-02-21 9:33 ` Michael J Gruber [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D623180.4030407@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=srabbelier@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).