[git-users] Re: git log "double dot" showing a false positive?

better the commit candidates are for > examination. > > Or/and, you could try bringing this question up on the main *Git mailing > list* [1], might be it`s something obvious for people much > more involved with Git internals :) > > [1] g...@vger.kernel.org > > Regards, >

[git-users] Re: git log "double dot" showing a false positive?

fe8f3727fe56dc..branchB > > Hopefully, these two can show a bit simpler graphs of how > 9ba8f06829b2d2170f23254ed3fe8f3727fe56dc eventually gets in both "branchA" > and "branchB". > > On Tuesday, August 8, 2017 at 10:12:21 PM UTC+2, Chris Murphy wrote: >>

[git-users] Re: git log "double dot" showing a false positive?

sday, August 8, 2017 at 3:54:16 PM UTC-4, Igor Djordjevic wrote: > > On Tuesday, August 8, 2017 at 2:38:09 PM UTC+2, Chris Murphy wrote: >> >> You're right, I didn't mean to leave the --tags=1 in. I double checked >> that the --tags and greps didn't remove any lines from the outpu

[git-users] Re: git log "double dot" showing a false positive?

On Tuesday, August 8, 2017 at 8:38:09 AM UTC-4, Chris Murphy wrote: > > You're right, I didn't mean to leave the --tags=1 in. I double checked > that the --tags and greps didn't remove any lines from the output. > > However, I did overlook the carat syntax - on zsh, those need to b

[git-users] Re: git log "double dot" showing a false positive?

t 4:02:43 AM UTC+2, Chris Murphy wrote: >> >> Oh man, sorry, I totally screwed up when editing the output to exclude >> tags, making the graph totally wrong since some lines were missing. Sorry >> about that. >> >> I've fixed that issue (Sorry, I still have to

[git-users] Re: git log "double dot" showing a false positive?

Djordjevic wrote: > > Hi Chris, > > On Monday, August 7, 2017 at 9:48:26 PM UTC+2, Chris Murphy wrote: >> >> The gist I uploaded was created via >> git log --format=%h\ %d --graph branchA branchB >> > > Is this the _exact_ command you used, or you had some additiona

[git-users] Re: git log "double dot" showing a false positive?

especially in combination with the second gist I posted a minute ago: git log branchA...branchB --graph | grep "commit \|Date: \|Merge: " https://gist.github.com/cmurphycode/c1e581c04a89b7f5a679ad6e1ae1d7d6 Thanks, Chris On Monday, August 7, 2017 at 3:48:26 PM UTC-4, Chris Murphy wrote: &g

[git-users] Re: git log "double dot" showing a false positive?

TC-4, Igor Djordjevic wrote: > > Hi Chris, > > On Monday, August 7, 2017 at 5:28:15 PM UTC+2, Chris Murphy wrote: >> >> The history of the repo is quite tangled with many merges, but I uploaded >> it here (with sensitive info removed, sorry, it's a repo for

Re: [git-users] git log "double dot" showing a false positive?

Unfortunately not -- that's also why I included the --contains result. ± % git log --pretty="%H" branchA | grep 9ba8f06829b2d2170f23254ed3fe8f3727fe56dc 9ba8f06829b2d2170f23254ed3fe8f3727fe56dc ± % git log --pretty="%H" branchB | grep 9ba8f06829b2d2170f23254ed3fe8f3727fe56dc

Re: [git-users] git log "double dot" showing a false positive?

: > > On Mon, Aug 07, 2017 at 08:28:15AM -0700, Chris Murphy wrote: > > [...] > > ą % git --version > > git version 2.13.0 > > > > % git log branchA..branchB | grep > 9ba8f06829b2d2170f23254ed3fe8f3727fe56dc > > commit 9ba8f06829b2d2170f23254ed

[git-users] git log "double dot" showing a false positive?

Hi, My understanding is that the command git log branchA..branchB should return the commits reachable via branchB that are not reachable via branchA I use this command a lot and have never noticed an issue, until