public inbox for
 help / color / mirror / Atom feed
From: Patrick Alken <patrick.alken@Colorado.EDU>
To: "" <>
Subject: Re: GSL git setup
Date: Fri, 03 Jan 2014 16:29:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

> Sounds like a plan.  Thank you Patrick.
> For new stuff, should we then plan to create topic/feature branches
> from master, have the right folks review it if necessary, and then
> merge into master?
> - Rhys
Yes that is what I'm planning to do, anything which is slightly 
nontrivial should get its own branch+merge since branching is so 
effortless in git


      reply	other threads:[~2014-01-03 16:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-02 16:13 Patrick Alken
2014-01-03 16:26 ` Rhys Ulerich
2014-01-03 16:29   ` Patrick Alken [this message]

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:

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

  git send-email \ \ \ \

* 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 read-only IMAP folder(s) and NNTP newsgroup(s).