git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Subject: Re: merging initial part of a branch?
Date: Thu, 12 Jan 2006 20:00:06 -0800	[thread overview]
Message-ID: <7v8xtkhj5l.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060113030837.GD27214@fieldses.org> (J. Bruce Fields's message of "Thu, 12 Jan 2006 22:08:37 -0500")

"J. Bruce Fields" <bfields@fieldses.org> writes:

> That's the only reference I can find to the "tag <tag>" notation, and
> it's a bit unhelpful as written.  (What backward compatibility?)
>
> How about the following?--b.

Makes sense.  Thanks.

Backward compatibility is that it was only either "<branch>" or
"tag <tag>".  When heads/branch or tags/tag came later,
supporting the separate word form "tag <tag>" was a bit
cumbersome but was done for b/c.

  reply	other threads:[~2006-01-13  4:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-11 23:04 merging initial part of a branch? J. Bruce Fields
2006-01-11 23:47 ` Junio C Hamano
2006-01-12  0:15   ` Andreas Ericsson
2006-01-12  0:24     ` Junio C Hamano
2006-01-12  0:59       ` Andreas Ericsson
2006-01-12  1:13         ` J. Bruce Fields
2006-01-12  0:55   ` J. Bruce Fields
2006-01-12  1:47     ` Junio C Hamano
2006-01-13  3:08       ` J. Bruce Fields
2006-01-13  4:00         ` Junio C Hamano [this message]
2006-01-13 15:10           ` J. Bruce Fields
2006-01-13 19:50             ` Junio C Hamano
2006-01-13 20:01               ` J. Bruce Fields
     [not found]                 ` <20060115185458.GA3985@fieldses.org>
2006-01-15 23:26                   ` [PATCH] new tutorial Junio C Hamano
2006-01-16  3:57                     ` J. Bruce Fields
2006-01-16  5:32                       ` Junio C Hamano
2006-01-23  4:57                     ` J. Bruce Fields

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=7v8xtkhj5l.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    /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).