On Sat, 4 Jul 2015 20:20:23 +0200 Peter Stuge wrote:
It's important that the review flow is well-understood and efficient.
This is impossible in our case due to the lack of manpower.
We already have a lot of bugs, patches, stabilization requests
hanging over there for months and even years.
On 5 July 2015 at 17:03, C Bergström cbergst...@pathscale.com wrote:
Again I don't see it as lying - (you're still working on stuff until
you push.. development isn't done) The ability to do micro or
incremental commits instead of the svn's forced wait approach is the
benefit here.
# Manuel Rüger mr...@gentoo.org (5 Jul 2015)
# Mask for various issues (missing ruby20 support, test failures)
# Removal in 30 days
app-text/deplate
app-text/migemo
dev-utils/travis-yaml
signature.asc
Description: OpenPGP digital signature
C Bergström wrote:
3) Ever tried to make a patch of the *actual* merge commit? Can one of
the advocates of merge show me the git command to do that? (Sure you
can diff between 2 commits, but the merge commit likes to avoid
being seen)
If there are no conflicts when merging then the
On 07/05/2015 06:10 AM, C Bergström wrote:
5) More about linear commits and history - I need to double check,
but I don't think rebase changes the actual commit date (I could be
mistaken).
You are mistaken, and should have double checked before you argued.
Arguing without checking makes you
Hi there!
I'm having trouble updating Qt:4 (dev-qt/qt*-4.8*:4) from 4.8.6 to 4.8.7.
Looking at the ebuilds, they require some 4.8.7 versions to be installed
already that in turn cannot be installed because other ebuilds require
4.8.6 while not yet upgraded.
I am running the latest version of
On Sun, Jul 05, 2015 at 12:03:29PM +0700, C Bergström wrote:
On Sun, Jul 5, 2015 at 11:31 AM, Duncan 1i5t5.dun...@cox.net wrote:
C Bergström posted on Sun, 05 Jul 2015 01:17:41 +0700 as excerpted:
I super don't like merge workflows.
1) merge commits are confusing at best and normal tools
Sunday 05 Jul 2015 16:03:27, hasufell wrote :
On 07/05/2015 06:10 AM, C Bergström wrote:
5) More about linear commits and history - I need to double check,
but I don't think rebase changes the actual commit date (I could be
mistaken).
You are mistaken, and should have double checked
On Sun, Jul 05, 2015 at 04:03:27PM +0200, hasufell wrote:
On 07/05/2015 06:10 AM, C Bergström wrote:
5) More about linear commits and history - I need to double check,
but I don't think rebase changes the actual commit date (I could be
mistaken).
You are mistaken, and should have double
On Sun, Jul 5, 2015 at 2:25 PM, Sebastian Pipping sp...@gentoo.org wrote:
I really wonder if there is any update path from having
dev-qt/qtcore-4.8.6-r2
dev-qt/qtgui-4.8.6-r4
installed before to
dev-qt/qtcore-4.8.7
dev-qt/qtgui-4.8.7
Usually this kind of conflict happens
All,
I've been hearing lately that the newest versions of git allow you to
sign pushes.
Once we have a version of git stable that allows this, can someone fill
me in on why we would need to sign commits if we sign pushes? If we have
a signature on the push, we know where that came from, so it
On Sun, Jul 05, 2015 at 07:17:26PM +0400, Jason Zaman wrote:
On Sun, Jul 05, 2015 at 12:03:29PM +0700, C Bergström wrote:
On Sun, Jul 5, 2015 at 11:31 AM, Duncan 1i5t5.dun...@cox.net wrote:
C Bergström posted on Sun, 05 Jul 2015 01:17:41 +0700 as excerpted:
I super don't like merge
On 05.07.2015 20:44, Alexandre Rostovtsev wrote:
What I usually end up doing is listing my installed dev-qt/qt* ebuilds, and
updating all of them together explicitly:
emerge -1 qtcore:4 qtgui:4 qtsql:4 etc.
That's what I tried but it doesn't seem to work with this update.
Looking at the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 05 Jul 2015 21:35:23 +0200
hasufell hasuf...@gentoo.org wrote:
https://wiki.gentoo.org/wiki/Gentoo_git_workflow#naming_convention
Ah ha! I must have missed that the last time that I read that wiki
article. Thanks for the link hasufell.
On 07/05/2015 08:57 PM, William Hubbs wrote:
On Sun, Jul 05, 2015 at 04:03:27PM +0200, hasufell wrote:
On 07/05/2015 06:10 AM, C Bergström wrote:
5) More about linear commits and history - I need to double check,
but I don't think rebase changes the actual commit date (I could be
mistaken).
On Sun, 2015-07-05 at 20:25 +0200, Sebastian Pipping wrote:
Hi there!
I'm having trouble updating Qt:4 (dev-qt/qt*-4.8*:4) from 4.8.6 to 4.8.7.
Looking at the ebuilds, they require some 4.8.7 versions to be installed
already that in turn cannot be installed because other ebuilds require
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Sun, 5 Jul 2015 15:00:26 -0400
NP-Hardass np-hard...@gentoo.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On July 5, 2015 2:57:14 PM EDT, William Hubbs willi...@gentoo.org
wrote:
If you are working on a topic branch to make
On Mon, Jul 6, 2015 at 2:15 AM, William Hubbs willi...@gentoo.org wrote:
On Sun, Jul 05, 2015 at 07:17:26PM +0400, Jason Zaman wrote:
On Sun, Jul 05, 2015 at 12:03:29PM +0700, C Bergström wrote:
On Sun, Jul 5, 2015 at 11:31 AM, Duncan 1i5t5.dun...@cox.net wrote:
C Bergström posted on Sun,
On 07/05/2015 09:00 PM, NP-Hardass wrote:
On July 5, 2015 2:57:14 PM EDT, William Hubbs willi...@gentoo.org
wrote:
If you are working on a topic branch to make your changes, which has
not
been published, just rebase that branch on master, then merge it to
master, and no one knows any
On 07/05/2015 04:01 PM, William Hubbs wrote:
All,
I've been hearing lately that the newest versions of git allow you to
sign pushes.
Once we have a version of git stable that allows this, can someone fill
me in on why we would need to sign commits if we sign pushes? If we have
a
On Sun, Jul 05, 2015 at 09:05:59AM +0300, Andrew Savchenko wrote:
On Sat, 4 Jul 2015 20:20:23 +0200 Peter Stuge wrote:
It's important that the review flow is well-understood and efficient.
This is impossible in our case due to the lack of manpower.
We already have a lot of bugs, patches,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On July 5, 2015 2:57:14 PM EDT, William Hubbs willi...@gentoo.org
wrote:
If you are working on a topic branch to make your changes, which has
not
been published, just rebase that branch on master, then merge it to
master, and no one knows any
On Sun, 2015-07-05 at 21:25 +0200, Sebastian Pipping wrote:
On 05.07.2015 20:44, Alexandre Rostovtsev wrote:
What I usually end up doing is listing my installed dev-qt/qt* ebuilds, and
updating all of them together explicitly:
emerge -1 qtcore:4 qtgui:4 qtsql:4 etc.
That's what I
On Sunday 05 July 2015 13:46:10 William Hubbs wrote:
On Sun, Jul 05, 2015 at 09:05:59AM +0300, Andrew Savchenko wrote:
On Sat, 4 Jul 2015 20:20:23 +0200 Peter Stuge wrote:
It's important that the review flow is well-understood and efficient.
This is impossible in our case due to the
The attached list notes all of the packages that were added or removed
from the tree, for the week ending 2015-07-05 23:59 UTC.
Removals:
dev-java/excalibur-logger 2015-06-29 12:44:14 monsieurp
kde-misc/kcmsystemd 2015-06-29 20:47:30 johu
games-misc/gpe-julia
On Sun, Jul 5, 2015 at 3:22 PM, Brian Dolbec dol...@gentoo.org wrote:
I would think that there would be a very small number of branches to the
main master tree. Those would be for the large projects like kde,
gnome,... They would still do their development work in their
overlays, then move
On 6 July 2015 at 08:01, William Hubbs willi...@gentoo.org wrote:
Once we have a version of git stable that allows this, can someone fill
me in on why we would need to sign commits if we sign pushes? If we have
a signature on the push, we know where that came from, so it seems to be
overkill
On 6 July 2015 at 07:15, William Hubbs willi...@gentoo.org wrote:
If you use the hash of a merge commit with git show, you get nothing, so
the merge commit is useless in terms of following changes.
git show SHA1 -m
--
Kent
KENTNL - https://metacpan.org/author/KENTNL
On Sun, Jul 5, 2015 at 4:01 PM, William Hubbs willi...@gentoo.org wrote:
I've been hearing lately that the newest versions of git allow you to
sign pushes.
Once we have a version of git stable that allows this, can someone fill
me in on why we would need to sign commits if we sign pushes? If
On 6 July 2015 at 03:25, Sebastian Pipping sp...@gentoo.org wrote:
On 05.07.2015 20:44, Alexandre Rostovtsev wrote:
What I usually end up doing is listing my installed dev-qt/qt* ebuilds, and
updating all of them together explicitly:
emerge -1 qtcore:4 qtgui:4 qtsql:4 etc.
That's what I
30 matches
Mail list logo
