git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Expand explanation of the use of + in git push refspecs.

From
Sverre Rabbelier <srabbelier@gmail.com>
Date
Feb 19, 2009, 18:20 UTC
Message-ID
<bd6139dc0902191020i787e56a7tbe88cedfc2cb4028@mail.gmail.com>
In-Reply-To
<20090219180258.2C7983360A6@rincewind>
On Thu, Feb 19, 2009 at 18:39, Marc Branchaud <marcnarc@xiplink.com> wrote:
>  Documentation/git-push.txt |   40 ++++++++++++++++++++++++++++++++--------
>  1 files changed, 32 insertions(+), 8 deletions(-)

Most of this is under examples, so I don't think this is cluttering the man page too much.

> +is recommended only for private, unshared repositories.)  See EXAMPLES

I don't know about this line, I reckon Junio has a + refspec for the pu branch, that is, it's ok to use a + refspec if you let others know that the branch may be 'rebased'.

> +       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"?

-- 
Cheers,

Sverre Rabbelier
Previous: Junio C HamanoNext: Junio C Hamano
Message 4 of 7 in “Expand explanation of the use of + in git push refspecs.”
  1. Expand explanation of the use of + in git push refspecs.Marc Branchaud, Feb 19, 2009
  2. [PATCHv2] Docs: Expand explanation of the use of + in git push refspecs.Marc Branchaud, Feb 19, 2009
  3. Junio C HamanoFeb 24, 2009
  4. Sverre RabbelierFeb 19, 2009
  5. Junio C HamanoFeb 20, 2009
  6. Junio C HamanoFeb 20, 2009
  7. Marc BranchaudFeb 24, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.