Skip to main content

Posts

Showing posts from August, 2014

List all branches in GitEye History view

By default, GitEye only shows the other branches the checked out branch has been merged with.  There is a way however, to show all the branches.  In the History view, select the button that looks like a downward pointing Y.  The tool tip on this button is "Show All Branches and Tags" and clicking it will show or hide all the branches and tags this particular branch is unassociated with. The "Show All Branches and Tags" button. Assume a repository has 4 branches, A, B, C, and D, but branch D has only been merged with branches B and C.  This means that the history for D will only show B, C, and D items.  Sometimes though, it may be necessary to compare the checked out branch with branch A even though the two have never been merged.  This control will expose those other items and the diffs can be made.

Email's 'carbon copy' issue

It seems obvious to many, but given the prevalence of the issue, it's not to most.  The problem:  sending a message to a mailing list in the "Cc" field.  Why is it a problem?  The email address of each person on the mailing list is now exposed to each of the other members on the list. For those who don't know, email clients have an additional field other than the "To" field to indicate the recipients of the message with.  This has colloquially been dubbed the carbon copy, or "Cc" field. In a similar way that email programs have the "Cc" field, they also have a "Bcc" field, or blind carbon copy.  The effect of the "Bcc" field is the same as the "Cc" field except for one crucial detail.  The address of each recipient is not exposed to each of the other recipients. Enter addresses one at a time, or use a mailing list just like either the "To" or "Cc" fields.  An individual message

Labels used by this publication

This is a summary of the types of labels used by this publication.  The term label can also be referred to as a tag and the two terms are used interchangeably. The types of labels are defined as the following: Language (technology) Development application ( IDE , database manager client, et cetera) Protocol ( FTP , LDAP , et cetera) Browser Concept (OOP, refactoring, continuous integration) Examples of tags might be:  PHP , ColdFusion , or MySQL , where PHP and ColdFusion are development languages and MySQL is a database manager.  Command line tools like Git would also have a tag. Labels that are not used are ones that refer to specific products or companies such as:  IBM , Gmail , or Flickr . These distinctions are made for two reasons.  The first is to stress the emphasis of the publication on development.  The second is to help limit the volume of tags that would certainly build up and thereby just create noise in the tagging mechanism.