This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFA] Rename python files.


On Sat, Aug 29, 2009 at 9:13 AM, Thiago Jung
Bauermann<thiago.bauermann@gmail.com> wrote:
> Em Terça-feira 25 Agosto 2009 12:28:17 Matt Rice escreveu:
>> On Fri, Aug 14, 2009 at 12:11 AM, Eli Zaretskii<eliz@gnu.org> wrote:
>> >> How should said renaming be done, by submitting and committing a patch
>> >> which removes the old file and adds a new one, or by moving things
>> >> around in CVSROOT?
>> >
>> > The latter is better, because it preserves the CVS history. ?But I
>> > think it requires special privileges on the repository.
>>
>> fyi I believe that by moving things around in the CVSROOT the changes
>> will not be automatically picked by the cvs/git conversion.
>
> I don't know much about conversions from CVS so I'll take your word on it. A
> quick search on the interwebs seem to indicate that conversion tools aren't
> good about detecting renames anyway, since CVS doesn't support the operation.
>
> IMHO the best way to do it then is to use the CVS-friendly way of doing a
> "rename": cvs rm $FILE, cvs add $NEW_FILE. IUUC git would be able to detect
> such rename (though I don't know it would show up in an svn-converted repo).

Yeah, i'm really not familiar with conversions or monkeying with CVS
under the hood either,
only been on the losing end of it :).

referring back to the issue i had:
http://sourceware.org/ml/archer/2009-q1/msg00332.html

it looks like i remembered incorrectly, and according to Jim's 'For
the record,' portion
it is possible to do in a cvs/git friendly way.

sorry should have looked back in my emails for this earlier.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]