zsh-workers
 help / color / mirror / code / Atom feed
From: Mikael Magnusson <mikachu@gmail.com>
To: Wieland Hoffmann <themineo@gmail.com>
Cc: zsh-workers@zsh.org
Subject: Re: [PATCH 3/3] zsh-development-guide: add a missing 'to'
Date: Thu, 7 Feb 2013 22:34:59 +0100	[thread overview]
Message-ID: <CAHYJk3QDV5AW0gGGkArNf=wW1HjSvrnoWSA-eXCOx_oJLQKnmg@mail.gmail.com> (raw)
In-Reply-To: <1360086270-13944-3-git-send-email-themineo@gmail.com>

This isn't true afaik... Did whoever wrote it mean git merge --squash?

On 05/02/2013, Wieland Hoffmann <themineo@gmail.com> wrote:
> ---
>  Etc/zsh-development-guide | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Etc/zsh-development-guide b/Etc/zsh-development-guide
> index e7d7385..e4ac1ba 100644
> --- a/Etc/zsh-development-guide
> +++ b/Etc/zsh-development-guide
> @@ -67,7 +67,7 @@ Git Workflow
>   * Do not merge your private feature branches onto the master branch: a
>     linear history without merge commits is simpler to follow (and to
>     bisect). Both "git cherry-pick" and "git merge --ff-only" can be used
> -   bring changes over to another branch without a merge commit.
> +   to bring changes over to another branch without a merge commit.
>
>   * It is often useful to regularly check in changes while prototyping a
>     solution on a private branch. When finished, it is better to deliver a
> --
> 1.8.1.2
>
>


-- 
Mikael Magnusson


  reply	other threads:[~2013-02-07 21:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-05 17:44 Wieland Hoffmann
2013-02-07 21:34 ` Mikael Magnusson [this message]
2013-02-07 22:47   ` Lawrence Velázquez
2013-02-08  2:25   ` Phil Pennock
2013-02-08  3:30     ` Lawrence Velázquez

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='CAHYJk3QDV5AW0gGGkArNf=wW1HjSvrnoWSA-eXCOx_oJLQKnmg@mail.gmail.com' \
    --to=mikachu@gmail.com \
    --cc=themineo@gmail.com \
    --cc=zsh-workers@zsh.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://git.vuxu.org/mirror/zsh/

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).