On Čt, 2014-03-06 at 17:06 +0100, Milan Crha wrote:
> On Thu, 2014-03-06 at 10:55 -0500, Matthew Barnes wrote:
> > I think the wip/webkit-composer branch might still be alive (ask Tomas).
>
> Right, that's the only being active currently from my point of view too
> (and according to commit log).
On Thu, 2014-03-06 at 11:40 -0500, Paul Smith wrote:
> If you have a new-ish git you can use the --delete flag instead of the
> colon (exactly the same result, but more readable):
>
> git push --delete origin
Thanks for the tip, that's much easier to remember.
Matt
__
On Thu, 2014-03-06 at 17:06 +0100, Milan Crha wrote:
> Right, that's the only being active currently from my point of view too
> (and according to commit log). Should I figure out the right git command
> and just get rid of those in eds/evo/ews/ema?
Yeah, have at it.
I think the commands you need
On Thu, 2014-03-06 at 10:55 -0500, Matthew Barnes wrote:
> I think the wip/webkit-composer branch might still be alive (ask Tomas).
Right, that's the only being active currently from my point of view too
(and according to commit log). Should I figure out the right git command
and just get rid of t
On Thu, 2014-03-06 at 16:09 +0100, Milan Crha wrote:
> when talking about branches, what about deleting all those obsolete for
> years? I mean the development branches, not those release related.
> I believe they are useless, definitely those not touched for years (even
> for months, like mine wher
Hi,
when talking about branches, what about deleting all those obsolete for
years? I mean the development branches, not those release related.
I believe they are useless, definitely those not touched for years (even
for months, like mine where I initiated the EClient stuff couple years
ago)
On Thu, 2014-03-06 at 09:27 -0500, Matthew Barnes wrote:
> I suggest just naming the branches after the module name, similar to how
> GLib and GTK+ do it. e.g.
>
>evolution-3-12
>evolution-data-server-3-12
>evolution-ews-3-12
>evolution-mapi-3-12
>
> That sound okay? I don't hav
On Mon, 2014-03-03 at 15:51 -0500, Matthew Barnes wrote:
> Been thinking about our release schedule after 3.12.0, when we break
> with GNOME and embark on our own annual development/support cycle.
>
> I'd like to release updates at a more predictable cadence than GNOME.
> With the GNOME 3.12.0 and
On Thu, 2014-03-06 at 09:58 +0100, Fabiano Fidêncio wrote:
> I can bet that (almost) every contributor has a different way to setup
> the environment, compile and use the fresh compiled Evolution and I'm
> here to describe the way I do my setup (based on Matthew's setup) :-)
Nice instructions! I
Howdy!
I can bet that (almost) every contributor has a different way to setup the
environment, compile and use the fresh compiled Evolution and I'm here to
describe the way I do my setup (based on Matthew's setup) :-)
Firstly, jhbuild or not jhbuild?
--
I l
10 matches
Mail list logo
