Author Topic: git problems  (Read 4159 times)

guth

  • Senior Community Member
  • Posts: 104
  • Hero Points: 7
git problems
« on: August 26, 2012, 11:29:36 AM »
I use git to version control a few files that I keep on a memory stick so I can take them home and work on them during evenings and weekends. At work we use Perforce. However, I have encountered a number of times that after a while slickedit cannot correctly show the history of a file. A git log filename shows all commits, but history in slickedit only shows up to a certain item and no more. If I branch and work from the branch, slickedit correctly shows history for a while. Why this behavior? Do I use git functionality wrongly? Isn't it possible to mix usage of git from command line and inside slickedit?

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2919
  • Hero Points: 153
Re: git problems
« Reply #1 on: August 29, 2012, 06:41:17 PM »
It looks like we are only listing for the current branch - are you seeing all of the current branch?

guth

  • Senior Community Member
  • Posts: 104
  • Hero Points: 7
Re: git problems
« Reply #2 on: August 30, 2012, 07:10:45 PM »
No, that is the problem, some entries are missing but a git log filename at the prompt in the branch directory shows all entries.

guth

  • Senior Community Member
  • Posts: 104
  • Hero Points: 7
Re: git problems
« Reply #3 on: September 11, 2012, 07:01:11 PM »
It seems like comments having several lines, or maybe only comments having at least one empty line in it, do not show up in History. Today I committed with a log like this

bla bla bla
intentional blank line
bla bla bla

And it didn't show up. Then I tested to make a small change and commit with the following comment:
Dummy correction. Comment on one line

The commit is shown in History.

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2919
  • Hero Points: 153
Re: git problems
« Reply #4 on: September 11, 2012, 07:06:20 PM »
I will look into this, I am currentlhy a bit bogged down in another issue.