> Anyway, in your first email you asked how you can merge that branch
> into 'master'. The command 'git merge origin/strings' will "merge" it
> without actually creating a merge commit, because 'strings' builds
> entirely on top of 'master'; this is what Git calls a "fast-forward
>
>>> "SG" == SZEDER Gábor writes:
> On Wed, Oct 09, 2019 at 09:13:56AM +0300, Uwe Brauer wrote:
>> Could you please try out
>> git clone https://git.code.sf.net/p/matlab-emacs/src matlab-emacs-hg
> This repository contains two branches: 'master' and 'strings'. From
> these two 'm
On Wed, Oct 09, 2019 at 09:13:56AM +0300, Uwe Brauer wrote:
> Could you please try out
> git clone https://git.code.sf.net/p/matlab-emacs/src matlab-emacs-hg
This repository contains two branches: 'master' and 'strings'. From
these two 'master' is the default branch, so that is that 'git clone'
On 10/9/2019 2:13 AM, Uwe Brauer wrote:
>
>> On Tue, Sep 24, 2019 at 12:22:27PM +0200, Uwe Brauer wrote:
>
>> I hear you: I had a brief encounter with Mercurial not that long ago,
>> and there were several things that didn't work the way I expected (or
>> rather: the way I got u
> On Tue, Sep 24, 2019 at 12:22:27PM +0200, Uwe Brauer wrote:
> I hear you: I had a brief encounter with Mercurial not that long ago,
> and there were several things that didn't work the way I expected (or
> rather: the way I got used to with Git). The subtle and sometimes
> not
On Tue, Sep 24, 2019 at 12:22:27PM +0200, Uwe Brauer wrote:
> I am confused, I just pulled
> but git log --graph --decorate
> did not show all commits,
>
> Only
>
> git log --graph --decorate --all
>
> and from the emails I received the commits shown by --all
>
> Should be on a new branch.
6 matches
Mail list logo
