As you may know, the core developers have been experimenting with
Git for some time, using a mirror repository [1] at Github. This trial
has been quite successful, and the developers are now preparing to make
it an official mirror of the Subversion repository.
Unfortunately in the course of pre
Developers,
those of you who are also admins of the sourceforge gnucash project page will
have received this as well: We'll be featured on sourceforge's front page
starting the coming week.
Do we want to update some of the information there? Like, adding some more
recent screenshots? Might be
On Jan 25, 2013, at 9:43 AM, Geert Janssens wrote:
> On 25-01-13 18:12, Derek Atkins wrote:
>>
>> I'm fine with this. I *may* have some time this weekend, but not a
>> lot. I promised I'd use this weekend to clean up my office so I wont
>> really be online much.
> I won't have time this weeke
On 25-01-13 18:12, Derek Atkins wrote:
I'm fine with this. I *may* have some time this weekend, but not a
lot. I promised I'd use this weekend to clean up my office so I wont
really be online much.
I won't have time this weekend.
Also, I'll need some help with:
1) setting up the repos to po
Geert Janssens writes:
> On 25-01-13 17:35, Derek Atkins wrote:
>> Just for the record, the things left to do are:
>>
>> 1) get gitolite to push to github -- this will require a github reset
>> 2) convert www to use git and get gitolite to signal an update instead
>> of svn
>> 3) send emails
On 25-01-13 17:57, John Ralls wrote:
On Jan 25, 2013, at 8:35 AM, Derek Atkins wrote:
Geert Janssens writes:
That's correct.
Strictly speaking you could _try_ to push but the attempt
would fail due to insufficient permissions. That's because the
gitolite repos are configured read-only, an
On 25-01-13 17:35, Derek Atkins wrote:
Just for the record, the things left to do are:
1) get gitolite to push to github -- this will require a github reset
2) convert www to use git and get gitolite to signal an update instead
of svn
3) send emails from gitolite instead of svn
I think we'
On Jan 25, 2013, at 8:35 AM, Derek Atkins wrote:
> Geert Janssens writes:
>
>> That's correct.
>>
>> Strictly speaking you could _try_ to push but the attempt
>> would fail due to insufficient permissions. That's because the
>> gitolite repos are configured read-only, and will remain so as l
Geert Janssens writes:
> That's correct.
>
> Strictly speaking you could _try_ to push but the attempt
> would fail due to insufficient permissions. That's because the
> gitolite repos are configured read-only, and will remain so as long as
> the svn->gitolite bridge is in use.
Yep, right now
On 25-01-13 02:50, Yawar Amin wrote:
On 2013-01-23 10:21, Derek Atkins wrote:
[...]
Once that happens we'll get svn -> gitolite -> github automatically on
every commit (modulo the up-to-60s delay in the svn -> gitolite
transfer). Then, down the road, once we turn off svn we'll still have
the g
10 matches
Mail list logo
