On Sat, Dec 26, 2009 at 06:08:15PM +0100, Branko Čibej wrote:
> Every couple of years someone comes up with a proposal like this, and it
> usually ends with a client-side hooks idea. Beh. Subversion is a version
> control system, not a build systam. If you want "current global
> revision" to label
Christian Schoenebeck wrote:
> On Saturday 26 December 2009 18:08:15 Branko Čibej wrote:
>
>> Every couple of years someone comes up with a proposal like this, and it
>> usually ends with a client-side hooks idea. Beh. Subversion is a version
>> control system, not a build systam. If you want "c
On Saturday 26 December 2009 18:08:15 Branko Čibej wrote:
> Every couple of years someone comes up with a proposal like this, and it
> usually ends with a client-side hooks idea. Beh. Subversion is a version
> control system, not a build systam. If you want "current global
> revision" to label your
Stefan Sperling wrote:
> On Thu, Dec 24, 2009 at 06:39:17PM +0100, Christian Schoenebeck wrote:
>
>> On Thursday 24 December 2009 17:00:00 Stefan Sperling wrote:
>>
>>> What problem do you really want to solve with this?
>>> Why is svnversion not good enough for your problem?
>>>
>>
On Thu, Dec 24, 2009 at 06:39:17PM +0100, Christian Schoenebeck wrote:
> On Thursday 24 December 2009 17:00:00 Stefan Sperling wrote:
> > What problem do you really want to solve with this?
> > Why is svnversion not good enough for your problem?
>
> Since svnversion is a separate application, it h
On Thursday 24 December 2009 17:04:08 Julian Foad wrote:
> Hi Christian.
>
> Before you spend lots more time and effort on discussing how to
> implement "this thing" efficiently ...
>
> I think this feature is exactly the sort of thing that would make sense
> as a plug-in to Subversion, and not a
On Thursday 24 December 2009 17:00:00 Stefan Sperling wrote:
> What problem do you really want to solve with this?
> Why is svnversion not good enough for your problem?
Since svnversion is a separate application, it has to be embedded in some way,
e.g. into a Makefile and then passed to a local s
On Thu, 2009-12-24 at 11:04 -0500, Julian Foad wrote:
> I think this feature is exactly the sort of thing that would make sense
> as a plug-in to Subversion, and not as part of the core product
It's possible that the entire keyword system would make more sense as a
plug-in to some version control
Hi Christian.
Before you spend lots more time and effort on discussing how to
implement "this thing" efficiently ...
I think this feature is exactly the sort of thing that would make sense
as a plug-in to Subversion, and not as part of the core product, but
Subversion does not (yet) have a plug-i
On Thu, Dec 24, 2009 at 04:44:24PM +0100, Christian Schoenebeck wrote:
> On Thursday 24 December 2009 15:59:38 Stefan Sperling wrote:
> > What if I do an update which should not update the working copy
> > root, such as "svn update somefile"?
>
> Then you have a mixed revision working copy. To add
On Thursday 24 December 2009 15:59:38 Stefan Sperling wrote:
> What if I do an update which should not update the working copy
> root, such as "svn update somefile"?
Then you have a mixed revision working copy. To address this case a bit
better, instead of introducing one new keyword like "Global
On Thu, Dec 24, 2009 at 03:42:38PM +0100, Christian Schoenebeck wrote:
> On Thursday 24 December 2009 14:23:25 Bert Huijben wrote:
> > Currently on a 'svn update' the client receives a list of files from the
> > repository that are updated with the information on how they are updated.
> >
> > E.g
On Thursday 24 December 2009 14:23:25 Bert Huijben wrote:
> Currently on a 'svn update' the client receives a list of files from the
> repository that are updated with the information on how they are updated.
>
> E.g. if you call 'svn update' on a working copy with 1 files, you
> receive cha
> -Original Message-
> From: Christian Schoenebeck [mailto:c...@users.sf.net]
> Sent: donderdag 24 december 2009 13:38
> To: dev@subversion.apache.org
> Subject: Re: new substitution keyword for global repository revision
>
> On Thursday 24 December 2009 12:48:
On Thursday 24 December 2009 12:48:59 Bert Huijben wrote:
> This solution won't work, because Subversion only updates files if they are
> already updated for other reasons. You would have to fix that (and thereby
> make the average update command much slower).
>
> Your keyword would require updati
On Thu, 2009-12-24 at 12:48 +0100, Bert Huijben wrote:
>
> > -Original Message-
> > From: Christian Schoenebeck [mailto:c...@users.sf.net]
> > Sent: donderdag 24 december 2009 11:17
> > To: dev@subversion.apache.org
> > Subject: new substitution keywo
> -Original Message-
> From: Christian Schoenebeck [mailto:c...@users.sf.net]
> Sent: donderdag 24 december 2009 11:17
> To: dev@subversion.apache.org
> Subject: new substitution keyword for global repository revision
>
> Hi!
>
> I would like to work on int
Hi!
I would like to work on introducing a new substitution keyword which always
reflects the latest repository revision. A client side way with svnversion
embedded into a Make file or something is not a solution for me.
I'm not used to the subversion code base yet. Just chased a bit over the tr
18 matches
Mail list logo
