2014/1/16 风尹 :
> it's not convenient for me ! i am used to using git to control my code
> version.
> the repo is difficult to get the src code if i don't use svn.
I'm not sure if I understand you, what's the problem with getting the
source code?
Regards
--
Łukasz
+ 48 606 323 122 http://www.le
it's not convenient for me ! i am used to using git to control my code version.
the repo is difficult to get the src code if i don't use svn.
-- 原始邮件 --
发件人: "Lukasz Lenart";;
发送时间: 2014年1月16日(星期四) 下午3:39
收件人: "Struts Developers List";
主题: Migrated Struts2 examp
-- 原始邮件 --
发件人: "风尹";;
发送时间: 2014年1月16日(星期四) 下午3:33
收件人: "Struts Developers List";
主题: 回复： 回复：Git flow
aha, thank you very much!
-- 原始邮件 --
发件人: "Lukasz Lenart";;
发送时间: 2014年1月16日(星期四) 下午3:27
收件人: "Struts Developers List";
WDYT?
http://svn.apache.org/repos/asf/struts/sandbox/trunk/struts2examples/
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mai
aha, thank you very much!
-- 原始邮件 --
发件人: "Lukasz Lenart";;
发送时间: 2014年1月16日(星期四) 下午3:27
收件人: "Struts Developers List";
主题: Re: 回复：Git flow
2014/1/16 风尹 :
> where can I find the repository of the struts?
http://struts.apache.org/dev/builds.html
https://twi
2014/1/16 风尹 :
> where can I find the repository of the struts?
http://struts.apache.org/dev/builds.html
https://twitter.com/TheApacheStruts/status/423709484155150336
https://git-wip-us.apache.org/repos/asf/struts.git
http://git.apache.org/repos/asf/struts.git
https://github.com/apache/struts
Re
I still don't get it - what is the problem with moving the source to
attic? It isn't valid source code any more - what is valid are the
tags (/struts2/tags/STRUTS_2_3_8) but I doubt that anybody uses them
(except us).
Wicket - very good example, I didn't know it isn't valid source code
anymore (I
where can I find the repository of the struts?
-- 原始邮件 --
发件人: "Lukasz Lenart";;
发送时间: 2014年1月16日(星期四) 下午3:01
收件人: "Struts Developers List";
主题: Git flow
Hi,
As Struts migrated to Git it's time to plan what kind of git flow we
are going to use.
I thought a
Hi,
As Struts migrated to Git it's time to plan what kind of git flow we
are going to use.
I thought about something like that:
- 'master' contains always the latest released source (also as a tagged version)
- 'develop' contains the next version and we can commit some small
patches directly to i
2.3.16 Exception below, plus lib folder print out.
total 8168
drwxr-xr-x 15 andrewcarr staff 510 Dec 19 06:39 .
drwxr-xr-x 6 andrewcarr staff 204 Dec 19 06:36 ..
-rw-r--r-- 1 andrewcarr staff 43578 Dec 19 06:36 asm-3.3.jar
-rw-r--r-- 1 andrewcarr staff 38275 Dec 19 06:3
I wonder what the downside is to just put svn subtrees in question into
read only mode compared to moving them to attic. As for placing a
prominent notice, such as MOVED-TO-GIT-README.txt, it would be useful to
our users in either case.
Having a look at wicket, they just left svn at a point in tim
2014/1/15 Paul Benedict :
> The published POMs should all have a link to the SCM URL. We shouldn't move
> to the attic so those links can stay valid.
Ok, what is wrong if they become invalid? Maybe people start thinking
about migration :-)
> And what do you mean "cut the wire"? Is that an Apache
The published POMs should all have a link to the SCM URL. We shouldn't move
to the attic so those links can stay valid.
And what do you mean "cut the wire"? Is that an Apache directive to stop
people from going to svn?
On Wed, Jan 15, 2014 at 2:39 AM, Lukasz Lenart wrote:
> We suppose to cut of
We suppose to cut off the wire - as moving the repos showed that we
still have a problem with DTDs. And published POMs shouldn't be a
problem, there are links in ciManagement section only or do I miss
something?
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
2014/1/14 Paul Benedic
14 matches
Mail list logo
