Hello Junio,
On Sat, Oct 24, 2015 at 12:41 AM, Junio C Hamano wrote:
> Francis Moreau writes:
>
>> I was mislead by the git-cherry manpage somehow which says:
>>
>> "git-cherry therefore
>> detects when commits have been "copied" by means of git-cherry-pick(1),
>>
>> which is not exactl
Francis Moreau writes:
> I was mislead by the git-cherry manpage somehow which says:
>
> "git-cherry therefore
> detects when commits have been "copied" by means of git-cherry-pick(1),
>
> which is not exactly true.
Yeah, I agree; the sentence is merely giving a description from
laypers
On Fri, Oct 23, 2015 at 12:57 PM, Kevin Daudt wrote:
> On Tue, Oct 20, 2015 at 06:32:12PM +0200, Francis Moreau wrote:
>> Hi,
>>
>> I'm seeing something odd with git-cherry: it doesn't seem to detect
>> that a commit has been cherry-picked from master branch.
>>
>> This happens with the systemd gi
On Tue, Oct 20, 2015 at 06:32:12PM +0200, Francis Moreau wrote:
> Hi,
>
> I'm seeing something odd with git-cherry: it doesn't seem to detect
> that a commit has been cherry-picked from master branch.
>
> This happens with the systemd git repository (from github) so it
> should be fairly simple t
Hi,
On Tue, Oct 20, 2015 at 6:32 PM, Francis Moreau wrote:
> Hi,
>
> I'm seeing something odd with git-cherry: it doesn't seem to detect
> that a commit has been cherry-picked from master branch.
>
> This happens with the systemd git repository (from github) so it
> should be fairly simple to rep
Hi,
I'm seeing something odd with git-cherry: it doesn't seem to detect
that a commit has been cherry-picked from master branch.
This happens with the systemd git repository (from github) so it
should be fairly simple to reproduce.
What I did:
$ git --version
git version 2.6.0
$ git checkout -b
6 matches
Mail list logo
