David Goodenough writes:
> Surely the point with Git is that it is multi-master. So you can have
> the master on code.gnucash.org and a clone on github. That way you have
> control over your master, and everyone else can find code where they expect
> it. You also have control over when it get
On Friday 09 Nov 2012, Derek Atkins wrote:
> Ngewi Fet writes:
> > On Tue, Nov 6, 2012 at 4:09 PM, Derek Atkins wrote:
> > John Ralls writes:
> > > Why can't we set up commit hooks on each that immediately push to
> > > the other? Yes, there's a small chance of a conflict if two peop
Ngewi Fet writes:
> On Tue, Nov 6, 2012 at 4:09 PM, Derek Atkins wrote:
>
> John Ralls writes:
>
> > Why can't we set up commit hooks on each that immediately push to the
> > other? Yes, there's a small chance of a conflict if two people push
> > changes of the same file to
On Tue, Nov 6, 2012 at 4:09 PM, Derek Atkins wrote:
> John Ralls writes:
>
> > Why can't we set up commit hooks on each that immediately push to the
> > other? Yes, there's a small chance of a conflict if two people push
> > changes of the same file to each repository at the same moment, but
> >
On 06-11-12 16:10, Derek Atkins wrote:
Geert Janssens writes:
John,
From what I see you and Christian have the most experience with
working in git. So I'm tempted to follow your advice. The above is
mostly my opinion, but clearly limited due to a lack of experience.
So for now, the proposal
Geert Janssens writes:
> John,
>
> From what I see you and Christian have the most experience with
> working in git. So I'm tempted to follow your advice. The above is
> mostly my opinion, but clearly limited due to a lack of experience.
>
> So for now, the proposal stands as:
> - github -> maste
John Ralls writes:
> Why can't we set up commit hooks on each that immediately push to the
> other? Yes, there's a small chance of a conflict if two people push
> changes of the same file to each repository at the same moment, but
> the team is so small that that likelihood is infinitesimal.
My
Geert Janssens writes:
> I'd rather see it the other way. If developers commit to
> code.gnucash.org, while all others fork from github you get a similar
> indirection like we have now with svn. I don't like that. It's a
> source for all kinds of small errors and sync irregularities. I have
> had
On 03-11-12 15:57, John Ralls wrote:
On Nov 3, 2012, at 5:14 AM, Geert Janssens wrote:
On 01-11-12 16:10, Derek Atkins wrote:
Geert Janssens writes:
[snip]
Let's continue to build on this. I propose this setup:
One master repo hosted on github. One canonical repo on
code.gnucash.org pulls
On Nov 3, 2012, at 5:14 AM, Geert Janssens wrote:
> On 01-11-12 16:10, Derek Atkins wrote:
>> Geert Janssens writes:
>>
>> [snip]
>>> Let's continue to build on this. I propose this setup:
>>>
>>> One master repo hosted on github. One canonical repo on
>>> code.gnucash.org pulls periodically
On 01-11-12 16:10, Derek Atkins wrote:
Geert Janssens writes:
[snip]
Let's continue to build on this. I propose this setup:
One master repo hosted on github. One canonical repo on
code.gnucash.org pulls periodically from this master repo to keep in
sync.
Only selected developers have commit
Geert Janssens writes:
[snip]
> Let's continue to build on this. I propose this setup:
>
> One master repo hosted on github. One canonical repo on
> code.gnucash.org pulls periodically from this master repo to keep in
> sync.
>
> Only selected developers have commit access to the github
> reposit
Christian Stimming writes:
> I guess all of the recent committers should be added, such as the full list
> from the file git-helper-scripts/gnc_authors. However, some of them don't
> seem
> to have a github account, do they? E.g., Derek?
derekatkins
-derek
--
Derek Atkins, SB '93 MI
On 01-11-12 10:29, Christian Stimming wrote:
Am Mittwoch, 31. Oktober 2012, 15:33:02 schrieb Geert Janssens:
This discussion has been had multiple times before and frankly I hope
this will be the last time.
Yes.
- Nobody opposed to using github. In fact most developers are in favour
of using
On Wed, 31 Oct 2012 19:26:05 -0700
John Ralls wrote:
>
> On Oct 31, 2012, at 7:33 AM, Geert Janssens
> wrote:
>
> > This discussion has been had multiple times before and frankly I
> > hope this will be the last time.
> >
> > The previous discussion didn't end in an explicit consensus, but I
Am Mittwoch, 31. Oktober 2012, 15:33:02 schrieb Geert Janssens:
> This discussion has been had multiple times before and frankly I hope
> this will be the last time.
Yes.
> - Nobody opposed to using github. In fact most developers are in favour
> of using it.
> - John indicated that github is goo
On Oct 31, 2012, at 7:33 AM, Geert Janssens wrote:
> This discussion has been had multiple times before and frankly I hope this
> will be the last time.
>
> The previous discussion didn't end in an explicit consensus, but I think we
> were close to finding a compromise at least. A summary:
>
This discussion has been had multiple times before and frankly I hope
this will be the last time.
The previous discussion didn't end in an explicit consensus, but I think
we were close to finding a compromise at least. A summary:
- Nobody opposed to using github. In fact most developers are i
18 matches
Mail list logo
