You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Benjamin Bentmann <be...@udo.edu> on 2011/03/30 12:20:44 UTC
Re: svn commit: r1086889 - /maven/indexer/trunk/indexer-core/src/test/java/org/apache/maven/index/packer/NEXUS4149TransferFormatTest.java
Hi Tamas,
> Author: cstamas
> Date: Wed Mar 30 10:07:35 2011
> New Revision: 1086889
>
> URL: http://svn.apache.org/viewvc?rev=1086889&view=rev
> Log:
> NEXUS-4152: added UT covering the same issue
I think it would be more appropriate if those commits were mentioning
the corresponding MINDEXER issue.
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: svn commit: r1086889 - /maven/indexer/trunk/indexer-core/src/test/java/org/apache/maven/index/packer/NEXUS4149TransferFormatTest.java
Posted by Tamás Cservenák <ta...@cservenak.net>.
All gitters (like me) having forks would need just a re-fetch again
(reinit the git-svn and refetch the svn history). But not sure what
will happen with ASF Git mirror? (the git.apache.org/maven-indexer.git
one)
If you can change svn logs, and you do know the ASF Git mirror will be
okay (I dunno), then i'd say go for it.
And again, sorry for messing this up :(
Thanks,
~t~
On Thu, Mar 31, 2011 at 2:35 AM, Brett Porter <br...@apache.org> wrote:
> Would it affect the git history if the svn logs were modified with the updated issue numbers now that it has already been pushed?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: svn commit: r1086889 - /maven/indexer/trunk/indexer-core/src/test/java/org/apache/maven/index/packer/NEXUS4149TransferFormatTest.java
Posted by Brett Porter <br...@apache.org>.
Would it affect the git history if the svn logs were modified with the updated issue numbers now that it has already been pushed?
On 30/03/2011, at 10:06 PM, Tamás Cservenák wrote:
> Hi,
>
> completely agreed, but let me explain -- not that it matters:
>
> I had a lot of accumulated changes in my github fork of maven-indexer,
> and initially did not wanted to disturb other forks of my repository.
>
> Hence, I started pushing changes _without_ changing commit messages
> first -- thinking "it would change history, hence screw other forks".
>
> I was distracted with ASF SVN mirroring pain (dcommiting multiple
> commits from EU, --no-rebase was not helping, there was a lot of
> interlaving changes for same file), but solved luckily:
>
> http://twitter.com/#!/cstamas/status/53021178750701568
>
> And then I realized: git-svn _also modifies_ history, but it was late
> then :( I already started pushing (and had to recover few times until
> I found out the dnsmasq fix), since there was a LOT of commits to be
> dcommited back to ASF SVN.
>
> To at least make it better, I linked the MINDEXER jira issues to the
> SVN revisions, so at least we have the JIRA->SVN direction, but SVN
> commit logs does not point back.
>
> http://jira.codehaus.org/browse/MINDEXER-15
> http://jira.codehaus.org/browse/MINDEXER-16
> http://jira.codehaus.org/browse/MINDEXER-17
> http://jira.codehaus.org/browse/MINDEXER-18
>
>
>
> Thanks,
> ~t~
>
> On Wed, Mar 30, 2011 at 12:20 PM, Benjamin Bentmann
> <be...@udo.edu> wrote:
>> I think it would be more appropriate if those commits were mentioning the
>> corresponding MINDEXER issue.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: svn commit: r1086889 - /maven/indexer/trunk/indexer-core/src/test/java/org/apache/maven/index/packer/NEXUS4149TransferFormatTest.java
Posted by Tamás Cservenák <ta...@cservenak.net>.
Hi,
completely agreed, but let me explain -- not that it matters:
I had a lot of accumulated changes in my github fork of maven-indexer,
and initially did not wanted to disturb other forks of my repository.
Hence, I started pushing changes _without_ changing commit messages
first -- thinking "it would change history, hence screw other forks".
I was distracted with ASF SVN mirroring pain (dcommiting multiple
commits from EU, --no-rebase was not helping, there was a lot of
interlaving changes for same file), but solved luckily:
http://twitter.com/#!/cstamas/status/53021178750701568
And then I realized: git-svn _also modifies_ history, but it was late
then :( I already started pushing (and had to recover few times until
I found out the dnsmasq fix), since there was a LOT of commits to be
dcommited back to ASF SVN.
To at least make it better, I linked the MINDEXER jira issues to the
SVN revisions, so at least we have the JIRA->SVN direction, but SVN
commit logs does not point back.
http://jira.codehaus.org/browse/MINDEXER-15
http://jira.codehaus.org/browse/MINDEXER-16
http://jira.codehaus.org/browse/MINDEXER-17
http://jira.codehaus.org/browse/MINDEXER-18
Thanks,
~t~
On Wed, Mar 30, 2011 at 12:20 PM, Benjamin Bentmann
<be...@udo.edu> wrote:
> I think it would be more appropriate if those commits were mentioning the
> corresponding MINDEXER issue.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org