edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Chris Brannon <chris@the-brannons.com>
To: edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] new branch for js work
Date: Tue, 24 Dec 2013 07:13:16 -0800	[thread overview]
Message-ID: <878uvab7ub.fsf@mushroom.PK5001Z> (raw)

So that we can keep the master branch clean, I've set up a new branch
specifically for js work, named newjs.
To work with it,
git fetch origin
git branch newjs origin/newjs
git checkout newjs
Code on the branch isn't guaranteed to build.
Eventually, once all the work is done, I'll merge it into master,
squashing most of the commits into one large commit, so as not to
pollute the history with commits that will not build.

-- Chris

                 reply	other threads:[~2013-12-24 15:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878uvab7ub.fsf@mushroom.PK5001Z \
    --to=chris@the-brannons.com \
    --cc=edbrowse-dev@lists.the-brannons.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).