GIT course

It was just the quick start guides I was referring too.

To be fair I've never found a truly good book on either VHDL or Verilog but my I do recommend:

VHDL-2008 Just the New Stuff, Peter J Ashenden

His earlier book "The designer's Guide to VHDL" is quite good too.

I learnt a lot of my VHDL stuff from good old internet news groups a long time ago when seriously good people, including from Xinlinx posted there.

And I started with a paid for week long course which was pretty good but far from cheap.

I've never found a book I'd recommend on Verilog, which may be related to my dislike for it, but I don't know which is cause and which effect.

I've only had a very quick look at the "Introduction to Logic Circuits...." pair but they seem to duplicate a lot of the material from the other two books

I followed your link to: Digital System Design with FPGA: Implementation Using Verilog and VHDL, but they seem to want money and it's out of stock.

MK

balearicdynamics  wrote:

 

Jon,

Branch strategy is an entirely separate topic.  Branching depends on the development environment and the branch strategy.

I am sorry but this is totally wrong. Not just IMHO, it is wrong as you read the basis of the Git features and behavior. What is TOTALLY another topic is Agile as well as the tons of other team development methodology. All of them – it is the current trend – tend to abandon SVN and other source control methods moving to Git.

 

Yeah, of course I am wrong on this forum.  It's not like I have to deal with this on a daily basis in my day job.  But. hey, thanks again for reaffirming for why I limit my posts here and seriously why I don't like coming to this site anymore. 

Cheers.

You expressed an opinion if I am not wrong. Me too. Both are valid, maybe criticizable.

That's all.

I first started using GIT because some article or other would refer to the code being available in a GIT repository.

I just remember it being strange and confusing when I was trying to use it. A lot of articles on element14 refer to GIT so I thought members might benefit from some tips on what it is and how to use it ….

I'm wrong all the time. Ask my spouse. Why so sensitive?

By your own admission you have minimal experience in Git. I suspect I have less than you. Chances are you might be wrong. The responder interpreted the documentation to suggest your perspective is not correct. It wasn't as though the comments were derogatory or disrespectful. I would expect with a level 8 ranking on the site you have seen worse.

If you are suggesting there are comment vultures sitting waiting for the chance to feed on a wrong response, I say there are few. Those that exist, I suggest are pretty thin because they are not feeding that well. My experience doesn't give me indication they are in abundance on the site.

Looking at your background profile and experience I think you might have some insight that would be of benefit to the community. It is unfortunate we don't have rules of conduct that are more to your liking but that is not surprising. With of 200K members someone is bound to get pissed at something. Confirmation bias will enable you to find details to support your wish to not participate.

I have been asked to change comments on posts. After asking for clarification from the moderator, I have refused. I accept the moderator has the right to remove what someone interprets as inappropriate. That doesn't mean I have to agree.

What type of use are you interested in?

Using other people's repo / getting their latest versions?

Contributing to other peoples repo?

Have a repo to have your code versioned and shared with other people?

Have a repo where other people can contribute to your code?

Mostly my uses are:

Using other people's repo / getting their latest versions

Have a repo to have my code versioned and shared with others - such as supporting element14 blogs

The original suggestion of a guide was not primarily for me, but for any members not familiar wit GIT.

It might be useful to present an introduction and basic user guide to GIT repository …..

A good introduction I would suggest:

1. What the Problem I have I would need an SCM
2. Why git? ( here comes the:  why it is a distributed and easy and work this way... )
3. How then, do I use git
   1. Here come the basic commands in an interactive way. Here was where I started.
   2. Now that one knows how to deal with doing things within git, it is time to see how workflows happen: There are many, one needs to be reasonable and pick the one that most suits the application or workflows of the existing job.

I like to see use cases for Git. I have employed it and still left with the question of why.

As this post responses have demonstrated, there are a variety of applications of Git as there are individuals that have posted.

I would like to see knowledge on Git depending on the use case. Single user, small team and large team. Does all the options apply across the different groups? What about the type of project you are working on.

It will be suggested just use what you need. I like to know what I need or what I can gain by taking advantage of options available. I suspect a large development team on a complex projects enables them to experience all the benefits of the application.

I'm still searching for reasons my small python projects warrant a Git repository?

I've just written a post on using git with suggested branch strategies.

Firmware Version Control with GitHub part 1: Branch Strategy for New Features

You may or ( - hey internet - ) may not like the solutions. And I hope I can learn from critique.