Le dim 30/10/2005 à 20:15, Josh Sled a écrit :
> On Sun, 2005-10-30 at 20:01 +0100, Didier Vidal wrote:
> > I've always wondered why the commits are systematically sent to
> > gnucash-patches... This results in noise and an additional chance to
> > forget or loose patches (since no dedicated tool e
On Monday 31 October 2005 11:01 pm, Josh Sled wrote:
> On Mon, 2005-10-31 at 22:50 +, Neil Williams wrote:
> > Josh, should I have access under the developer URL?
>
> You may need to use `svn co svn+ssh://[EMAIL PROTECTED]/[...]` to
> change the user being ssh-authenticated.
Doh!
Working now.
On Mon, 2005-10-31 at 22:50 +, Neil Williams wrote:
> Josh, should I have access under the developer URL?
Yes. If you can use cvs, then you should be able to use svn+ssh ...
it's the same mechanism used to invoke both.
> $ svn checkout
> svn+ssh://svn.gnucash.org/repo/gnucash/branches/gnuca
On Saturday 22 October 2005 11:04 pm, Josh Sled wrote:
> svn.gnucash.org is setup and resolves (thanks Linas! :), so the various
> base URLs look like:
>
> anonymous: http://svn.gnucash.org/repo/gnucash/trunk
> developer: svn+ssh://svn.gnucash.org/repo/gnucash/trunk
Josh, should I have acces
On Saturday 22 October 2005 11:04 pm, Josh Sled wrote:
> One thing cvs2svn does /not/ provide (that I can see, anyways) is the
> migration of the contents of the .cvsignore files into subversion's
> 'svn:ignore' directory-property. Perhaps someone wants to cut their teeth
> on subversion by doing
Josh Sled wrote:
On Tue, Oct 25, 2005 at 06:50:36PM -0400, Derek Atkins wrote:
| >Something like
| >http://www.goshaky.com/goshaky-distfiles/svn2rss/
| >might be useful once SVN is in use - and rss feed of svn commits.
|
|
RSS feeds are quite useful in their own ways
Wouldn't be too hard
Josh Sled wrote:
On Tue, Oct 25, 2005 at 06:50:36PM -0400, Derek Atkins wrote:
| |Something like
| |http://www.goshaky.com/goshaky-distfiles/svn2rss/
| |might be useful once SVN is in use - and rss feed of svn commits.
|
| I have no objection to this, but I don't see why it would be useful to
On Sun, 2005-10-30 at 20:01 +0100, Didier Vidal wrote:
> I've always wondered why the commits are systematically sent to
> gnucash-patches... This results in noise and an additional chance to
> forget or loose patches (since no dedicated tool exists to manage them).
>
> Why not just sending the pa
Sorry for answering late to this email. I was traveling last week, and
was away from my email...
My comment is just about the following specific point:
[...]
> I've setup the post-commit hook to mail the changeset diffs to
> '[EMAIL PROTECTED]'. Note that a seperate gnucash-patches mail of
> only
On Wed, 2005-10-26 at 14:35 +0100, Adrian Simmons wrote:
> Chris Lyttle wrote:
> > too many people having access and no control.
> That's part of the point of a CMS like Drupal. You still only need one person
> to
> install and maintain the actual CMS, but you can set up members of the site
> wi
Chris Lyttle wrote:
too many people having access and no control.
That's part of the point of a CMS like Drupal. You still only need one person to
install and maintain the actual CMS, but you can set up members of the site with
varying levels of access. Admin, Senior editor, content editor etc,
On Tue, Oct 25, 2005 at 10:58:36PM -0600, Chris Lyttle wrote:
> Just to add to this, there are 2 people who have access to change the
> gnucash website, Linas and myself. My access is somewhat limited (only
> to the parts that Linas has specifically added me to) but I can change
> what I need to. I
Derek Atkins wrote:
Basically, yes. It's Linas' personal machine and he doesn't want
just anybody to have shell access.
Perfectly understandable.
Moving the site to a CMS might well be an issue then, given the potential extra
overhead.
I have no objection to this, but I don't see why it wou
Just to add to this, there are 2 people who have access to change the
gnucash website, Linas and myself. My access is somewhat limited (only
to the parts that Linas has specifically added me to) but I can change
what I need to. I tend not to make any major changes without consulting
Linas as it is
On Tue, Oct 25, 2005 at 01:12:31PM -0400, Josh Sled wrote:
> On Tue, Oct 25, 2005 at 01:00:35PM -0400, Chris Shoemaker wrote:
>
> | On Tue, Oct 25, 2005 at 10:14:46AM -0400, Dan Widyono wrote:
> | > So.
> | >
> | > Is it possible for me to jump in, pull SVN down, install SVN + SVK on my
> | > wor
On Tue, Oct 25, 2005 at 06:50:36PM -0400, Derek Atkins wrote:
| >>I can ask. I know he's been really really busy.. He might be
| >>amenable to some CVS/SVN push into the web server.. I don't know.
| >Something like
| >http://www.goshaky.com/goshaky-distfiles/svn2rss/
| >might be useful once SVN
Quoting Adrian Simmons <[EMAIL PROTECTED]>:
and even our own WWW server (even if access
is somewhat restricted).
And it's restricted because?
Hosted in someone else's web space?
Basically, yes. It's Linas' personal machine and he doesn't want
just anybody to have shell access. Similarly,
Derek Atkins wrote:
Trac also has a patch tracker, so we could use that, too.
Trac certainly looks promising, I've looked at it before, but it seemed too much
for my one-man-webdev setup.
and even our own WWW server (even if access
is somewhat restricted).
And it's restricted because?
Hosted
On Tue, Oct 25, 2005 at 12:55:13PM -0400, Josh Sled wrote:
| Yes. Our web site needs 50-75% less words, and more appropriate ones.
FWIW, I had cause to go to the Evolution site [1] recently, and I consider
it a model of an excellent project site: pretty, clean, minimalist,
content-rich yet conc
On Tue, Oct 25, 2005 at 01:00:35PM -0400, Chris Shoemaker wrote:
| On Tue, Oct 25, 2005 at 10:14:46AM -0400, Dan Widyono wrote:
| > So.
| >
| > Is it possible for me to jump in, pull SVN down, install SVN + SVK on my
| > workstation, diddle away using my own local personal branch, submit frequent
On Tue, Oct 25, 2005 at 10:14:46AM -0400, Dan Widyono wrote:
>
> So.
>
> Is it possible for me to jump in, pull SVN down, install SVN + SVK on my
> workstation, diddle away using my own local personal branch, submit frequent
> patchsets to the list, and when all is said and done, submit my branch
On Tue, Oct 25, 2005 at 11:16:51AM +0100, Neil Williams wrote:
| developers on code management. Some method of clearly attributing branches to
| particular goals beyond a short, cryptic, branch name.
"short, cryptic, branch name[s]" such as?
| 3. More acceptance that new developers don't nece
Chris Shoemaker <[EMAIL PROTECTED]> writes:
> Just because it's *technically* possible doesn't mean there's not a
> problem. (It just means there's no technical problem.) The real
> problem is PSYCHOLOGICAL. Email is final. For whatever reason, and
You never try to solve a social problem with
On Mon, Oct 24, 2005 at 08:09:23PM -0400, Chris Shoemaker wrote:
| So we agree, yes? :)
Sounds like we mostly do, yes. I don't think branches are needed for "all"
development, but they can be useful.
...jsled
--
http://asynchronous.org/jsled/ | a=jsled; b=asynchronous.org; echo [EMAIL
PROTEC
Quoting Neil Williams <[EMAIL PROTECTED]>:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adrian Simmons wrote:
| Neil Williams wrote:
|
|> 4. Has anyone seriously considered using the SourceForge project more?
|
| Personally I find SF painfully slow and clunky.
A slow site is better than a clo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adrian Simmons wrote:
| Neil Williams wrote:
|
|> 4. Has anyone seriously considered using the SourceForge project more?
|
| Personally I find SF painfully slow and clunky.
A slow site is better than a closed site!
:-)
|> 5. More write access to onl
Quoting Dan Widyono <[EMAIL PROTECTED]>:
So.
Is it possible for me to jump in, pull SVN down, install SVN + SVK on my
workstation, diddle away using my own local personal branch, submit frequent
patchsets to the list, and when all is said and done, submit my branch
somehow to the central repos
So.
Is it possible for me to jump in, pull SVN down, install SVN + SVK on my
workstation, diddle away using my own local personal branch, submit frequent
patchsets to the list, and when all is said and done, submit my branch
somehow to the central repository for safekeeping?
Dan W.
_
Neil Williams wrote:
4. Has anyone seriously considered using the SourceForge project more?
Personally I find SF painfully slow and clunky.
5. More write access to online information outside the mailing list archives.
The gnucash.org website is not being updated, new documentation has to go on
First, a little Hello,
I'm Adrian Simmons and I've been subscribed to gnucash-user for some time, but
decided I'd come and lurk here for a while, and though I'm only a web geek at
least see if I can help out somewhere. I run Gnucash on OS X via Fink.
Chris Shoemaker wrote:
Giving one more pe
On Tuesday 25 October 2005 3:26 am, Chris Shoemaker wrote:
> On Mon, Oct 24, 2005 at 09:37:07PM -0400, David Hampton wrote:
> > > I've spent more time refreshing out-of-tree patches that I have
> > > actually developing code! (ok, not really, but a LOT of time, it's a
> > > PITA.)
> >
> > You shoul
On Mon, Oct 24, 2005 at 09:37:07PM -0400, David Hampton wrote:
> On Mon, 2005-10-24 at 20:37 -0400, Chris Shoemaker wrote:
>
> > Maybe that's a reasonable criteria for giving someone commit access to
> > the OneTrueBuild. But, that's not reasonable criteria for giving
> > someone access to conven
On Mon, 2005-10-24 at 20:37 -0400, Chris Shoemaker wrote:
> Maybe that's a reasonable criteria for giving someone commit access to
> the OneTrueBuild. But, that's not reasonable criteria for giving
> someone access to convenient SCM. That's like saying: We love for
> people to join us on this tr
On Mon, Oct 24, 2005 at 01:20:11PM -0400, Derek Atkins wrote:
> Quoting Brian <[EMAIL PROTECTED]>:
>
> >>My point is not so much "distributed is better than centralized", as
> >>it is "lower the barriers to new developers by letting them share code
> >>early and often." Distributed SCM is *one* w
On Mon, Oct 24, 2005 at 04:48:22PM -0400, Derek Atkins wrote:
> Quoting Chris Shoemaker <[EMAIL PROTECTED]>:
>
> PS: I still don't agree with your premise that the gnucash project needs
> to radically change its development processes in order to increase the
> number of fringe developers. Histori
On Mon, Oct 24, 2005 at 04:59:18PM -0400, Josh Sled wrote:
> On Mon, Oct 24, 2005 at 04:45:47PM -0400, Chris Shoemaker wrote:
>
> | Well, I think *all* development should be on branches.
>
> Ick. Now we have to fight about the benefits of Continuous Integration. :)
I can't tell if you're saying
On Mon, Oct 24, 2005 at 04:45:47PM -0400, Chris Shoemaker wrote:
| Well, I think *all* development should be on branches.
Ick. Now we have to fight about the benefits of Continuous Integration. :)
(Strangely, its argument [1] has a similar form: "[...] fundamental shift
to the whole development
Quoting Chris Shoemaker <[EMAIL PROTECTED]>:
Well, I think *all* development should be on branches.
I disagree. There is PLENTY of development that doesn't need to be done
on a branch. When I wrote the business features, there's no reason
that all the code in src/business had to be on a bran
Quoting Chris Shoemaker <[EMAIL PROTECTED]>:
Derek,
I apologize for dredging up the past like that. I said I
wanted to remain constructive, but my actions said otherwise. I wish
I could take it back. I /will/ try to exercise more self-control in
the future. Please forgive me.
I sti
On 10/25/05, Derek Atkins <[EMAIL PROTECTED]> wrote:
> The problem is that historically the commiters have been restricted to
> a trusted
> group of people, but there are a few "new" developers who have not yet been
> given commit access. Honestly I can only think of one developer in
> particular.
On Mon, Oct 24, 2005 at 04:16:57PM -0400, David Hampton wrote:
> On Mon, 2005-10-24 at 13:42 -0400, Chris Shoemaker wrote:
>
> > If you'd like some more detailed info, I'd recommend:
> > [5] for the heart of the issue in concise terms
> > [6] for an good overview of the main SCM debate
> > [8] for
On Mon, Oct 24, 2005 at 03:20:15PM -0400, David Hampton wrote:
> On Mon, 2005-10-24 at 14:52 -0400, Chris Shoemaker wrote:
>
> > It kind of makes me want to respond like others have [1],
> > but I want to remain constructive.
>
> If you wanted to remain constructive you wouldn't have posted that
On Mon, 2005-10-24 at 13:42 -0400, Chris Shoemaker wrote:
> If you'd like some more detailed info, I'd recommend:
> [5] for the heart of the issue in concise terms
> [6] for an good overview of the main SCM debate
> [8] for an overview of SCM softwares available
> [1, 2, 7] for some informative Ar
On Mon, 24 Oct 2005, Chris Shoemaker wrote:
> > > Here's a fun link to git's author's opinion on the matter:
> > > http://www.gelato.unsw.edu.au/archives/git/0504/0594.html
> >
> > The main point here is that per file tracking is wrong - and I would
> > agree. Maybe I'm missing something, but fr
On Mon, 2005-10-24 at 14:52 -0400, Chris Shoemaker wrote:
> It kind of makes me want to respond like others have [1],
> but I want to remain constructive.
If you wanted to remain constructive you wouldn't have posted that URL.
David
___
gnucash-devel
On Mon, Oct 24, 2005 at 02:02:51PM -0400, Derek Atkins wrote:
> Quoting Chris Shoemaker <[EMAIL PROTECTED]>:
>
> >>A very important feature for me is that the repository format stills
> >>allows
> >>me to extract the latest version of things if it gets corrupted. I'm
> >>not sure SVN meets that
On Mon, Oct 24, 2005 at 01:20:11PM -0400, Derek Atkins wrote:
> The problem is that historically the commiters have been restricted
> to a trusted group of people,
I disagree that that's the problem, but, assuming you're
right... How's that strategy been working for GnuCash over the past 3
years?
Quoting Chris Shoemaker <[EMAIL PROTECTED]>:
A very important feature for me is that the repository format stills allows
me to extract the latest version of things if it gets corrupted. I'm
not sure SVN meets that criterion, but CVS does. That was the main
motivation for us moving from SCCS to
On Mon, Oct 24, 2005 at 12:38:35PM -0400, Stuart D. Gathman wrote:
> On Sun, 23 Oct 2005, Chris Shoemaker wrote:
>
> > > I thought this was the main point of SVN, and the motivation for
> > > replacing CVS - that it has atomic changesets that affect many files.
> >
> > Please see: http://subversi
Quoting Brian <[EMAIL PROTECTED]>:
My point is not so much "distributed is better than centralized", as
it is "lower the barriers to new developers by letting them share code
early and often." Distributed SCM is *one* way to do that.
I agree with with Chris on this one. I am not much of a de
On Sun, 23 Oct 2005, Chris Shoemaker wrote:
> > I thought this was the main point of SVN, and the motivation for
> > replacing CVS - that it has atomic changesets that affect many files.
>
> Please see: http://subversion.tigris.org/faq.html#changesets
>
> for a rather biased, but not unhelpful a
On Mon, 2005-24-10 at 10:53 -0400, Chris Shoemaker wrote:
> The actual state of things is that there are *very* few developers,
> and I think the survival of gnucash depends on attracting more. That
> doesn't necessarily require a distributed model, but I think one key
> step is providing the con
On Mon, Oct 24, 2005 at 03:37:52PM +0200, Fabien COELHO wrote:
>
> Dear Chris,
>
> >** Changesets **
> >** Centralized vs. Distributed **
> > In summary, I think there are two main reasons for looking
> >further than SVN for SCM software. 1) Changesets are a big
> >convenience for all deve
Dear Chris,
** Changesets **
** Centralized vs. Distributed **
In summary, I think there are two main reasons for looking
further than SVN for SCM software. 1) Changesets are a big
convenience for all developers. 2) Distributed SCM lets fringe
developers benefit from a real SCM, too.
On Sun, 23 Oct 2005, Chris Shoemaker wrote:
> Alternatively, for another breed of SCMs the model is: the
> repository is a project that has history, which happens to be
> represented by files. This distinction may (or may not?) seem subtle
> but it is HUGE. This is the whole concept of
>
On Sun, Oct 23, 2005 at 07:09:36PM -0400, Stuart D. Gathman wrote:
> On Sun, 23 Oct 2005, Chris Shoemaker wrote:
>
> > Alternatively, for another breed of SCMs the model is: the
> > repository is a project that has history, which happens to be
> > represented by files. This distinction ma
SVN is clearly superior to CVS. SVN basically seems like a
faster, less-annoying, more-featureful version of CVS. But, like CVS, it
was never intended to be a SCM system [1], it's just a version control
system. Since we're obviously writing software, I think a real SCM
has compelling adv
Generally, I'm happy with the proposed changes, and personally, I don't
see anything wrong with invalidating the old names, especially as we're
getting close to doing a new release branch anyway. The proposed
structure looks fine to me. Of course, since I'm not doing any active
development, none o
On Sat, 2005-10-22 at 18:50 -0400, Chris Shoemaker wrote:
> I tried to view a diff and got this:
Hmm, I read comments mentioning something like this, but didn't see it
myself. Admittedly, I didn't test too much.
In the last released viewcvs (0.9.4), the subversion support seems to be
broken. Th
I tried to view a diff and got this:
An Exception Has Occurred
Python Traceback
Traceback (most recent call last):
File "/usr/lib/viewcvs-1.0/lib/viewcvs.py", line 3362, in main
request.run_viewcvs()
File "/usr/lib/viewcvs-1.0/lib/viewcvs.py", line 379, in run_viewcvs
self.view_func(s
Recently we've been planning on moving the GnuCash repository from CVS to
Subversion. This week I've made the changes on cvs.gnucash.org to enable
anonymous and developer access to a subversion repository. This encompases:
- http-style anonymous access
- svn+ssh authenticated developer acce
61 matches
Mail list logo
