From: Marc Branchaud <marcnarc@xiplink.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] pulling signed tag: add howto document
Date: Wed, 18 Jan 2012 16:40:45 -0500 [thread overview]
Message-ID: <4F173C5D.7000802@xiplink.com> (raw)
In-Reply-To: <7v62g8n1tq.fsf@alter.siamese.dyndns.org>
On 12-01-18 04:22 PM, Junio C Hamano wrote:
> Marc Branchaud <marcnarc@xiplink.com> writes:
>>> +
>>> +------------
>>> + $ git checkout work
>>> + $ ... "git pull" from sublieutenants, "git commit" your own work ...
>>> + $ git tag -s -m "Completed frotz feature" frotz-for-xyzzy work
>>> +------------
>>> +
>>> +and pushes the tag out to her publishing repository [*2*]. There is no
>>
>> This footnote speaks of the example using a +, but the example does no such
>> thing.
>>
>>> +need to push the `work` branch or anything else:
>>> +
>>> +------------
>>> + $ git push example.com:/git/froboz.git/ +frotz-for-xyzzy
>>> +------------
>
> Do you not see the plus in front of +'frotz-for-xyzzy' above, or am I
> missing something?
Oops, I was tripped up because the footnote is attached to a sentence that my
addled mind associates with the previous "git tag" example.
It might be better to just move the footnote to the end of the next sentence.
M.
next prev parent reply other threads:[~2012-01-18 21:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 22:53 Using signed tag in pull requests Junio C Hamano
2012-01-17 23:29 ` [PATCH] pulling signed tag: add howto document Junio C Hamano
2012-01-18 15:15 ` Marc Branchaud
2012-01-18 21:22 ` Junio C Hamano
2012-01-18 21:40 ` Marc Branchaud [this message]
2012-01-18 22:27 ` Junio C Hamano
2012-01-18 22:35 ` Marc Branchaud
2012-01-18 1:07 ` Using signed tag in pull requests Andrew Ardill
2012-01-18 1:47 ` Junio C Hamano
2012-01-18 2:34 ` Andrew Ardill
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=4F173C5D.7000802@xiplink.com \
--to=marcnarc@xiplink.com \
--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).