On 9 January 2013 20:23, Diego Elio Pettenò flamee...@flameeyes.eu wrote:
On 09/01/2013 13:20, Duncan wrote:
Are the git migration blockers at such a point that we can get an ETA
yet?
PLEASE ALL STOP DETOURING EVERY DAMN TOPIC OUT THERE WITH THE GIT
MIGRATION, THANK YOU VERY MUCH.
And yes
On 9 January 2013 23:16, Duncan 1i5t5.dun...@cox.net wrote:
Diego Elio Pettenò posted on Wed, 09 Jan 2013 13:23:13 +0100 as excerpted:
On 09/01/2013 13:20, Duncan wrote:
Are the git migration blockers at such a point that we can get an ETA
yet?
PLEASE ALL STOP DETOURING EVERY DAMN TOPIC OUT
On 01/08/2013 11:49 PM, Duncan wrote:
Zac Medico posted on Tue, 08 Jan 2013 23:36:59 -0800 as excerpted:
Thought: Do the CVS keyword expansion in repoman, and then feed the
expanded file to CVS for commit. This gives you a fixed file, which
you can then generate your manifest against.
On 09-01-2013 00:31:04 -0800, Zac Medico wrote:
Of course that assumes that the keywords are suitably distinct such that
they won't ordinarily be found in the pre-expanded lines. Whether that's
actually the case or not I've no idea...
Well, I'd suggest to simply drop the keywords.
On 09/01/2013 10:09, Fabian Groffen wrote:
Yeah, but I'd really appreciate it if they could stay for as long as
we're on CVS, so my scripts that use the version number to retrieve
diffs and apply them to the Prefix' tree versions keep on working.
Since we're discussing adding this on Portage
On 09-01-2013 10:14:21 +0100, Diego Elio Pettenò wrote:
On 09/01/2013 10:09, Fabian Groffen wrote:
Yeah, but I'd really appreciate it if they could stay for as long as
we're on CVS, so my scripts that use the version number to retrieve
diffs and apply them to the Prefix' tree versions keep
On 09/01/2013 13:20, Duncan wrote:
Are the git migration blockers at such a point that we can get an ETA
yet?
PLEASE ALL STOP DETOURING EVERY DAMN TOPIC OUT THERE WITH THE GIT
MIGRATION, THANK YOU VERY MUCH.
And yes I know it's not polite to scream. At this point I DON'T CARE.
--
Diego
On Wed, Jan 9, 2013 at 7:20 AM, Duncan 1i5t5.dun...@cox.net wrote:
Zac Medico posted on Tue, 08 Jan 2013 23:42:39 -0800 as excerpted:
Weren't we planning to drop the CVS keywords for the git migration,
anyway?
Are the git migration blockers at such a point that we can get an ETA
yet?
On Wed, 09 Jan 2013 13:23:13 +0100
Diego Elio Pettenò flamee...@flameeyes.eu wrote:
PLEASE ALL STOP DETOURING EVERY DAMN TOPIC OUT THERE WITH THE GIT
MIGRATION, THANK YOU VERY MUCH.
Translation: We all know that there are lots of things that would be a
hell of a lot easier if we weren't the
On 09/01/2013 13:37, Ciaran McCreesh wrote:
Translation: We all know that there are lots of things that would be a
hell of a lot easier if we weren't the only project in the world still
using CVS, but the Git migration is never going to happen, so
mentioning it just makes everyone angry.
No,
On Wed, Jan 9, 2013 at 7:42 AM, Diego Elio Pettenò
flamee...@flameeyes.eu wrote:
On 09/01/2013 13:37, Ciaran McCreesh wrote:
Translation: We all know that there are lots of things that would be a
hell of a lot easier if we weren't the only project in the world still
using CVS, but the Git
On 01/09/2013 01:09 AM, Fabian Groffen wrote:
On 09-01-2013 00:31:04 -0800, Zac Medico wrote:
Of course that assumes that the keywords are suitably distinct such that
they won't ordinarily be found in the pre-expanded lines. Whether that's
actually the case or not I've no idea...
Well,
On 09-01-2013 05:06:15 -0800, Zac Medico wrote:
If we had a live cvs - git sync, then I'd suggest that you migrate your
scripts to use that instead. However, it looks like this one is not
synced regularly (last sync was about 2 months ago):
On Wed, 09 Jan 2013 05:06:15 -0800
Zac Medico zmed...@gentoo.org wrote:
On 01/09/2013 01:09 AM, Fabian Groffen wrote:
On 09-01-2013 00:31:04 -0800, Zac Medico wrote:
Of course that assumes that the keywords are suitably distinct such that
they won't ordinarily be found in the pre-expanded
On 01/09/2013 12:31 AM, Zac Medico wrote:
I guess we could use the cvs -ko option [1] on all files. That's
apparently what prevents $Header expansion for $PORTDIR/skel.ebuild.
Actually, we should use -kb rather than -ko, since -kb disables
transformations entirely [1]. The -ko mode is identical
15 matches
Mail list logo
