[Top][All Lists]

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

Re: [Liberty-eiffel] ET plan

From: Raphael Mack
Subject: Re: [Liberty-eiffel] ET plan
Date: Sun, 10 Nov 2013 21:05:02 +0100


sorry for not responding so long.

I share the opinion that it is not very useful to maintain ET in several
branches. And from your options it may be best to have a separate repo
for ET, but on the other side I'm not sure whether we really have to
create an adler branch before the release and have branch support in ET.
Is this really worth the effort? Wouldn't it be simpler to have et
always in master and running on masters Liberty code? For a release it
seems reasonable to me to just let the master branch become stable and
branch just for the release or even just use a tag. - When we are
stable, we can let ET run and after it "passes" just do a tagged commit
for a release candidate and/or the release. If we need to add a fix in
an existing release we can still branch from the tagged commit, do we?


On Mi, 2013-11-06 at 20:01 +0100, Cyril ADRIAN wrote:
> Hi all,
> Maintaining ET in both branches is a PITA. I need to git cherry-pick
> each time I change a thing.
> There are two solutions:
> * either a specific branch: not very user-friendly git-wise (because
> git pull will do unexpected merges), but contained in the same repo;
> * either a specific repository: a bit more complex to setup, but maybe
> simpler in the long term?
> What do you think? Do you have better ideas?
> Anyway any of that is post-adler.
> Cyril ADRIAN
> To any NSA and FBI agents reading my email: please consider whether
> defending the US Constitution against all enemies, foreign or
> domestic, requires you to follow Snowden's example.
> Facebook Twitter LinkedIn Google Plus
> Contact me: Google Talk address@hidden
> Free signature tool. CLICK HERE TO GET IT.
> ‚Äč 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]