Interesting! If it does work then:

1) I'd notify infra because this permits any committer to destroy the
log history without a trace ;)

2) the consequences for git mirrors of any project that did such a
change are also interesting -- incremental git svn won't pick these up
and effectively the git mirror contains different logs than the
official SVN.

Dawid

On Fri, Jan 22, 2016 at 8:24 PM, Ishan Chattopadhyaya
<[email protected]> wrote:
> Seems to have worked for Dennis:
> http://lucene.472066.n3.nabble.com/Update-commit-message-td4249465.html#a4249469
>
> On Sat, Jan 23, 2016 at 12:51 AM, Dawid Weiss <[email protected]> wrote:
>>
>> I'm sorry, I wasn't precise enough -- have you tried it on the Apache
>> SVN? Quote:
>>
>> "The first way is for the repository administrator to enable revision
>> property modifications."
>>
>> I admit I didn't check, but I'd be surprised if these were allowed as
>> this permits historical changes to the content of the repository. If
>> you do have admin privileges you can rewrite the repository entirely
>> and do whatever you can, obviously.
>>
>> Dawid
>>
>> On Fri, Jan 22, 2016 at 8:16 PM, Steve Rowe <[email protected]> wrote:
>> > Not true - you can fix it in SVN.
>> >
>> > From <http://subversion.apache.org/faq.html#change-log-msg>:
>> >
>> > svn propset -r N --revprop svn:log "new log message” URL
>> >
>> > --
>> > Steve
>> > www.lucidworks.com
>> >
>> >> On Jan 22, 2016, at 2:13 PM, Dawid Weiss <[email protected]> wrote:
>> >>
>> >> No way to do it in SVN. You can revert your commit and commit the same
>> >> one again, with proper message.
>> >>
>> >> In the git world this would be possible (locally, with git commit
>> >> --amend), but after you push to a remote repository this would be
>> >> discouraged and the same way as above would be advised since other
>> >> people might already be using your commit.
>> >>
>> >> D.
>> >>
>> >> On Fri, Jan 22, 2016 at 8:08 PM, Anshum Gupta <[email protected]>
>> >> wrote:
>> >>> Does anyone here know how to edit a log message after committing? I
>> >>> accidentally typed in lucene instead of solr for one of the release
>> >>> related
>> >>> commits.
>> >>>
>> >>> On Fri, Jan 22, 2016 at 11:03 AM, Anshum Gupta
>> >>> <[email protected]>
>> >>> wrote:
>> >>>>
>> >>>> Hi Adrien,
>> >>>>
>> >>>> I'm in the middle of publishing the artifacts. I should be able to
>> >>>> get to
>> >>>> it in just a bit.
>> >>>> Thanks for reminding.
>> >>>>
>> >>>> On Fri, Jan 22, 2016 at 7:58 AM, Adrien Grand <[email protected]>
>> >>>> wrote:
>> >>>>>
>> >>>>> Anshum, I would like to draw your attention to the fact that Dawid
>> >>>>> plans
>> >>>>> to start the git migration at 4PM PST, and I think it would be
>> >>>>> preferable to
>> >>>>> commit the backward compatibility indices before that (which I think
>> >>>>> is the
>> >>>>> only remaining step that requires you to modify the code base).
>> >>>>>
>> >>>>> If you will not be able to do it by that time, I can take care of
>> >>>>> it,
>> >>>>> just let me know.
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> --
>> >>>> Anshum Gupta
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Anshum Gupta
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: [email protected]
>> >> For additional commands, e-mail: [email protected]
>> >>
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: [email protected]
>> > For additional commands, e-mail: [email protected]
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to