Orsburn (Static Content)

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.

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 ...

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 mechanis...

Noticed first a couple of days ago, the browser based version of Google Drive can now view Open Document Format (ODF) files.  Initial tests have confirmed that both word processing (ODT) and spreadsheet (ODS) files will open in Drive. Drive is Google 's offering in the cloud storage market.  The service includes web based applications for editing office productivity files.  Until just recently, ODF files could only be downloaded in order to be read. At this point, web application productivity suites are light on features compared to their desktop brethren, so this addition is a welcome convenience, to be sure.

News broke today on tech outlets like The Verge and TechCrunch about a new calendar service called Sunrise .  Login options for the web application version include Google and Facebook .  A quick look around after logging in via each of these methods yielded an appealing interface, but nothing really enough to sway users away from whatever they're currently using. What is impressive though is how quickly the spam machine was fired up.  The following message was received only hours after the brief tour from earlier in the day.  Here is the message veiled under the "From" address of "support@sunrise.am." Dear user, Today is an exciting day for Sunrise. We're launching on both Desktop and Android. [image] You can start using Sunrise everywhere for free. On desktop, Sunrise will help you stay organized by combining all the information you need in one place. The desktop app is fast, beautiful and brings everything you love about Sunrise to your desk...

The three main functions of programming, coding, testing, and documenting can be a "mouthful" when spoken together.  This can be clumsy when done so on a regular basis.  In en effort to simplify matters and to "follow suit" with so many other aspects of the development world, the abbreviation CTD may be appropriate. Like so many other abbreviations (also known as acronyms), this term could be used as a verb as well.  "Thanks Bill, I'll get back to CTDing now."  Of course, the assumed redundancy is noted when used in this manner.  Meaning that, if the use of CTD in its expanded form stands for code-ing, test-ing, and document-ing, then CTD-ing is assumed to be compounding the "-ing" ending in each of the individual words as well.  For simplicity's sake, just let it stand as "CTDing."

The ability to respond to calendar event invitations in most applications is broken.  This is true for both web and desktop applications. There are a whole host of calendaring applications on the market with the likes such as Exchange , Google , Yahoo , iCloud , you name it.  In more closed environments like those in many offices that use Outlook as the client for email and calendaring, the problem is less noticeable.  The integration is much tighter.  Take Google Calendar and iCloud for example, the integration is less tight because invitees will get their notifications using Apple Mail , Yahoo Mail , iOS , Android , and who knows what else.  This is because the invitees will be using their email and calendaring application of choice rather than whatever is issued in the office. Attempts have been made by most software vendors to gracefully handle invitations from email, and the calendar vendors try their best to make the invitations simple to respond from...