[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[creduce-dev] Nit

To: C-Reduce Dev Mailing List <creduce-dev@flux.utah.edu>
Subject: [creduce-dev] Nit
From: Eric Eide <eeide@cs.utah.edu>
Date: Thu, 10 Mar 2016 14:11:18 -0700
List-archive: </listarchives/creduce-dev>
List-help: <mailto:creduce-dev-request@flux.utah.edu?subject=help>
List-id: C-Reduce Development Mailing List <creduce-dev.flux.utah.edu>
List-post: <mailto:creduce-dev@flux.utah.edu>
List-subscribe: <http://www.flux.utah.edu/mailman/listinfo/creduce-dev>, <mailto:creduce-dev-request@flux.utah.edu?subject=subscribe>
List-unsubscribe: <http://www.flux.utah.edu/mailman/options/creduce-dev>, <mailto:creduce-dev-request@flux.utah.edu?subject=unsubscribe>
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (darwin)

Looking at some recent git history, I gather that some recent "general" bug
fixes have happened on the llvm-svn-compatible branch, not the master branch.
E.g., 440b6ae.

Is that right?  Or are these fixes specific to the llvm-svn-compatible branch?

At some level it doesn't really matter, since the branches come back together
when we make a release.  But it might be a good idea to do all the dev/bug
fixing on master, and save llvm-svn-compatible for versionitis stuff.

My $0.02.

-- 
-------------------------------------------------------------------------------
Eric Eide <eeide@cs.utah.edu>  .         University of Utah School of Computing
http://www.cs.utah.edu/~eeide/ . +1 (801) 585-5512 voice, +1 (801) 581-5843 FAX

Follow-Ups:
- Re: [creduce-dev] Nit
  - From: John Regehr <regehr@cs.utah.edu>

Prev by Date: [creduce-dev] towards a release
Next by Date: Re: [creduce-dev] Nit
Previous by thread: Re: [creduce-dev] towards a release
Next by thread: Re: [creduce-dev] Nit
Index(es):
- Date
- Thread