On Tue, Feb 15, 2011 at 10:44 AM, Stefan Sperling wrote:
> On Tue, Feb 15, 2011 at 10:41:13AM -0500, NN Ott wrote:
> > Are things still on track for a q1 release?
>
> We're trying.
>
OK, here's hoping for smooth sailing. :-)
On Tue, Feb 15, 2011 at 12:31 AM, Daniel Shahaf wrote:
> > > - Will either of the above improvements help me if the server
> > > _does_ get upgraded to v1.7?
> > >
> > > - Will either of the above improvements help me if the server _does
> > > not_ get upgraded to v1.7?
> >
> > All that said, I ne
>
>
> >
> > My machine is pretty beefy, so that's not the bottle neck. Network
> > speed to the remote svn server is OK, but not terrible, and
> > certainly not the bottle neck.
>
> It could be if it is a windows machine. Trying checking out to a RAM disk.
> I have found the performance is much mu
On Mon, Feb 14, 2011 at 4:52 PM, ankush chadha
wrote:
> Is there a reason to checkout 40k files again and again? Can it be
> substituted by an svn update (after first checkout)?
>
>
Well, I obviously try use update/switch to avoid a fresh checkout. :)
Using cmd-line & tortisesvn on windows.
I n
Hello,
I notice that svn v1.7 is slated to have a new transfer protocol as well as
new WC module.
( http://subversion.apache.org/roadmap.html )
Right now, I have a repo with ~40,000 source and xml files.
Full checkouts take forever.
My machine is pretty beefy, so that's not the bottle neck. N
Hello,
Here is what i've got:
I've got an svn:external'd folder within my working copy in to which I've
made some local changes.
Short of writing a script, is there a command I can use to svn switch to a
different branch, but not clobber my local changes in the svn:external'd
folder? (Unless th
On Wed, Jan 26, 2011 at 5:02 PM, amol gole wrote:
> I am a tortise svn user. I recently started trying the svn:externals
> property to share files between projects. I got this feature to work and I
> am happy with it so far.
>
> My question is related to how tags should behave with such shared fi
On Tue, Jan 11, 2011 at 2:16 PM, Stefan Sperling wrote:
> On Tue, Jan 11, 2011 at 01:36:37PM -0500, NN Ott wrote:
> > I just want the svn copy/log/diff/merge logic to see past, and account
> for,
> > and svn:external barrier. Very much a one-way flow of changes. Imho,
&g
On Tue, Jan 11, 2011 at 1:02 PM, Stefan Sperling wrote:
> On Tue, Jan 11, 2011 at 12:36:58PM -0500, NN Ott wrote:
> > >
> > >
> > > >> To recap, as Les put it:
> > > >>
> > > >> I think the idea is that he'd like to see
On Tue, Jan 11, 2011 at 12:50 PM, Andy Levy wrote:
> On Tue, Jan 11, 2011 at 12:42, NN Ott wrote:
> > Hi all,
> > If UserA checks out a working copy on to his machine, can UserB walk up
> to
> > that machine and the commit changes under his own credentials?
> >
Hi all,
If UserA checks out a working copy on to his machine, can UserB walk up to
that machine and the commit changes under his own credentials?
Would seem possible, but just wanted to double check if there are any pit
falls.
Thanks
>
>
> >> To recap, as Les put it:
> >>
> >> I think the idea is that he'd like to see the development history of
> both the vendor and local changes as a continuous set of changes as you
> would if they were in the same repository with log and diff working across
> any points in time or branch vers
>
> > That's exactly right.
> >
> > Should I post this to the dev list?
>
> No. Your question is clearly a usage question so it is not appropriate
> for the dev list
Since it's been firmly established as Impossable in the
current architecture of subversion, I guess this has turned into more of a
>
>
>
>> Can I make a local (patched) branch of an svn:external? That way I could
>>> pull updates as needed, but still retain access to the full commit
>>> history.
>>>
>>
>> You'd need to manually (or some automated fashion) apply each commit
>> made to their repository to your own repository.
>
> > >
> > > I have a source library that I need to periodically import (and then
> patch)
> > > for use by my code base.
> > >
> > > The SVN Book seems to reccomend a "vendor branch" scheme where you keep
> a
> > > patched branch of the "vendor drops". This would work, except that I
> loose
> > >
Hello,
I have a source library that I need to periodically import (and then patch)
for use by my code base.
The SVN Book seems to reccomend a "vendor branch" scheme where you keep a
patched branch of the "vendor drops". This would work, except that I loose
any history of the library development.
16 matches
Mail list logo
