From: Junio C Hamano <gitster@pobox.com>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: Marc Branchaud <marcnarc@xiplink.com>, git@vger.kernel.org
Subject: Re: [PATCH] Expand explanation of the use of + in git push refspecs.
Date: Thu, 19 Feb 2009 21:10:47 -0800 [thread overview]
Message-ID: <7veixtk814.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <bd6139dc0902191020i787e56a7tbe88cedfc2cb4028@mail.gmail.com> (Sverre Rabbelier's message of "Thu, 19 Feb 2009 19:20:15 +0100")
Sverre Rabbelier <srabbelier@gmail.com> writes:
>> + branch. *This can abandon commits in the origin repository.*
>
> I liked your wording with the commits becoming dangling better.
>
>> +That is, commits A and B would belong to an unreachable branch without a
>> +symbolic name.
>
> Perhaps it would be better to say those commits "would no longer
> belong to a branch with a symbolic name, and thus become unreachable"?
I agree with you on both counts.
next prev parent reply other threads:[~2009-02-20 5:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-19 17:39 [PATCH] Expand explanation of the use of + in git push refspecs Marc Branchaud
2009-02-19 17:39 ` [PATCHv2] Docs: " Marc Branchaud
2009-02-24 17:39 ` Junio C Hamano
2009-02-19 18:20 ` [PATCH] " Sverre Rabbelier
2009-02-20 5:10 ` Junio C Hamano [this message]
2009-02-20 5:04 ` Junio C Hamano
2009-02-24 16:54 ` Marc Branchaud
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=7veixtk814.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=marcnarc@xiplink.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.
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).