git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Philip Oakley" <philipoakley@iee.org>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: "GitList" <git@vger.kernel.org>
Subject: Re: [PATCH v1 2/3] doc: rebase: fixup! can take an object name
Date: Mon, 15 Aug 2016 00:30:31 +0100	[thread overview]
Message-ID: <DDCA022C9C704F1DA20FC024B84FEB5E@PhilipOakley> (raw)
In-Reply-To: xmqq1t1rj6n9.fsf@gitster.mtv.corp.google.com

From: "Junio C Hamano" <gitster@pobox.com>
> "Philip Oakley" <philipoakley@iee.org> writes:
> 
>> the 'standalone' is that it must be a single (standalone) word on the
>> subject line immediately after the "fixup! "(s).
>>
>> communicationg that one cannot have any extra textual notes after that
>> word was the issue that 'standalone' tried to address.
> 
> Perhaps I am slow but did you mean the same thing as "it must be a
> single word and nothing else on the remainder of the line"?

Yes.

--
Philip

  reply	other threads:[~2016-08-14 23:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-14 21:46 [PATCH v1 0/3] fixup fixup documenation Philip Oakley
2016-08-14 21:46 ` [PATCH v1 1/3] doc: commit: --fixup/--squash can take a commit revision Philip Oakley
2016-08-14 22:09   ` Junio C Hamano
2016-08-14 22:45     ` Philip Oakley
2016-08-14 22:55       ` Junio C Hamano
2016-08-14 23:29         ` Philip Oakley
2016-08-16 22:11           ` Philip Oakley
2016-08-14 21:46 ` [PATCH v1 2/3] doc: rebase: fixup! can take an object name Philip Oakley
2016-08-14 22:11   ` Junio C Hamano
2016-08-14 23:00     ` Philip Oakley
2016-08-14 23:02       ` Junio C Hamano
2016-08-14 23:30         ` Philip Oakley [this message]
2016-08-14 21:46 ` [PATCH v1 3/3] doc: rebase: clarify fixup! fixup! constraint Philip Oakley
2016-08-14 22:20   ` Junio C Hamano
2016-08-14 23:23     ` Philip Oakley
2016-08-15 15:42       ` Junio C Hamano

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=DDCA022C9C704F1DA20FC024B84FEB5E@PhilipOakley \
    --to=philipoakley@iee.org \
    --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).