Fails handling fetch results other than new branch/tag/commit about git-dude HOT 6 CLOSED

Output flags returned by git fetch (based on git version 1.7.8):

• - indicates a deleted ref (tag) fetch.c#L281
• * indicates a new ref (tag, branch) fetch.c#L306
• (space) indicates a fast-forward fetch.c#L322
• + indicates a successful forced update fetch.c#L336
• = indicates a ref that was up to date fetch.c#L257
• ! indicates a ref that was rejected fetch.c#L271

Also note that in fast-forwards, the output contains ".." (2 dots) but in a forced update the output contains "..." (3 dots).

https://gist.github.com/1480257

from git-dude.

Thanks for deep investigation.
However for me it looks like this:

$ echo " + 83e93db...b212eee branch-name -> origin/branch-name  (forced update)" | grep -F -- '->' | sed -E 's/^\s+\+\s+//'
83e93db...b212eee branch-name -> origin/branch-name  (forced update)

No "+" at the start of string. I wonder why sed is not stripping out "+" for you...

from git-dude.

AFAIK, not all sed's are equal; linux uses GNU sed, the BSDs use their own, etc. In looking at the manpage for sed on OS X, it looks like the POSIX.2 is being used for regex, so I'm guessing the regex used to strip the + would be different on OS X -- just a shot in the dark...

Either way, I figured it was safe to open this as an issue with what I had uncovered so far, considering more than a + could cause this issue.

from git-dude.

Considering awk is already in use, maybe the sed regex can be swapped for awk to avoid cross-platform issues?

from git-dude.

I appreciate that and I'll keep that issue open for some time, maybe more facts will come up.

As for sed and output flags you listed I've made small fix: #23
Can you try this fix on your machine?

from git-dude.

Pull #23 fixed the issue so I'm closing this one.

from git-dude.