On Wednesday, August 29, 2012 2:21:54 PM UTC+2, Michael Haggerty wrote:
>
> On 08/28/2012 04:51 PM, Fred wrote:
> > git rev-list ist great, but it doesn't work for cherry picked commits
> >
> > do a cherry-pick commit from branchB into master. git rev-list
> > master..branchB would show sha1
On 08/28/2012 04:51 PM, Fred wrote:
> git rev-list ist great, but it doesn't work for cherry picked commits
>
> do a cherry-pick commit from branchB into master. git rev-list
> master..branchB would show sha1 of the commit in branchB.
> But the change itself is already in master (cherry-picked and
On Wednesday, August 29, 2012 4:11:23 AM UTC+2, Michael Wang wrote:
>
> I have tried git diff master... which also have this issue, the
> cherry-picked change is showing in the output.
You are right. that's because the way it works. it finds last commit in
master where branchB was forked and
I have tried git diff master... which also have this issue, the
cherry-picked change is showing in the output.
2012/8/28 Fred
>
>
> On Tuesday, August 28, 2012 3:26:15 PM UTC+2, Michael Wang wrote:
>>
>> try git rev-list, following is an exmaple:
>>
>> loveky@LOVEKY-PC ~/test/test (dev)
>> $ g
On Tuesday, August 28, 2012 5:13:39 PM UTC+2, donnoman wrote:
>
> git diff master..
>
> Would give you what's in your current branch since master
>
> git diff ..master
>
> Would show you commits in master that your local branch doesn't have
>
> git diff ...master
>
> Or
>
> git diff master.
git diff master..
Would give you what's in your current branch since master
git diff ..master
Would show you commits in master that your local branch doesn't have
git diff ...master
Or
git diff master...
Would show you all commits that your branch and master do not share
I only find the 3 d
On Tuesday, August 28, 2012 3:26:15 PM UTC+2, Michael Wang wrote:
>
> try git rev-list, following is an exmaple:
>
> loveky@LOVEKY-PC ~/test/test (dev)
> $ git log --oneline master
> 1874792 4
> 8ed7a1e 3
> a224756 2
> 34b4b11 1
>
> loveky@LOVEKY-PC ~/test/test (dev)
> $ git log --oneline dev
> f
Hi..
On Tue, Aug 28, 2012 at 6:02 PM, Fred wrote:
>
>
> On Tuesday, August 28, 2012 1:15:08 PM UTC+2, Tim Chase wrote:
>>
>> On 08/28/12 05:47, Tim Chase wrote:
>> > On 08/28/12 03:13, Fred wrote:
>> >> is there a way to check if a branch doesn't introduce changes,
>> >> which are not in master.
try git rev-list, following is an exmaple:
loveky@LOVEKY-PC ~/test/test (dev)
$ git log --oneline master
1874792 4
8ed7a1e 3
a224756 2
34b4b11 1
loveky@LOVEKY-PC ~/test/test (dev)
$ git log --oneline dev
fd0c922 5
a224756 2
34b4b11 1
loveky@LOVEKY-PC ~/test/test (dev)
$ git rev-list master..dev
