> Is there any way to change the native newline mode for a particular
> working copy?
>
> I'm checking out code in Linux, over a CIFS mount to a Windows machine
> where it's being used. This is much easier for me than any of the
> solutions involving Windows clients, but ends up with Unix line
>
On Feb 12, 2010, at 16:05, Bob Archer wrote:
>> Is there any way to change the native newline mode for a particular
>> working copy?
>>
>> I'm checking out code in Linux, over a CIFS mount to a Windows machine
>> where it's being used. This is much easier for me than any of the
>> solutions inv
> On Feb 12, 2010, at 16:05, Bob Archer wrote:
>
> >> Is there any way to change the native newline mode for a particular
> >> working copy?
> >>
> >> I'm checking out code in Linux, over a CIFS mount to a Windows machine
> >> where it's being used. This is much easier for me than any of the
> >>
On Fri, Feb 12, 2010 at 5:16 PM, Bob Archer wrote:
> Ah I see. Then wouldn't he just specify svn:eol-style CRLF? Assuming he only
> every edits with Windows tools.
This isn't Windows-only code, and it's not code that only I'm
touching. If someone's checking it out in Linux to compile in Linux
n
On Feb 12, 2010, at 16:32, Glenn Maynard wrote:
>> Although I'm not sure why he wouldn't check out with a windows client. I'm
>> not sure how connecting to a Linux machine to checkout to a folder mounted
>> on a windows machine is easier than using the windows CLI.
>
> It's easier because it's
> > Although I'm not sure why he wouldn't check out with a windows client.
> I'm not sure how connecting to a Linux machine to checkout to a folder
> mounted on a windows machine is easier than using the windows CLI.
>
> It's easier because it's a fully configured CLI that I already have
> running
On Fri, Feb 12, 2010 at 6:23 PM, Bob Archer wrote:
> Use the native windows CLI. No clumsy Cygwin needed. But, to each his own.
What, CMD? That's an order of magnitude worse than Cygwin.
> I would complain to MS about Studio mangling your line endings. Although my
> understanding was it suppor
Greetings, Glenn Maynard!
>> Although I'm not sure why he wouldn't check out with a windows client. I'm
>> not sure how connecting to a Linux machine to checkout to a folder mounted
>> on a windows machine is easier than using the
>> windows CLI.
> It's easier because it's a fully configured CL
Greetings, Glenn Maynard!
> Is there any way to change the native newline mode for a particular
> working copy?
> I'm checking out code in Linux, over a CIFS mount to a Windows machine
> where it's being used. This is much easier for me than any of the
> solutions involving Windows clients, but
Greetings, Glenn Maynard!
>> Use the native windows CLI. No clumsy Cygwin needed. But, to each his own.
> What, CMD? That's an order of magnitude worse than Cygwin.
First, CMD is quite powerful, if you know how to cook it.
Second, http://jpsoft.com/
Third, I think Bob was referring to native Wi
On Fri, Feb 12, 2010 at 10:15 PM, Andrey Repin wrote:
> Don't do that. Check out it where it'll be used.
Telling people "don't do what you want to do; do what you don't want
instead" is not helpful.
> First, CMD is quite powerful, if you know how to cook it.
It doesn't really matter how powerfu
On Fri, Feb 12, 2010 at 10:56:28PM -0500, Glenn Maynard wrote:
> Telling people "don't do what you want to do; do what you don't want
> instead" is not helpful.
o rly?
I haven't been following this thread closely but it seems that your
complaint is the classic, "Doctor, it hurts when I do this."
On Feb 13, 2010, at 10:11, Tyler Roscoe wrote:
> I can't find it right now but there was a presentation about the top ten
> ways *not* to use Subvesion. One of the entries was about using
> Subversion in a way that it was not designed to be used. This arises
> most frequently when people want to
On Sat, Feb 13, 2010 at 11:11 AM, Tyler Roscoe wrote:
> I haven't been following this thread closely but it seems that your
> complaint is the classic, "Doctor, it hurts when I do this." Several
> people in the community have suggested, "Then don't do that." I would
> take this sage advice (i.e. d
On Feb 13, 2010, at 16:09, Glenn Maynard wrote:
> I suspect that it's not a massive project to actually implement this
> properly; fundamentally, it probably means adjusting
> svn_wc__get_eol_style to allow substituting "native" for one of the
> other EOL modes, based on a working-copy-local sett
On Sat, Feb 13, 2010 at 7:10 PM, Ryan Schmidt
wrote:
> "svn export" already has a "--native-eol" switch. This is easy because after
> exporting, Subversion doesn't have to deal with that directory anymore. But
> as a fellow user I think it would fit nicely to have the same switch on "svn
> chec
On Feb 13, 2010, at 19:00, Glenn Maynard wrote:
> A database representing the whole working copy? That's odd--I can't
> think of how that could generally handle actions like cloning a whole
> WC (cp -a wc1 wc2), pulling a piece out of a WC creating a new WC as a
> result (mv wc1/trunk .; rm -rf
Ryan Schmidt wrote:
> On Feb 13, 2010, at 19:00, Glenn Maynard wrote:
>
>> A database representing the whole working copy? That's odd--I can't
>> think of how that could generally handle actions like cloning a whole
>> WC (cp -a wc1 wc2), pulling a piece out of a WC creating a new WC as a
>> resu
Greetings, Glenn Maynard!
>> I haven't been following this thread closely but it seems that your
>> complaint is the classic, "Doctor, it hurts when I do this." Several
>> people in the community have suggested, "Then don't do that." I would
>> take this sage advice (i.e. don't share working copie
On Feb 13, 2010, at 23:09, Andrey Repin wrote:
> Second, don't join replies to multiple authors in one post - it's frustrating.
Actually, the mailing list guidelines encourage us to do this:
http://subversion.apache.org/docs/community-guide/mailing-lists.html#when-to-post
On Sun, Feb 14, 2010 at 12:09 AM, Andrey Repin wrote:
> First, I said already, AnkhSVN.
And I've already explained that I want to use my existing Linux CLI to
manipulate all of my repositories, so I don't have separate SVN
interfaces for each of my working copies. That's the *whole point*.
A Win
On Sat, Feb 13, 2010 at 9:56 PM, C. Michael Pilato wrote:
> You can't think how that would handle those actions because many of them
> won't be handled at all. 'cp -a wc1 wc2' will result in a non-working-copy
> named 'wc2'. 'mv wc1/trunk .; rm -rf wc1' will result in a non-working-copy
> named
On Sun, Feb 14, 2010 at 2:34 AM, Glenn Maynard wrote:
> Based on looking through [1] some more, it looks like "cp -a wc1 wc2"
> and renaming working copies should work fine, since the database is
> inside the working copy, and will just get copied along with the rest.
In SVN 1.7 there will be a
On Sun, Feb 14, 2010 at 9:45 AM, Mark Phippard wrote:
> copy. Beyond 1.7 there are plans to make this configurable so that
> you could have it in ~/.subversion and shared across all your working
> copies. Of course the default will be the same as it will be in 1.7.
That sound brittle. Users wo
> On Fri, Feb 12, 2010 at 6:23 PM, Bob Archer wrote:
> > Use the native windows CLI. No clumsy Cygwin needed. But, to each his
> own.
>
> What, CMD? That's an order of magnitude worse than Cygwin.
Because it doesn't have the Unix cl tools? If you install msysgit it adds
pretty much all the Uni
25 matches
Mail list logo
