Dne 4.6.2010 9:36, Dag Wieers napsal(a):
On Fri, 4 Jun 2010, Yury V. Zaytsev wrote:
Yes, I want git too !
It shouldn't be hard to move to git, but we have to first make sure that
everyone knows how to use git (I haven't used it myself either) and
convert the current data to git so we
Hi!
On Fri, 2010-06-04 at 09:36 +0200, Dag Wieers wrote:
Yes, I want git too !
Well, just to have it is not that much of an issue :-)
There's a sucky but reasonably well-maintained git package at EPEL and a
package that I guess follows Fedora more closely contributed by Tom G.
Christensen.
On Fri, 2010-06-04 at 10:03 +0200, David Hrbáč wrote:
Guys, well, let me repeat myself. I guess RPMForge is near clinical death.
Oh really?! That's totally news to me!!!
As to me shout out let's move to git solves nothing. We need to bring
up solution which solves the points above.
Let's
On Fri, Jun 04, 2010 at 10:03:39AM +0200, David Hrbáč wrote:
10. commit access is fine, but without build trigger etc., totally
useless...
I wouldn't say it's useless.. what's to stop you contributing a new/updated
package to the repo, then pinging someone with build access to review/build
the
Dne 4.6.2010 10:59, Chris Butler napsal(a):
On Fri, Jun 04, 2010 at 10:03:39AM +0200, David Hrbáč wrote:
10. commit access is fine, but without build trigger etc., totally
useless...
I wouldn't say it's useless.. what's to stop you contributing a new/updated
package to the repo, then
On Fri, 2010-06-04 at 11:07 +0200, David Hrbáč wrote:
I'm fine with process commit- review - build, but at rpmforge we have
process: commit-wait for Dag 1-30 days-build. It's something I have
discussed and community with Dag and I guess Dag is unhappy about that.
The way out of this is
On Fri, 4 Jun 2010, David Hrbáč wrote:
Dne 4.6.2010 9:36, Dag Wieers napsal(a):
On Fri, 4 Jun 2010, Yury V. Zaytsev wrote:
Yes, I want git too !
It shouldn't be hard to move to git, but we have to first make sure that
everyone knows how to use git (I haven't used it myself either) and
On Fri, 4 Jun 2010, David Hrbáč wrote:
Dne 4.6.2010 10:59, Chris Butler napsal(a):
On Fri, Jun 04, 2010 at 10:03:39AM +0200, David Hrbáč wrote:
10. commit access is fine, but without build trigger etc., totally
useless...
I wouldn't say it's useless.. what's to stop you contributing a
On Fri, 4 Jun 2010, Yury V. Zaytsev wrote:
On Fri, 2010-06-04 at 11:07 +0200, David Hrbáč wrote:
I'm fine with process commit- review - build, but at rpmforge we have
process: commit-wait for Dag 1-30 days-build. It's something I have
discussed and community with Dag and I guess Dag is
On 04/06/2010 08:31, Yury V. Zaytsev wrote:
Hi guys!
I just want to share something that came to my mind. I am definitively
tired of waiting for 5-10 minutes for my local svn checkout to update.
By contrast, I've been using git for version control on some other
projects and it's proved to be
Dne 4.6.2010 11:16, Yury V. Zaytsev napsal(a):
On Fri, 2010-06-04 at 11:07 +0200, David Hrbáč wrote:
What else do you want? Can you contribute something to what has already
been discussed or it's just reiterating on the issues without getting
any closer to solving them?
Ok, so because we
On Fri, 2010-06-04 at 11:37 +0200, Dag Wieers wrote:
Yury, I don't fully agree that things have been discussed to a state that
it is waiting for an implementation. On the other hand nothing is being
lead in a way that we do get forward. Let alone that we have the hardware
we need for doing
On 04/06/2010 09:05, Yury V. Zaytsev wrote:
If you set up a small KVM host with a minimal install of EL5 or Ubuntu
Lucid or whatnot for me I can play around it and follow up on the
mailing list with the results. One day :-)
If you send me a key and ip list that you will connect from, I can get
On Fri, 2010-06-04 at 11:23 +0200, Dag Wieers wrote:
Since Matthias, who owns the rpmforge.net domain doesn't want us to use it
and since I don't believe rpmrepo is going anywhere I needed a new domain
name, which I registered as repoforge.org (close enough to RPMforge, and
we can keep the
Dne 4.6.2010 11:23, Dag Wieers napsal(a):
On Fri, 4 Jun 2010, David Hrbáč wrote:
Since Matthias, who owns the rpmforge.net domain doesn't want us to use
it and since I don't believe rpmrepo is going anywhere I needed a new
domain name, which I registered as repoforge.org (close enough to
Dne 4.6.2010 12:19, Karanbir Singh napsal(a):
Why not just use redmine instead and get the mulitple vcs backend
included right away ?
iirc, there are people on the list here who have used redmine in the
past ( and also offered to help get it going! )
I don't want to start the flame, I vote
On Fri, 2010-06-04 at 13:23 +0200, David Hrbáč wrote:
Dne 4.6.2010 13:15, Karanbir Singh napsal(a):
In the first post I suggested MY help in *evaluating* (this means trying
it out and seeing whether it has any compelling advantages / major
disadvantages) the migration to git, ok?
So,
On Fri, 2010-06-04 at 14:01 +0100, Karanbir Singh wrote:
I think a separation in the two process's would be good. eg: have a
version control process that outputs srpms
And another process - the buildsystem - that takes the srpms and does
its build. There are a lot of clear wins around not
18 matches
Mail list logo
