From: Johannes Sixt <j.sixt@viscovery.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2010, #05; Sun, 21)
Date: Mon, 22 Feb 2010 08:35:58 +0100 [thread overview]
Message-ID: <4B8233DE.7050106@viscovery.net> (raw)
In-Reply-To: <7vtytacebd.fsf@alter.siamese.dyndns.org>
Since you do not publish your topic branches, I'd appreciate if you could
include the SHA1 of the topic heads in the headlines, for example:
* jn/maint-fix-pager 2d3ca21 (2010-02-20) 7 commits
This way I could copy-paste the branch name and SHA1 to a 'git branch -f'
command to track the topic manually.
-- Hannes
next prev parent reply other threads:[~2010-02-22 7:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-22 0:19 What's cooking in git.git (Feb 2010, #05; Sun, 21) Junio C Hamano
2010-02-22 3:08 ` Larry D'Anna
2010-02-22 7:35 ` Johannes Sixt [this message]
2010-02-22 7:49 ` Junio C Hamano
2010-02-22 8:17 ` Björn Gustavsson
2010-02-22 8:37 ` Johannes Schindelin
2010-02-22 9:48 ` Thomas Rast
2010-02-22 10:01 ` Thomas Rast
2010-02-22 10:08 ` Johannes Schindelin
2010-02-22 10:37 ` Jeff King
2010-02-22 10:52 ` Jeff King
2010-02-22 20:21 ` Junio C Hamano
2010-02-23 0:53 ` Jeff King
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=4B8233DE.7050106@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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).