Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: [PATCH 3/3] zsh-development-guide: add a missing 'to'
- X-seq: zsh-workers 31033
- From: Mikael Magnusson <mikachu@xxxxxxxxx>
- To: Wieland Hoffmann <themineo@xxxxxxxxx>
- Subject: Re: [PATCH 3/3] zsh-development-guide: add a missing 'to'
- Date: Thu, 7 Feb 2013 22:34:59 +0100
- Cc: zsh-workers@xxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=LpIJeccwMEul+jrtmp7xdY9NwgK8kU1lDlNg2hFcW3M=; b=PYPqt12xA4KUxYf/sGp7ZAm52GGgOQ7Iyhd85hoeNTHyDoW+IP+ZPLw0PRv93R1dro KQ0YAvwaBziSN2D2iPIJyzBak957xTA+xrOn58ss3T/MNSO8ESjeUjQaUiTe15dZp2TX 46HbjIxY7uBO2sPJjSehuOOLlPTloNOGmKLQ3UflZPywU4/Ypm70p7p5KpBX48HlRtjD BT8MNYlTYpyQy0c7uYoDtrvle/cOs9SkiasUQtIGNHHUZnN08yl7r7rwVe2xfBygDN2p kk3I4WJ12JDOvguqdTpEius+cRrZCtcMMvaIKWmwhz0us4t4k0RUzs+vml2Hk9qmVl1g XmTw==
- In-reply-to: <1360086270-13944-3-git-send-email-themineo@gmail.com>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <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@xxxxxxxxx> 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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author