On 28.09.2010 19:11, Mark Thomas wrote:
On 28/09/2010 17:36, David Jencks wrote:
From what I hear the best advice is "use git, not svn". However that's
usually difficult at apache.
There are git mirrors for trunk and 6.0.x/trunk but that does rely on a
Tomcat committer also using git. Anyo
On 28/09/2010 17:36, David Jencks wrote:
>
> From what I hear the best advice is "use git, not svn". However that's
> usually difficult at apache.
There are git mirrors for trunk and 6.0.x/trunk but that does rely on a
Tomcat committer also using git. Anyone?
I had high hopes for git, particul
2010/9/28 Wesley Acheson :
> HI All,
>
> I'm not actually sure how OT this is or if the question belongs here.
>
> This is semi duplicating some comments seen in a bug. However I think
> its useful for anyone trying to create future patches who is
> inexperienced like me, so I'm sort of double post
On Sep 28, 2010, at 7:23 AM, Wesley Acheson wrote:
> HI All,
>
> I'm not actually sure how OT this is or if the question belongs here.
>
> This is semi duplicating some comments seen in a bug. However I think
> its useful for anyone trying to create future patches who is
> inexperienced like me
fficulty creating working patch - renamed file.
>
>> However as It hasn't got the new filename in SVN when
>> that patch is applied it breaks.
>
> Have you tried "svn add" to register the new (renamed) file in the
> .svn/entries file?
>
> - Chuck
>
> From: Wesley Acheson [mailto:wesley.ache...@gmail.com]
> Subject: [OT] Difficulty creating working patch - renamed file.
> However as It hasn't got the new filename in SVN when
> that patch is applied it breaks.
Have you tried "svn add" to register the new (rename
HI All,
I'm not actually sure how OT this is or if the question belongs here.
This is semi duplicating some comments seen in a bug. However I think
its useful for anyone trying to create future patches who is
inexperienced like me, so I'm sort of double posting.
I'm trying to create a patch. How
